1
Intent
You choose an action, such as advancing an opportunity stage or requesting a discount.
2
Context
Spine resolves the current deal graph, permissions, and guardrails relevant to the intent.
3
Decision
Twin or the domain agent confirms the action is valid and suggests any prerequisites.
4
Proposal
A capability proposal is generated: what will change, in which system, and what the outcome will be.
5
Capability Resolution
Spine selects the correct capability, such as
crm.opportunity.stage_update, and checks authorization.6
Handoff
If approval is required, the proposal routes to a manager or compliance agent.
7
Tool Selection
Spine picks the connector: Salesforce REST API, HubSpot API, or email gateway.
8
MCP/Connector
The connector translates the capability into the target system’s native API call.
9
Authorization
OAuth tokens or API keys are injected. The call is signed and scoped to the user.
10
Human Approval
For high-risk actions, a final approval panel is shown with diff and impact summary.
11
Workflow Execution
The API call is executed. Spine waits for confirmation and handles retries.
12
Source-System Write
Salesforce or HubSpot records are updated. Dependent triggers may fire in the source system.
13
Receipt
Spine generates a receipt: actor, timestamp, input, output, and sync status.
14
Event
A domain event is emitted. Views refresh, agents observe, and continuity tokens update.
15
Continuation
Your session context and the deal graph are updated. Twin monitors for the next trigger.