1
Intent
A recruiter decides to move a candidate to the offer stage. Twin records the intent and links it to the candidate context.
2
Context
Twin assembles the requisition, feedback, and policy rules to ensure the move is valid.
3
Decision
Twin presents the proposed move with reasoning. The recruiter confirms.
4
Proposal
Twin generates a capability proposal:
hr.candidate.stage.update with target stage and candidate ID.5
Capability Resolution
Spine checks that the recruiter has the required capability and that the scope covers this requisition.
6
Handoff
If the stage change triggers an offer, Twin hands off to the Offer workflow and notifies the Compensation Agent.
7
Tool Selection
Spine selects the Greenhouse connector to perform the stage update.
8
MCP/Connector
The connector translates the capability into a Greenhouse 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 stage, the request routes to the hiring manager for sign-off.
11
Workflow Execution
The stage update executes. Subsequent workflow steps, such as offer drafting, are triggered.
12
Source-System Write
Greenhouse 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 CandidateStageUpdated event is produced and re-enters the system flow.
15
Continuation
Context is updated. Twin resumes monitoring and proposes the next step, such as scheduling the debrief.