You are coding human-in-the-loop for a multi-agent refunds system on Azure. Refunds over $500 require manager approval. Which implementation best matches production HITL patterns?
Select an answer to reveal the explanation.
Short Explanation
You need a real approval gate that pauses the workflow, tells the manager what the agent proposed, records the decision, and only then lets the refund tool run. That keeps high-dollar refunds controlled and auditable.
Full Explanation
The approval workflow step that pauses orchestration, notifies the manager with the agent proposal, records approve/reject/override, and only then allows the refund tool to execute is correct because multi-agent solutions require human-in-the-loop approval workflows, overrides, and explicit continuation rules. The refund tool must be gated on recorded human decisions for amounts over threshold. TODO comments are not controls. Asynchronous email without a blocking approval state allows unauthorized execution. Simulated approval is fraudulent automation. Persist approval artifacts, including who, when, and decision, for audit and compliance reporting.