Intervention needs enough information and time

What it is

A gate before consequence is not enough. To decide release, a person needs the present state, what is about to happen, and time in which to make that judgement. Missing one, the gate becomes default consent when a countdown ends. A meaningful review window is information and time arriving together; supplying only one leaves intervention empty.

A button, five seconds on a clock, a summary that says “about to send” — that is not an opportunity to intervene.

Why it happens

Judging is work. Work needs materials: who the recipients are, which attachment, what amount, which passage is the basis. It also needs time: to read those materials, to match them to one’s own goal, to consider a veto. Automation raises execution speed far above reading speed; if the window opens on machine tempo, people can only use a heuristic: looks normal, release. That heuristic is the door automation bias walks through.

A window without information forces a guess; a window without time forces a rush. Both pressures turn veto into a right that exists in theory and cannot be used in practice. In aviation and process control, time-to-takeover is measured as a hard constraint. Generative agents spend the same constraint on a confirm dialog that does not size dwell to the amount of reading.

Studying it

System factors: density of the summary (are object, consequence, basis listed), available time (self-paced versus countdown). The task includes harmful items that should be vetoed and normal items that should pass. Dependent variables: catch rate on harmful items, false vetoes on normal ones, decision time, reports of “I had not finished reading.”

Countdown conditions must record how many releases are defaults after time ran out. A default yes is not a person’s decision.

Where it stops holding

An operator who has been sitting in the context for a long time (continuous monitoring of one flow) needs less extra information, but still needs “how this step differs from the last.” Someone pulled in once to sign needs a full rebuild and a longer window. Emergency stop is the reverse case: time is tiny, information is crushed into one large Stop, and the judgement was encoded into that act in advance. That is not review. Do not reuse a confirm dialog for it. This entry does not treat “there is a button but no authority to veto”; that is control in name only.

Applying it

• A release surface must list concrete objects and concrete consequences: to whom, which rows, what amount, whether it goes outward. Missing one, release does not light.
• Give time by reading volume, not by animation. Default to self-paced; if the business insists on a cap, the cap must fit the object list, and timeout must be a veto or hold-unexecuted, not a release.
• Provide an explicit “I have not finished reading.” Do not take silence as consent.
• Check: hide a harmful item in the middle of the list and keep your current window. If it is not caught, add information or add time until a mid-list item is also readable. Then count timeout-default releases — any number above zero means the window is still deciding for the person.

Related

• Same group: L1.05.1 The intervention point must sit before consequences land · L1.05.3 Formal intervention is not actual control
• Nearby: L1.09 Intervention points in the human loop · L4.04 Takeover and handoff design · L4.11 Pre-action confirmation and irreversible operations
• Search terms: meaningful review window · time to intervene · information for veto