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

# Support Execution Flow: From Intent to Source System Update

> The full governed execution path for a Support action: intent, decision, proposal, capability resolution, authorization, and receipt.

The Execution Flow defines how a human intent in the Support domain becomes an actual update in Zendesk, Linear, or PagerDuty. Every stage is traceable, authorized, and reversible until execution completes.

<Steps>
  <Step title="Intent">
    A support engineer signals an intent: reply to a customer, update status, or escalate to engineering.
  </Step>

  <Step title="Context">
    Spine loads the full projection for the ticket: history, customer, linked issues, and SLA state.
  </Step>

  <Step title="Decision">
    Twin proposes the most likely next action based on context, rules, and historical outcomes.
  </Step>

  <Step title="Proposal">
    The proposal is surfaced in the workbench: draft, capability name, target system, and expected effect.
  </Step>

  <Step title="Capability Resolution">
    Spine resolves the capability to concrete operations, such as `support.ticket.reply` or `support.escalation.create`.
  </Step>

  <Step title="Handoff">
    If required, the proposal is routed to a manager or on-call approver before execution.
  </Step>

  <Step title="Tool Selection">
    The connector for the target system (Zendesk, Linear, etc.) is selected by Spine.
  </Step>

  <Step title="MCP / Connector">
    The operation is translated to the target API call through the connector layer.
  </Step>

  <Step title="Authorization">
    Credentials and permissions are verified against the governance policy for this role and scope.
  </Step>

  <Step title="Human Approval">
    If the capability requires it, a human confirms before execution.
  </Step>

  <Step title="Workflow Execution">
    The action runs: a reply is sent, a status is updated, or a Jira issue is created.
  </Step>

  <Step title="Source System Write">
    The update is committed to the source system and acknowledged.
  </Step>

  <Step title="Receipt">
    A receipt with operation details, timestamp, and actor is stored in Spine.
  </Step>

  <Step title="Event">
    A state change event is emitted for downstream agents and views.
  </Step>

  <Step title="Continuation">
    Context remains available for follow-up actions without reassembly.
  </Step>
</Steps>

## Related

* [Support Index](/internal-docs/domains/support/index)
* [Capabilities](/internal-docs/domains/support/capabilities)
* [System Flow](/internal-docs/domains/support/system-flow)
* [Governed Actions](/how-it-works/governed-actions)
* [Continuity](/how-it-works/continuity)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.