1
Intent
A practitioner or agent declares a goal: approve a vendor renewal, update an OKR, transition a workflow.
2
Context
Spine Fabric assembles the dossier: related records, policy context, historical precedent, and current state.
3
Decision
Twin or the practitioner evaluates the dossier and decides on the action.
4
Proposal
Twin drafts the specific capability invocation with parameters and expected outcome.
5
Capability Resolution
The system checks authorization, role scope, and record-level permissions for the proposed action.
6
Handoff
If the action requires another approver or specialist, it is routed with full context.
7
Tool Selection
The target source system and connector are identified: ERP for vendor updates, Asana for workflow transitions, Notion for OKR progress.
8
MCP/Connector
The capability is translated into a connector request with schema-mapped payload.
9
Authorization
OAuth or API credentials are resolved and token freshness is verified.
10
Human Approval
Actions beyond pre-authorized thresholds pause for explicit human confirmation in the workbench.
11
Workflow Execution
The connector executes the write and captures the response.
12
Source-System Write
The source system commits the change and returns a confirmation.
13
Receipt
Spine generates an audit receipt with identity, timestamp, parameters, and outcome.
14
Event
A Spine event is emitted so views update and downstream agents react.
15
Continuation
Context, receipts, and next tasks persist for the practitioner or the next agent.