Build · 17 Apr 2026
The repair path was built before the response path
A system that is honest before it is capable can be made capable. The other order rarely recovers.
Specifics
The numbers, and where they come from
| Quantity | Value | Basis |
|---|---|---|
| Flags implemented first | All 11 | Counted |
| Response path started | 6 weeks later | Stated |
| Turns refused correctly before first answer | 100% | Measured |
| Flag outranks result | Invariant | Stated |
The order
Refusing first
For the first two months this engine could not answer anything. It could parse, it could detect the eleven failure conditions, and it could raise the right flag for each. Building that first meant the invariant that flags outrank results was load-bearing from the beginning rather than retrofitted around a working answer path.
Retrofitting it is where systems go wrong. Once answers flow, every incentive points at letting a marginal one through, and the flag becomes advisory.
What it cost
Two months with nothing to demonstrate
It is a genuinely awkward thing to explain to anyone expecting a demo. The compensation is that the repair surface is not a fallback in this system, it is the primary path, and it behaves that way because it was there first.