# Ask one question at a time

Tested daily in the verification lane and the inbox triage: one question, at the end, as tap options. Batches stall; singles get answered.

From the [Learned the hard way](../index.md#learned) section of [The Muse Field Guide](../index.md).

## The claim

Decision traffic works when it is one question per message, placed at the end, offered as tap options.

## What happened

The household's decision traffic runs on this format as a standing rule. The operator answers in fragments, often a single word, and the work keeps moving. A batch of five questions gets none answered; five single questions get five. The rule holds in two very different rooms: a verification lane ruling on data claims, and an inbox triage that surfaces exactly one question per pass.

## Where this came from

The format has been a standing rule since October 19, 2026, and it also forces the agent to decide what it actually needs, which turns out to be the harder discipline.

Deep dive: [Memory that holds](../deep-dives/memory.md)

Related resources: [One question, at the end](one-question-at-a-time.md), [Restate the question with the choices](restate-the-question.md)

Canonical page: https://www.niclydon.io/muse/items/verdict-one-question-at-a-time.html
