security//human-in-the-loop

Human-in-the-loop (HITL) design requires a person to review or authorize selected parts of a system's trajectory. The phrase says little until three details are specified: which actions stop, what evidence the reviewer sees, and what occurs after rejection.

Human-in-the-loop (HITL) design requires a person to review or authorize selected parts of a system's trajectory. The phrase says little until three details are specified: which actions stop, what evidence the reviewer sees, and what occurs after rejection.

Approvals work best for rare, consequential and legible decisions. If prompts are constant, low-information or routinely safe, the human learns to click through them. The interface then preserves ceremony while losing judgment.

A person in the loop is not automatically a control. Sometimes it is only latency wearing a badge.