1
Intent
A TAM or agent identifies a need: update a milestone, escalate an integration failure, or schedule an architecture review. Intent is expressed through the UI or inferred by Twin from monitoring signals.
2
Context
Spine Fabric assembles full technical context: architecture, integrations, issues, API usage, deployments, and authorization scope.
3
Decision
Twin or the TAM selects the action from available capabilities. The system validates actor authorization for the target entity and capability.
4
Proposal
For complex actions, Twin generates a proposal with expected changes, affected systems, and side effects. The TAM reviews before confirmation.
5
Capability Resolution
The action maps to a governed capability:
jira.ticket.create, datadog.dashboard.annotate, or workflow.escalation.technical. Scope enforced at resolution time.6
Handoff
If the action spans systems or teams, Twin coordinates handoff. Escalations notify engineering. Architecture reviews schedule with stakeholders.
7
Tool Selection
Spine Fabric selects the connector: Jira REST API, Datadog API, Zendesk API, or documentation store.
8
MCP/Connector
The connector translates the capability into a native API call with authentication, field mapping, and error handling.
9
Authorization
Final check validates connector token, user permissions, and entity scope before API execution.
10
Human Approval
High-impact actions require explicit approval: production deployments, architecture changes, customer-facing outage communication. Approvals route to defined approvers.
11
Workflow Execution
The API call executes. Workflow capabilities may run multiple steps with intermediate validation.
12
Source-System Write
The target system records the change. Jira creates the ticket. Datadog adds the annotation. Documentation updates. Confirmation returned.
13
Receipt
Spine Fabric records a receipt: actor, capability, target, timestamp, outcome, source-system reference. Receipts visible in account timeline.
14
Event
A domain event emitted: TicketCreated, EscalationInitiated, MilestoneUpdated. Agents and views react.
15
Continuation
Session state updates with completed action and pending follow-ups. Continuity ensures next session or handoff resumes seamlessly.