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

# Content Execution Flow: Intent to Published Output and Receipt

> Learn how the Content Execution Flow transforms practitioner intent into governed actions, source-system writes, receipts, and continuity.

The Content Execution Flow is the path from a practitioner's intent to a completed action in a connected system. It ensures every publish, review, and update is authorized, tracked, and preserved.

<Steps>
  <Step title="Intent">
    A practitioner decides to publish an article, request a review, or upload an asset. The intent is captured in the workbench.
  </Step>

  <Step title="Context">
    Spine assembles the full context: article metadata, campaign links, prior versions, and pending comments.
  </Step>

  <Step title="Decision">
    The practitioner or Twin selects the appropriate capability, such as `content.article.publish`.
  </Step>

  <Step title="Proposal">
    Twin or the workbench presents a proposal with expected outcome, target system, and required approvals.
  </Step>

  <Step title="Capability Resolution">
    Spine resolves the capability, checking authorization, scope, and approval requirements.
  </Step>

  <Step title="Handoff">
    If multi-step, the workflow routes to the next actor: editor, manager, or agent.
  </Step>

  <Step title="Tool Selection">
    Spine selects the correct connector: WordPress, Contentful, Confluence, or another target.
  </Step>

  <Step title="MCP / Connector">
    The connector translates the action into the target system's API request.
  </Step>

  <Step title="Authorization">
    OAuth tokens or service credentials are retrieved and validated for the write operation.
  </Step>

  <Step title="Human Approval">
    If required, a final human confirms the action before execution.
  </Step>

  <Step title="Workflow Execution">
    The action runs. The source system creates or updates the record.
  </Step>

  <Step title="Source-System Write">
    The target system returns a confirmation with IDs, URLs, and timestamps.
  </Step>

  <Step title="Receipt">
    Spine generates a receipt capturing intent, actor, capability, outcome, and source confirmation.
  </Step>

  <Step title="Event">
    An event is emitted. Views update. Agents are notified.
  </Step>

  <Step title="Continuation">
    Context and memory persist for the next session, handoff, or follow-up action.
  </Step>
</Steps>

### Related

* [Content Workflows](/internal-docs/domains/content/workflows)
* [Content Capabilities](/internal-docs/domains/content/capabilities)
* [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.