Facio Blog

Practical notes on human-reviewed AI agents.

Payload-powered product notes, security writing, HITL patterns, and operational guidance from the Facio runtime: long sessions, Placet approvals, audit trails, memory, providers, channels, tools, and Docker-first operations.

Clear

Showing 21-25 of 73 articles in Human-in-the-loop.

Human-in-the-loop

HITL and the Reciprocity Problem: Why Reviewer Decisions Bias Toward the Customer Even When Policy Suggests Otherwise

Jul 18, 2026Human-in-the-loop

HITL and the Reciprocity Problem: Why Reviewer Decisions Bias Toward the Customer Even When Policy Suggests Otherwise

Reviewers show customers mercy. The policy says reject, the reviewer approves with a note. The policy says escalate, the reviewer reassures. Reviewers don't apply policy neutrally — they apply policy with an unconscious tilt toward the customer's side. The reciprocity problem is the most pervasive reviewer bias in HITL, and the most invisible. Here is how it manifests, why it matters, and how to design for it.

Human-in-the-loop

HITL and the Latency Tax: Why Every Second of Review Waits Has a Cost the System Doesn't Acknowledge

Jul 17, 2026Human-in-the-loop

HITL and the Latency Tax: Why Every Second of Review Waits Has a Cost the System Doesn't Acknowledge

Every HITL review waits. The customer's request sits in the queue. The latency is real — the customer perceives it, the SLA measures it, the business pays for it. But most HITL systems treat the latency as external to the HITL design. The latency is internal. The latency has a cost. The cost is a tax on every decision the reviewer makes. Here is why the latency tax is the most underrated cost in HITL.

Human-in-the-loop

HITL and the Paradox of Choice: Why Fewer Options Make Reviewers More Accurate

Jul 16, 2026Human-in-the-loop

HITL and the Paradox of Choice: Why Fewer Options Make Reviewers More Accurate

Every HITL interface gives the reviewer four options: approve, reject, modify, escalate. Add "ask for context" and "defer" and "flag for policy review" and "request rollback preview" — and the reviewer's accuracy drops. The paradox of choice in HITL: the more options the reviewer has, the worse the decisions get. Less is more. Here is why, and how to design the choice architecture that maximizes reviewer accuracy.

Human-in-the-loop

HITL as a Forgetting Curve: Why Reviewer Memory Is the Limiting Factor Nobody Measures

Jul 15, 2026Human-in-the-loop

HITL as a Forgetting Curve: Why Reviewer Memory Is the Limiting Factor Nobody Measures

Reviewers forget. The first 50 actions of the day are calibrated. The next 100 are fatigued. The last 50 are rubber stamps. HITL systems are designed for the first 50, monitored for the middle 100, and silent about the last 50. The forgetting curve is the limiting factor on HITL quality — and most teams don't measure it because measuring it would force them to redesign the schedule.

Human-in-the-loop

HITL as a Trust Calibration: Why the Real Job of the Reviewer Is to Calibrate the System, Not the Individual Action

Jul 14, 2026Human-in-the-loop

HITL as a Trust Calibration: Why the Real Job of the Reviewer Is to Calibrate the System, Not the Individual Action

Most HITL designs treat the reviewer's job as evaluating individual actions. But the deeper job is calibrating the system — every decision is a data point that updates the team's belief about the agent, the policy, the interface, and the reviewer pool. The reviewer who only evaluates individual actions is doing one job. The reviewer who calibrates the system is doing the job HITL was actually designed for.