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

# Business Operations Execution Path: Intent to Source-System Write

> The governed execution path for Business Operations: from intent and context assembly through human approval to source-system write and continuity.

The Execution Flow in Business Operations is the path from a human or agent intent to a verified change in a source system. It is governed at every step.

<Steps>
  <Step title="Intent">
    A practitioner or agent declares a goal: approve a vendor renewal, update an OKR, transition a workflow.
  </Step>

  <Step title="Context">
    Spine Fabric assembles the dossier: related records, policy context, historical precedent, and current state.
  </Step>

  <Step title="Decision">
    Twin or the practitioner evaluates the dossier and decides on the action.
  </Step>

  <Step title="Proposal">
    Twin drafts the specific capability invocation with parameters and expected outcome.
  </Step>

  <Step title="Capability Resolution">
    The system checks authorization, role scope, and record-level permissions for the proposed action.
  </Step>

  <Step title="Handoff">
    If the action requires another approver or specialist, it is routed with full context.
  </Step>

  <Step title="Tool Selection">
    The target source system and connector are identified: ERP for vendor updates, Asana for workflow transitions, Notion for OKR progress.
  </Step>

  <Step title="MCP/Connector">
    The capability is translated into a connector request with schema-mapped payload.
  </Step>

  <Step title="Authorization">
    OAuth or API credentials are resolved and token freshness is verified.
  </Step>

  <Step title="Human Approval">
    Actions beyond pre-authorized thresholds pause for explicit human confirmation in the workbench.
  </Step>

  <Step title="Workflow Execution">
    The connector executes the write and captures the response.
  </Step>

  <Step title="Source-System Write">
    The source system commits the change and returns a confirmation.
  </Step>

  <Step title="Receipt">
    Spine generates an audit receipt with identity, timestamp, parameters, and outcome.
  </Step>

  <Step title="Event">
    A Spine event is emitted so views update and downstream agents react.
  </Step>

  <Step title="Continuation">
    Context, receipts, and next tasks persist for the practitioner or the next agent.
  </Step>
</Steps>

**Related**

* [Overview](/internal-docs/domains/business-ops/index)
* [Capabilities](/internal-docs/domains/business-ops/capabilities)
* [Workflows](/internal-docs/domains/business-ops/workflows)
* [System Flow](/internal-docs/domains/business-ops/system-flow)
* [How It Works: Governed Actions](/how-it-works/governed-actions)


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