1
Intent
An executive signals an intent: record a decision, update a commitment, draft an update, or prepare a meeting.
2
Context
Spine loads the full projection: linked meetings, attendee context, metrics, emails, and Slack threads.
3
Decision
Twin proposes the most likely next action based on context, rules, and historical outcomes.
4
Proposal
The proposal is surfaced in the workbench: draft text, capability name, target system, and expected effect.
5
Capability Resolution
Spine resolves the capability to concrete operations, such as
founder_ops.decision.create or founder_ops.update.publish.6
Handoff
If required, the proposal is routed to an approver before execution.
7
Tool Selection
The connector for the target system (Notion, Gmail, etc.) is selected by Spine.
8
MCP / Connector
The operation is translated to the target API call through the connector layer.
9
Authorization
Credentials and permissions are verified against the governance policy for this role and scope.
10
Human Approval
If the capability requires it, a human confirms before execution.
11
Workflow Execution
The action runs: a decision is recorded, an email is drafted, or a meeting agenda is updated.
12
Source System Write
The update is committed to the source system and acknowledged.
13
Receipt
A receipt with operation details, timestamp, and actor is stored in Spine.
14
Event
A state change event is emitted for downstream agents and views.
15
Continuation
Context remains available for follow-up actions without reassembly.