Check E - ACTIVE_AUTHORITY / SUPERSEDED_NON_AUTHORITY Boundary Recheck

Verdict: ACTIVE_SUPERSEDED_BOUNDARY_NEEDS_FIX

Accepted: the registry, per-doc DOC_STATUS markers, and BEGIN/END fences are machine-readable, unambiguous in the reviewed revision, and not Directus-editable.

Remaining blocker: they are mutable KB text and are not pinned to the exact Codex-reviewed document revisions/content hashes. G-ACTIVE-AUTHORITY-SCOPE currently checks classification syntax, but cannot prove that the active corpus being consumed is the exact corpus reviewed here. A later marker, fence, registry, or body edit could change authority without a new approval.

Required fix:

1. Produce an immutable/content-addressed approval envelope listing every ACTIVE document/section, exact KB revision and SHA-256, plus a manifest/envelope SHA-256 and this Codex recheck identity.
2. Missing/extra document, revision drift, content/hash drift, marker/fence drift, or envelope mismatch must invalidate authoring approval and require a fresh Codex recheck.
3. Extend G-ACTIVE-AUTHORITY-SCOPE to verify that exact envelope, not only marker syntax.
4. Keep this approval envelope non-runtime: no new authority surface, readiness gate, #20 column, catalog family, or top-level FIX7 runtime hash contract.