1
Intent
A practitioner decides to publish an article, request a review, or upload an asset. The intent is captured in the workbench.
2
Context
Spine assembles the full context: article metadata, campaign links, prior versions, and pending comments.
3
Decision
The practitioner or Twin selects the appropriate capability, such as
content.article.publish.4
Proposal
Twin or the workbench presents a proposal with expected outcome, target system, and required approvals.
5
Capability Resolution
Spine resolves the capability, checking authorization, scope, and approval requirements.
6
Handoff
If multi-step, the workflow routes to the next actor: editor, manager, or agent.
7
Tool Selection
Spine selects the correct connector: WordPress, Contentful, Confluence, or another target.
8
MCP / Connector
The connector translates the action into the target system’s API request.
9
Authorization
OAuth tokens or service credentials are retrieved and validated for the write operation.
10
Human Approval
If required, a final human confirms the action before execution.
11
Workflow Execution
The action runs. The source system creates or updates the record.
12
Source-System Write
The target system returns a confirmation with IDs, URLs, and timestamps.
13
Receipt
Spine generates a receipt capturing intent, actor, capability, outcome, and source confirmation.
14
Event
An event is emitted. Views update. Agents are notified.
15
Continuation
Context and memory persist for the next session, handoff, or follow-up action.