1
Intent
A PM approves a sprint change or an on-call engineer resolves an incident.
2
Context
Spine Fabric assembles the relevant entities, history, and authorization.
3
Decision
Twin or the practitioner confirms the action: update issue, merge PR, run playbook.
4
Proposal
A capability is generated with inputs, scope, and expected outcome.
5
Capability Resolution
The capability is matched to a registered connector and authorization scope.
6
Handoff
If human approval is required, the proposal is surfaced in the workbench.
7
Tool Selection
The connector for Linear, GitHub, or PagerDuty is selected based on target system.
8
MCP/Connector
The connector translates the capability into a native API call.
9
Authorization
The call is authorized with scoped credentials and policy checks.
10
Human Approval
Sensitive actions pause for explicit approval before execution.
11
Workflow Execution
The action runs: issue moves, PR merges, incident resolves.
12
Source-System Write
The change is committed in the source system.
13
Receipt
A receipt is generated with actor, action, scope, time, and outcome.
14
Event
The receipt becomes an event, re-ingested into Spine Fabric.
15
Continuation
Full context persists for the next actor or session.