Technical System Explainer

Default shape

Teach one useful mental model through one concrete path. Do not turn an explainer into a complete reference manual.

1. State the primary question in one sentence.
2. Give the short answer immediately.
3. Walk one representative scenario from start to finish.
4. Introduce boundaries, messages, states, or components at the moment the scenario crosses them.
5. Separate acceptance, internal state, and physical outcome when they prove different things.
6. Close with the few constraints or unresolved questions that materially change interpretation.

For HTML delivery, use html-rich-communication; its ten-minute lane owns page structure, verification, and publishing.

Source discipline

If a grounded explanation already exists in the conversation or working notes, use it. Do not repeat its research phase.