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

# Operations Execution Flow: Governed Action to Source Write

> How an operational intent becomes a governed, audited action that writes back to source systems and preserves continuity across sessions.

The Execution Flow is the path from a human or agent decision to a concrete change in a source system. In Operations, this covers ticket updates, asset assignments, vendor changes, approval decisions, and workflow triggers.

<Steps>
  <Step title="Intent">
    A practitioner or agent decides to act: approve a request, assign an asset, or trigger vendor onboarding.
  </Step>

  <Step title="Context">
    Spine Fabric assembles the target entity, related records, active policies, and authorization scope for the intended action.
  </Step>

  <Step title="Decision">
    Twin or the practitioner confirms the action path, selecting from proposed options or entering custom parameters.
  </Step>

  <Step title="Proposal">
    The system generates a capability proposal: which capability, on which entity, with what parameter values, and the expected outcome.
  </Step>

  <Step title="Capability Resolution">
    The capability engine checks authorization, policy constraints, and target system availability. It returns a resolved capability or a denial with reason.
  </Step>

  <Step title="Handoff">
    If the action spans systems, the workflow engine coordinates handoffs: asset update to ServiceNow, license change to Google Workspace, notification to Slack.
  </Step>

  <Step title="Tool Selection">
    The connector layer selects the right adapter for each target system and translates the capability into native API parameters.
  </Step>

  <Step title="MCP/Connector">
    The adapter dispatches the call to the source system API or Model Context Protocol endpoint.
  </Step>

  <Step title="Authorization">
    The target system validates its own credentials and permissions. Any failure is returned as an error receipt.
  </Step>

  <Step title="Human Approval">
    For sensitive actions, an inline approval step pauses execution until an authorized human confirms.
  </Step>

  <Step title="Workflow Execution">
    The action executes. If part of a larger workflow, downstream steps are queued.
  </Step>

  <Step title="Source-System Write">
    The change is committed in the source system. The new state is emitted as an event back into Spine Fabric.
  </Step>

  <Step title="Receipt">
    A receipt records the actor, target, before and after state, timestamp, and linked context. It is immutable and auditable.
  </Step>

  <Step title="Event">
    The state change event triggers any dependent projections, alerts, or agent responses.
  </Step>

  <Step title="Continuation">
    Session context, open items, and notes are preserved so the next practitioner or agent resumes with full awareness.
  </Step>
</Steps>

<Warning>
  A failed Source-System Write does not rollback earlier steps automatically. The workflow engine marks the step as failed and surfaces it for operator review.
</Warning>

### Related

* [Workflows](/internal-docs/domains/operations/workflows)
* [Capabilities](/internal-docs/domains/operations/capabilities)
* [System Flow](/internal-docs/domains/operations/system-flow)
* [Governed Actions](/how-it-works/governed-actions)


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