---
title: The Uncertainty Gate: Ask Once, Learn Forever
type: playbook
level: L2
status: live
revision: 1
updated: 2026-08-14
systemVersion: 4.2
tags: [uncertainty, routing, playbook]
rating: 7.40
ratingAxes: useful 8 · evidence 6 · pull 7 · original 8 · form 9
ratingKind: derived
source: uncertainty gate, in production
---

# The Uncertainty Gate: Ask Once, Learn Forever

_Written 2026-08-14 · last verified 2026-08-14 · system v4.2 · live_

**TL;DR** — An agent facing a classification or routing choice at roughly 40 to 75 percent confidence should ask rather than guess. The half everyone skips is the second: record the resolved mapping, so the same question is never asked twice. Without that, asking becomes a tax rather than a learning mechanism.

## Prerequisites

An agent that makes discrete choices — where a file goes, which category applies, which of two readings of a request is intended. A place to record resolved mappings.

If every choice is either obvious or genuinely novel, this adds nothing. It earns its keep in the middle band.

## Steps

**1. Identify the band.** The gate fires between roughly **40% and 75%** confidence, or whenever 2 or more options are live. Above that, act. Below it, the question is not *which* but *what is this*, which is a different problem.

**2. Distinguish thinking from choosing.** Reversible analysis proceeds without asking — an agent that stops to confirm every interpretation before reading a file is useless. The gate applies to **lossy or irreversible selections**: filing, routing, classification, anything where a wrong choice is expensive to undo or invisible once made.

**3. Ask in a form that is cheap to answer.** Two or three concrete options with the consequence of each, not an open question:

> `A` file under the supplier · `B` file under the project · `C` both, cross-linked
> Default if you do not answer: `A`

The default matters. It converts silence into a decision rather than a block.

**4. Record the resolved mapping immediately.** This is the step that makes the gate worth having. The answer goes into a reference file as a rule, not as a note about one incident:

> invoices from a logistics provider → filed under the project, not the supplier *(resolved 2026-08-14)*

**5. Check the record before asking.** Every firing of the gate begins by searching prior resolutions. An agent that asks a resolved question is not being careful, it is being forgetful, and it burns the goodwill the gate depends on.

**6. Batch the questions.** More than 3 open choices at once is not a series of questions, it is a form. Present them together as a clickable list with defaults rather than interrupting 3 times — the answer rate on a single batch is dramatically better than on scattered prompts, and the operator can see the whole shape of what is unresolved.

**7. Do not fire on the extremes.** The gate is for the middle band. A clear match needs no question; something entirely unrecognised is not a choice between options but a request for information, and dressing it up as A/B/C wastes the operator's time on a menu that contains no correct answer.

## Verify

Count the questions over a month and look at the ratio of **novel** to **repeat**. Novel is the gate working. Repeat means step 4 or step 5 is not happening, and the gate is degrading into an interruption habit.

A second check: how many resolutions were later contradicted? A high number means the options being offered are the wrong ones — the agent is asking a question that does not carve the problem at its joints.

## Troubleshooting

**Too many questions.** Usually the band is being applied to reversible analysis. Re-read step 2; thinking is not choosing.

**The gate never fires.** Either the confidence estimate is not being made at all, or it is being made after the decision, which is rationalisation rather than estimation.

**Answers do not stick.** Resolutions are being written as incident notes rather than as rules. `Palo said file it under the project` is not reusable; the generalised form is.

**Asking feels expensive.** Then it is too expensive to survive contact with a busy week. Reduce it to a single click with a stated default, or the gate will be quietly abandoned at exactly the moment it matters.