08 — Design / Index Update (SUPERTRACK H)

Updated

• knowledge/dev/architecture/BIRTH_GATEWAY_DESIGN_INDEX.md (revision 12): header status now states Stage 2.6A PASSED with SSOT registries live and apply still BLOCKED; a new macro row 2.6A added to the implementation table; a "QT-001 apply re-audit chain" section added; the Stage 2.6A live objects enumerated under "Live gateway facts"; birth anchor updated.
• knowledge/dev/architecture/BIRTH_STAGE2_6A_QT001_SSOT_PACKET.md (created): the Stage 2.6A handoff/re-audit packet — what was delivered, reviewer commands + expected results, what the next layers must do, and the re-audit requirement (external SAFE verdict bound to current plan checksum).

Stated explicitly in the design index

• Apply is still forbidden.
• Stage 2.6A is completed; the writer remains blocked until the next layers.
• The next layer is Permit/Run/Keyset/Resume (plus parity-invariant separation, trigger reconciliation, paired DOTs) — or whatever the router selects.
• A fresh independent Codex re-audit is required after each layer.

Continuity

The index now records the full QT-001 apply re-audit chain in order: Stage 2.5 hardening (PASS) → Codex Stage 2.5 re-audit (NOT_SAFE_NEEDS_FIX / SCALE_NOT_SAFE) → Stage 2.6A SSOT + hardcode elimination (PASS, apply blocked). This keeps the canonical entry point truthful about why apply is blocked and what must happen next.