> ## Documentation Index
> Fetch the complete documentation index at: https://docs.integratewise.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Product Engineering Execution Flow: Action to Result

> How governed actions resolve in the Product Engineering domain, from intent through tool execution and receipt.

The Execution Flow in Product Engineering turns human or agent intent into concrete changes in source systems. Every step is governed, scoped, and logged.

<Steps>
  <Step title="Intent">
    A PM approves a sprint change or an on-call engineer resolves an incident.
  </Step>

  <Step title="Context">
    Spine Fabric assembles the relevant entities, history, and authorization.
  </Step>

  <Step title="Decision">
    Twin or the practitioner confirms the action: update issue, merge PR, run playbook.
  </Step>

  <Step title="Proposal">
    A capability is generated with inputs, scope, and expected outcome.
  </Step>

  <Step title="Capability Resolution">
    The capability is matched to a registered connector and authorization scope.
  </Step>

  <Step title="Handoff">
    If human approval is required, the proposal is surfaced in the workbench.
  </Step>

  <Step title="Tool Selection">
    The connector for Linear, GitHub, or PagerDuty is selected based on target system.
  </Step>

  <Step title="MCP/Connector">
    The connector translates the capability into a native API call.
  </Step>

  <Step title="Authorization">
    The call is authorized with scoped credentials and policy checks.
  </Step>

  <Step title="Human Approval">
    Sensitive actions pause for explicit approval before execution.
  </Step>

  <Step title="Workflow Execution">
    The action runs: issue moves, PR merges, incident resolves.
  </Step>

  <Step title="Source-System Write">
    The change is committed in the source system.
  </Step>

  <Step title="Receipt">
    A receipt is generated with actor, action, scope, time, and outcome.
  </Step>

  <Step title="Event">
    The receipt becomes an event, re-ingested into Spine Fabric.
  </Step>

  <Step title="Continuation">
    Full context persists for the next actor or session.
  </Step>
</Steps>

### Related

* [Capabilities](/internal-docs/domains/product-engineering/capabilities)
* [Workflows](/internal-docs/domains/product-engineering/workflows)
* [System Flow](/internal-docs/domains/product-engineering/system-flow)
* [How It Works: Governed Actions](/how-it-works/governed-actions)
* [How It Works: Continuity](/how-it-works/continuity)