Ordering
Not all contracts are equal.
When multiple things are broken, this ordering prevents agents from polishing the experience layer on top of a lying data plane. Level 1 gates everything. Level 4 gates nothing essential. It orders dependent repairs inside one publishing surface; it does not replace the portfolio-wide control priority classes.
- 01
Data truth
Blocks everything
- Is the data pipeline running?
- Are observations being classified?
- Are snapshots materializing?
If broken: stop all other work.
- 02
Content truth
Blocks user trust
- Do pages show accurate data?
- Do facts match across surfaces?
- Do internal links resolve?
- Are stale pages degrading to SHELL?
Fix before any feature work.
- 03
Content depth
Blocks discoverability
- Are intelligence views computing?
- Is narrative enrichment running?
- Is the eval baseline improving?
Build after truth is established.
- 04
Experience
Blocks nothing essential
- Design polish
- Interactivity
- Advanced features
Only after levels 1–3 are stable.
Rule 01
Use the repair stack for repair sequencing.
If Level 1 is broken, do not work on Level 3. Across unrelated candidate actions, use the control priority classes instead. The protocol map owns that distinction.