1
Intent
A contracts manager decides to move a contract to the approval stage. Twin records the intent and links it to the contract context.
2
Context
Twin assembles the contract terms, party profiles, redline history, and policy rules to ensure the move is valid.
3
Decision
Twin presents the proposed move with reasoning. The contracts manager confirms.
4
Proposal
Twin generates a capability proposal:
legal.contract.stage.update with target stage and contract ID.5
Capability Resolution
Spine checks that the contracts manager has the required capability and that the scope covers this contract.
6
Handoff
If the stage change triggers the approval chain, Twin hands off to the Approval workflow and notifies the General Counsel.
7
Tool Selection
Spine selects the Ironclad connector to perform the stage update.
8
MCP/Connector
The connector translates the capability into an Ironclad API call.
9
Authorization
Spine verifies OAuth tokens and rate limits before sending the request.
10
Human Approval
If the policy requires approval for this contract type, the request routes to the General Counsel for sign-off.
11
Workflow Execution
The stage update executes. Subsequent workflow steps, such as approval notifications, are triggered.
12
Source-System Write
Ironclad records the new stage. The connector captures the response.
13
Receipt
Spine generates a receipt with actor, action, timestamp, and outcome. It is stored for audit.
14
Event
A ContractStageUpdated event is produced and re-enters the system flow.
15
Continuation
Context is updated. Twin resumes monitoring and proposes the next step, such as sending the approval request.