RS-TKT-1 (Phase 1) · 16 — Compatibility Matrix: Design vs Codex-Accepted Patches

Lane: RS-TKT-1 — Phase 1 TKT Base Design Package (design-only) Date: 2026-06-22 Gate: REGISTRATION_HOLD · REGISTRATION_CAN_PROCEED = NO · 0 runtime mutations Authority: NON_AUTHORITY · may_gate=false · decision_effect=NONE

Traceability from the Codex-accepted PATCH1/PATCH2 contracts (and the carry-forward caveats) to the Phase-1 design files, the construction-blueprint files, and the negative fixtures. A requirement with no clean mapping is not CLOSED — it is HOLD_TRACEABILITY_MISSING.

---

1. Compatibility matrix

requirement_id	source	design file	construction blueprint file	negative fixture	expected outcome	compatible	stop state if HOLD
Codex PATCH2 acceptance	codex-rereview-rs-tkt-0a-patch2-2026-06-22.md	00, 01	—	—	Phase 1 design-only opened under HOLD	YES	—
P1 unstructured forbidden output	PATCH2 01	04 (6-conjunct + token floor + detector order)	11, 12, 13	BAD-FC-001..008	deterministic FAIL/SAFE_REJECT/HOLD	YES	—
P6 profile_id schema	PATCH2 02	08 (profile_id 2 values, scope_class 3 values)	10 rs_profile_checker	BAD-RS-001	no profile_id=structural; no auto-promote	YES	—
P7 HOLD propagation + truth table	PATCH2 03	06 (rules + 10-row table)	13 report schema	BAD-PROP-001, BAD-PROP-002	HOLD≠PASS; N/A no upgrade	YES	—
P2 L3 split	PATCH1 02	05 (four one-concern bricks)	10 module boundaries	BAD-L3-001	no cross-brick read; split held	YES	—
P3 source authority hierarchy	PATCH1 03	00 §6, 01 §6	—	(MCB-6 caveat)	Tier-1/2/3; DRAFT≠enacted	YES	—
P4 L1 vs Phase-4 boundary	PATCH1 04	02 §3 (L1 inert only)	10, 11, 15	BAD-L1-001	HOLD_RUNTIME_SURFACE_REQUIRED	YES	—
P5 NVSZ taxonomy + ledger	PATCH1 05	07 (ESCROW_E*/ROOT_E*, hash_manifest.sha256)	14	BAD-NVSZ-001, BAD-NVSZ-002	ESCROW_E5/ESCROW_E9	YES	—
REGISTRATION_HOLD	all patches + Codex §8	every file header	every file header	TKT-RS-GATE-001 analog	HOLD remains active	YES	—
REGISTRATION_CAN_PROCEED = NO	all patches + Codex §8	every file header	every file header	BAD-FC-007	=YES ⇒ FAIL	YES	—
NVSZ root caveat (MCB-5)	Codex §6.2; PATCH1 05 §4	07 §6	14 §5	BAD-NVSZ-002	undesignated blocks Phase 3, not Phase 1	YES (open caveat)	—
RS5B draft caveat (MCB-1)	Codex §6.1; PATCH2 02 §5	08 §4/§5/§7	10 rs_profile_checker	BAD-RS-001	RS5B stays SELF_REPORTED_DRAFT	YES (open caveat)	—
MCB-6 architecture caveat	Codex §6.3; PATCH1 03 §5	00 §6	—	—	three-tier hierarchy; MCB-6 OPEN	YES (open caveat)	—
Caveat §5 reserved-token floor as versioned config	Codex §6.5	04 §3 (token_floor_config)	13 schema	BAD-FC-001/006/007	floor versioned, monotonic, normalization defined	YES	—
Caveat §6 aggregate N/A removed	Codex §6.6	06 §3 (aggregate ∈ {PASS,FAIL,HOLD})	13 §4	BAD-PROP-002	no unreachable aggregate N/A	YES	—
Caveat §7 "0 mutations" = attestation	Codex §6.7	22 mutation confirmation	—	—	attestation, not live proof	YES	—

2. No-overwrite / additive-supersession discipline

Phase 1 edits NO prior file. RS-TKT-0A 00–08, patch1/00–08, patch2/00–04 stay revision 1.
Phase 1 inherits PATCH1/PATCH2 by REFERENCE (this matrix), not by re-statement-that-could-drift.
The only existing file touched is index.md (additive Phase-1 pointer).
Where Phase 1 adds something new (caveat §5 token_floor_config in 04; caveat §6 aggregate-N/A removal in 06),
  it is an ADDITIVE clarification on top of the accepted contract, never a weakening.

3. Completeness verdict

All 15 required rows map to a design file (and, where applicable, a construction-blueprint file and a negative fixture) with a deterministic expected outcome.
No row is HOLD_TRACEABILITY_MISSING.
Three rows are open CAVEATS (MCB-1, MCB-5, MCB-6) — non-blocking for Phase 1 (Codex §6/§7), tracked in 20.
⇒ compatibility matrix COMPLETE (not RS_TKT_1_HOLD_COMPATIBILITY_MATRIX_INCOMPLETE).