Require a human final decision for every recommendation

Review the HITL confirmation card and verify that downstream Actors run only after a person confirms approved, partial, or rejected.

Question for this chapter

Where must a person confirm the decision after the AI recommendation?

Understand HITL in this situation

Human-in-the-loop does not mean a person performs every step manually. Evidence lookup, policy retrieval, and recommendation can be automated, while a person re-enters the flow before a consequential, difficult-to-reverse decision.

Try it

Continue the Agent session. After the AI proposes approved, partial, or rejected with a rationale, the capture_review_decision confirmation card opens. Compare:

order ID and requested amount
customer tier and risk_level
retrieved policy and AI-analysis summary
proposed decision, amount, and reviewer note

The reviewer may accept or change the proposal. No downstream Actor runs before confirmation.

flowchart LR
    accTitle: HITL boundary between an AI recommendation and a human decision
    accDescr: Order and policy evidence becomes an AI recommendation, then a human confirms approved, partial, or rejected before the corresponding result Actor runs.
    evidence["Order and policy evidence"] --> recommend["AI recommendation"]
    recommend --> confirm{"Human final decision"}
    confirm -->|approved or partial| refund["issue_refund result"]
    confirm -->|rejected| email["send_rejection_email result"]

Read the result

Human decision	Next Actor	Current return value
`approved`	`issue_refund`	refund ID, amount, and `processed` status object
`partial`	`issue_refund`	status object using the approved amount
`rejected`	`send_rejection_email`	`sent: true`, order ID, and reason object

What is automated

Automatable: evidence enrichment, risk triage, policy retrieval, recommendation summary
Human-owned: final approved, partial, or rejected confirmation
Automated after confirmation: the matching Actor call and result summary
Out of current scope: payment refund, email delivery, and persisted audit history

Next decision

You have confirmed the responsibility boundary. Next, check the batch distribution, Agent demo, and downstream-result limits in four questions before the final operations explanation.