09 - SUPERTRACK I: Hard Blocks / Do-Not-Touch Review

Required hard-block coverage (macro list)

required item	present in doc 08	verdict
Stage 2.6B	yes (§A)	covered
permit	yes (§A)	covered
REAL_RUN	yes (§A)	covered
QT001 apply	yes (§A)	covered
owner/ACL cutover	yes (§A)	covered
manifest activation	yes (§A)	covered
Directus authority change	yes (§A, scoped)	covered
scheduler/action enablement	yes (§A)	covered
production writer execution	yes (§A)	covered
old dangerous DOT unfreeze	yes (§A)	covered
birth gateway modification unless separately authorized	MISSING -> added (XHH-01)	covered after fix
registry-pivot repoint until birth/governance/registry truth pass	MISSING -> added (XHH-01)	covered after fix

Finding

XHH-01 (P1) - two required hard-block rows missing

• The High draft listed the birth gateway under §B do-not-touch objects but had no §A hard-blocked action row for "birth gateway modification," and had no row at all for "registry-pivot repoint"
  • both explicitly required by the macro's SUPERTRACK I.
• Fix: added two §A rows:
  • birth gateway modification (DO_NOT_TOUCH) - FIX7 references the gateway only via #26; a CREATE OR REPLACE of the gateway is the DOT-119 hazard (now guarded by G-DOT-NOOVERWRITE); unlock only via a separate explicitly-authorized birth-gateway program.
  • registry-pivot repoint (BLOCKED_UNTIL_AUTHORITY) - must not occur until birth/governance/ registry truth all pass; FIX7's repoint (S13-S15) is scoped to the QT001 control-plane writer/ gateway, NOT a broader registry-of-record pivot.

Cross-impact checked

• The "registry-pivot repoint" hard block is consistent with the new cross-layer OUT-OF-SCOPE section (doc 08 §E) and with doc 04's framing of S13-S15 as a QT001-control-plane-scoped repoint.
• The "birth gateway modification" block reinforces DO_NOT_TOUCH (§B) and G-DOT-NOOVERWRITE / G-BIRTH-NEUTRAL.

Verdict

HARD_BLOCKS_PASS_AFTER_FIX - all macro-required hard blocks now present and preserved; nothing in the blueprint unlocks any of them.