> ## 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.

# Legal Execution Flow: Intent to Receipt and Continuation

> Trace the Execution Path for Legal actions, from intent and decision through capability resolution, approval, source-system write, and receipt.

The execution flow is the governed path that turns a practitioner's intent into a source-system change in the Legal domain. Every step is auditable, and every completed action produces a receipt.

<Steps>
  <Step title="Intent">
    A contracts manager decides to move a contract to the approval stage. Twin records the intent and links it to the contract context.
  </Step>

  <Step title="Context">
    Twin assembles the contract terms, party profiles, redline history, and policy rules to ensure the move is valid.
  </Step>

  <Step title="Decision">
    Twin presents the proposed move with reasoning. The contracts manager confirms.
  </Step>

  <Step title="Proposal">
    Twin generates a capability proposal: `legal.contract.stage.update` with target stage and contract ID.
  </Step>

  <Step title="Capability Resolution">
    Spine checks that the contracts manager has the required capability and that the scope covers this contract.
  </Step>

  <Step title="Handoff">
    If the stage change triggers the approval chain, Twin hands off to the Approval workflow and notifies the General Counsel.
  </Step>

  <Step title="Tool Selection">
    Spine selects the Ironclad connector to perform the stage update.
  </Step>

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

  <Step title="Authorization">
    Spine verifies OAuth tokens and rate limits before sending the request.
  </Step>

  <Step title="Human Approval">
    If the policy requires approval for this contract type, the request routes to the General Counsel for sign-off.
  </Step>

  <Step title="Workflow Execution">
    The stage update executes. Subsequent workflow steps, such as approval notifications, are triggered.
  </Step>

  <Step title="Source-System Write">
    Ironclad records the new stage. The connector captures the response.
  </Step>

  <Step title="Receipt">
    Spine generates a receipt with actor, action, timestamp, and outcome. It is stored for audit.
  </Step>

  <Step title="Event">
    A ContractStageUpdated event is produced and re-enters the system flow.
  </Step>

  <Step title="Continuation">
    Context is updated. Twin resumes monitoring and proposes the next step, such as sending the approval request.
  </Step>
</Steps>

## Related

* [System Flow](/internal-docs/domains/legal/system-flow)
* [Capabilities](/internal-docs/domains/legal/capabilities)
* [How It Works: Governed Actions](/how-it-works/governed-actions)