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

# Founder Ops Execution Flow: Intent to Source Update

> The full governed execution path in Founder Ops: intent, context assembly, decision, capability resolution, authorization, and receipt.

The Execution Flow defines how an executive intent becomes an actual update in Gmail, Notion, Calendar, or Slack. Every stage is traceable, authorized, and reversible until execution completes.

<Steps>
  <Step title="Intent">
    An executive signals an intent: record a decision, update a commitment, draft an update, or prepare a meeting.
  </Step>

  <Step title="Context">
    Spine loads the full projection: linked meetings, attendee context, metrics, emails, and Slack threads.
  </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 text, capability name, target system, and expected effect.
  </Step>

  <Step title="Capability Resolution">
    Spine resolves the capability to concrete operations, such as `founder_ops.decision.create` or `founder_ops.update.publish`.
  </Step>

  <Step title="Handoff">
    If required, the proposal is routed to an approver before execution.
  </Step>

  <Step title="Tool Selection">
    The connector for the target system (Notion, Gmail, 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 decision is recorded, an email is drafted, or a meeting agenda is updated.
  </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

* [Founder Ops Index](/internal-docs/domains/founder-ops/index)
* [Capabilities](/internal-docs/domains/founder-ops/capabilities)
* [System Flow](/internal-docs/domains/founder-ops/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.