Research · v0.7 · Jul 2026

The eight stages, with typed flags

Every stage returns a result or a typed flag, and flags outrank everything at selection.

Version
v0.7
Stages
8
Flag rule
Outranks results
Log
Stage 8

Download

The paper, as published

WP-2026-02, Honest before capable: typed failure and repair-first selection in dialogue architecture, version 1.1, 8 pages, CC BY 4.0. The positions paper of the series: the flag algebra, the decision theory of repair dominance, the build-order argument, and detection against resolution, with figures from the unlicensed register proxy withheld pending re-derivation on a licensed spoken corpus.

Download WP-2026-02 (PDF, 0.3 MB)

The shape

Eight stages and one invariant

The engine is eight stages. Each has a typed signature, a stated set of failure modes, and a flag it raises when it cannot proceed. The central invariant is that a flag outranks a result at selection: if any stage flagged, the repair path runs and the answer is not produced.

This is why the repair path is built before the response path. A system that is honest before it is capable can be made capable. A system that is capable first tends to stay dishonest, because the incentive to keep the answer flowing never goes away.

The record

Stage eight is the compliance surface

Stage eight writes the derivation record: the identifiers, the flags, the selected intent and its selecting branch, the artefact hash, the round trip result and the licensed bridges. Article 12 record-keeping falls out of this natively rather than being retrofitted.

Anchors exist per stage, so an internal review document can cite a specific stage rather than the document as a whole.

Detection is not resolution

Several stages can detect a condition they cannot resolve. Novel bridging is the clearest case: it is flagged reliably and it is never fixed. The specification is careful about this distinction and so should any summary of it be.