> ## Documentation Index
> Fetch the complete documentation index at: https://docs.integratewise.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# HR Execution Flow: Intent to Receipt and Continuation

> Trace the Execution Path for HR actions, from intent and decision through capability resolution, approval, source-system write, and receipt.

The execution flow is the governed path that turns a practitioner's intent into a source-system change in the HR domain. Every step is auditable, and every completed action produces a receipt.

<Steps>
  <Step title="Intent">
    A recruiter decides to move a candidate to the offer stage. Twin records the intent and links it to the candidate context.
  </Step>

  <Step title="Context">
    Twin assembles the requisition, feedback, and policy rules to ensure the move is valid.
  </Step>

  <Step title="Decision">
    Twin presents the proposed move with reasoning. The recruiter confirms.
  </Step>

  <Step title="Proposal">
    Twin generates a capability proposal: `hr.candidate.stage.update` with target stage and candidate ID.
  </Step>

  <Step title="Capability Resolution">
    Spine checks that the recruiter has the required capability and that the scope covers this requisition.
  </Step>

  <Step title="Handoff">
    If the stage change triggers an offer, Twin hands off to the Offer workflow and notifies the Compensation Agent.
  </Step>

  <Step title="Tool Selection">
    Spine selects the Greenhouse connector to perform the stage update.
  </Step>

  <Step title="MCP/Connector">
    The connector translates the capability into a Greenhouse API call.
  </Step>

  <Step title="Authorization">
    Spine verifies OAuth tokens and rate limits before sending the request.
  </Step>

  <Step title="Human Approval">
    If the policy requires approval for this stage, the request routes to the hiring manager for sign-off.
  </Step>

  <Step title="Workflow Execution">
    The stage update executes. Subsequent workflow steps, such as offer drafting, are triggered.
  </Step>

  <Step title="Source-System Write">
    Greenhouse records the new stage. The connector captures the response.
  </Step>

  <Step title="Receipt">
    Spine generates a receipt with actor, action, timestamp, and outcome. It is stored for audit.
  </Step>

  <Step title="Event">
    A CandidateStageUpdated event is produced and re-enters the system flow.
  </Step>

  <Step title="Continuation">
    Context is updated. Twin resumes monitoring and proposes the next step, such as scheduling the debrief.
  </Step>
</Steps>

## Related

* [System Flow](/internal-docs/domains/human-resources/system-flow)
* [Capabilities](/internal-docs/domains/human-resources/capabilities)
* [How It Works: Governed Actions](/how-it-works/governed-actions)