1
Intent
A practitioner or agent decides to act: approve a request, assign an asset, or trigger vendor onboarding.
2
Context
Spine Fabric assembles the target entity, related records, active policies, and authorization scope for the intended action.
3
Decision
Twin or the practitioner confirms the action path, selecting from proposed options or entering custom parameters.
4
Proposal
The system generates a capability proposal: which capability, on which entity, with what parameter values, and the expected outcome.
5
Capability Resolution
The capability engine checks authorization, policy constraints, and target system availability. It returns a resolved capability or a denial with reason.
6
Handoff
If the action spans systems, the workflow engine coordinates handoffs: asset update to ServiceNow, license change to Google Workspace, notification to Slack.
7
Tool Selection
The connector layer selects the right adapter for each target system and translates the capability into native API parameters.
8
MCP/Connector
The adapter dispatches the call to the source system API or Model Context Protocol endpoint.
9
Authorization
The target system validates its own credentials and permissions. Any failure is returned as an error receipt.
10
Human Approval
For sensitive actions, an inline approval step pauses execution until an authorized human confirms.
11
Workflow Execution
The action executes. If part of a larger workflow, downstream steps are queued.
12
Source-System Write
The change is committed in the source system. The new state is emitted as an event back into Spine Fabric.
13
Receipt
A receipt records the actor, target, before and after state, timestamp, and linked context. It is immutable and auditable.
14
Event
The state change event triggers any dependent projections, alerts, or agent responses.
15
Continuation
Session context, open items, and notes are preserved so the next practitioner or agent resumes with full awareness.