06 - ACTIVE_AUTHORITY vs SUPERSEDED_NON_AUTHORITY Boundary

What Codex required

A machine-readable document/section status boundary so the no-disposition guard can distinguish current load-bearing authority from retained history. ACTIVE_AUTHORITY = current load-bearing sections (construction order, package split, guards, final verdict) — the only sections consumable by implementation authoring. SUPERSEDED_NON_AUTHORITY = historical notes, previous failed plans, prior XHigh/Max/Codex/T1 reports, stale instructions retained as audit trail — not consumable; may contain old terms only if clearly fenced and machine-readable as superseded. The boundary must be present, unambiguous, and not Directus-editable.

How T1 made it machine-readable (three mechanisms)

1. Per-doc DOC_STATUS: marker at the top of every numbered doc (HTML comment, deterministically parseable): <!-- DOC_STATUS: ACTIVE_AUTHORITY --> or <!-- DOC_STATUS: SUPERSEDED_NON_AUTHORITY -->.
   • ACTIVE: docs 00, 01, 02, 03, 04, 05, 06, 07, 08, 12.
   • SUPERSEDED (whole doc): 09 (XHigh review), 10 (Max review), 11 (revisions-from-reviews).
2. SUPERSEDED_NON_AUTHORITY BEGIN/END fences around retained history inside otherwise-active docs:
   • doc 00 §Self-verdict: the pre-Option-Beta gate-chain narrative is fenced.
   • doc 12: the Codex RECHECK-2 / Codex RECHECK (owner-semantics) / Codex critical-review patch passes, the A-K verdict alignment, and the Independent XHigh/Max narratives are fenced.
   • the blueprint checkpoint: the pre-recheck-3 patch-pass narratives + Phase outcomes are fenced.
3. The doc 00 §Active-authority boundary registry — a table enumerating the ACTIVE_AUTHORITY set and the SUPERSEDED_NON_AUTHORITY set with no overlap and no unclassified load-bearing section.

Not Directus-editable

The boundary lives only in the blueprint's KB document structure (markdown + HTML-comment markers

• the doc 00 registry), authored under T1/Codex discipline. It is not a Directus collection, not a #20/manifest row, and not a runtime table — so Directus has no write path to it. G-ACTIVE-AUTHORITY-SCOPE fails if the boundary is absent, ambiguous (a section both/neither), an unmatched/mis-nested fence, or expressed as a Directus-editable artifact. (This also keeps the boundary out of the 27/11/14/7 DB-surface count — it is document metadata, not a DB authority surface.)

Guards

• G-ACTIVE-AUTHORITY-SCOPE: boundary present + machine-readable + unambiguous + not Directus-editable; every load-bearing doc/section carries exactly one marker; the registry classifies docs 00..12.
• G-NO-SUPERSEDED-CONSUMPTION: no package (PKG-A..I), guard, seal, construction-order step, rollback step, or implementation-authoring input reads or derives authority from a SUPERSEDED_NON_AUTHORITY section.

Self-check

PASS. The ACTIVE_AUTHORITY vs SUPERSEDED_NON_AUTHORITY boundary is machine-readable (registry + markers + fences) and not Directus-editable.