0
Design a human-in-the-loop approval gate that doesn't create rubber-stamping
Design a human-in-the-loop approval step for an agent doing high_stakes_task. The goal is a real check, not a rubber-stamp click-through. Cover:
1. What information the approval UI/message must show the human to make an informed decision in under target_review_time: not the full agent reasoning trace (too long, gets skimmed), but the specific decision points a human reviewer actually needs to see to catch an error.
2. How to surface the agent's own uncertainty (if it has any signal of confidence) so the human's attention goes to the risky parts, not spread evenly across a routine-looking approval.
3. A rule against approval fatigue: if this agent's approvals are almost always rubber-stamped in practice, what design change (batching similar low-risk ones, sampling for audit instead of gating every one) would keep the check meaningful without approval volume burning out the reviewer.
4. What happens on rejection: does the agent get to see why (for learning/adjustment) or just a binary no, and how does it recover (retry with feedback, drop the action).
5. An audit trail requirement: what gets logged about the approval decision itself, not just the agent's action.
Task: high_stakes_task
Approval volume expected: volume