RS-TKT-0A-PATCH1 · 06 — RS5A/RS5B Profile Provenance Split Patch (P6)

Lane: RS-TKT-0A-PATCH1 · Date: 2026-06-21 Gate: REGISTRATION_HOLD · REGISTRATION_CAN_PROCEED = NO · 0 runtime mutations (KB writes only) Authority: NON_AUTHORITY · may_gate=false · decision_effect=NONE · design-only

Supersedes: the single mixed profile in 06-rs5a-rs5b-pre-codex-profile-draft-2026-06-21.md and any generic "RS-series" labeling of RS5A-specific values.

---

1. The defect (Codex P6)

RS-TKT-0A's profile mixed externally Codex-caught RS5A rules with self-reported RS5B draft rules, and risked hardcoding RS5A-specific values (84/86 counts, Q-code order) as a generic RS-series contract. RS5B has no external Codex review; its BI01–BI10 are self-reported. The two provenances must be split and never described as equally validated.

2. Two named profiles

RS5A profile  =  CODEX_CAUGHT_RS5A
                 (rules traceable to actual Codex verdicts: RS5A original NEED_PATCH1,
                  PATCH1 NEED_PATCH2, PATCH2 NEED_PATCH3, PATCH3 REJECT (quorum precedence),
                  PATCH4 ACCEPT_with_registration_hold)

RS5B profile  =  SELF_REPORTED_RS5B_DRAFT
                 (rules from RS5B's own BI01–BI10 self-check; NO external Codex review yet)

RS5B rows MUST NOT be described as externally validated. A later Codex RS5B review must update the defect catalog before any RS5B row is promoted.

3. Per-rule provenance metadata (added to every 06 rule)

profile_id        : CODEX_CAUGHT_RS5A | SELF_REPORTED_RS5B_DRAFT
stage             : RS5A | RS5A-PATCH1..4 | RS5B
provenance        : codex_caught | self_reported
source_review     : <path to the Codex review or RS5B self-check doc>
validation_status : EXTERNALLY_CODEX_VALIDATED | SELF_REPORTED_DRAFT
applies_to        : <which packets/stages this rule governs>
does_not_apply_to : <explicit non-targets — prevents generic over-application>

4. Re-tagging of the 06 checker groups

The original 06 groups A–G are RS5A-grounded unless noted. Provenance assignment:

Group / rule	profile_id	provenance	validation_status	applies_to	does_not_apply_to
A Package (PKG-001..004)	structural	codex_caught (RS5A chain)	EXTERNALLY_CODEX_VALIDATED	any RS packet	—
B Gate (GATE-001..004)	structural	codex_caught	EXTERNALLY_CODEX_VALIDATED	any RS packet	—
C Lifecycle (LIFE-001..004)	CODEX_CAUGHT_RS5A	codex_caught (PATCH3)	EXTERNALLY_CODEX_VALIDATED	RS5A lifecycle packets	non-RS5A unless promoted
D Quorum (QUORUM-001..006)	CODEX_CAUGHT_RS5A	codex_caught (PATCH3 REJECT → PATCH4)	EXTERNALLY_CODEX_VALIDATED	RS5A quorum	generic RS-series
E Replay (REPLAY-001..005)	CODEX_CAUGHT_RS5A	codex_caught (PATCH4)	EXTERNALLY_CODEX_VALIDATED	RS5A replay	generic RS-series
F Count (COUNT-001..004)	CODEX_CAUGHT_RS5A	codex_caught (PATCH4)	EXTERNALLY_CODEX_VALIDATED	RS5A suites	generic RS-series
G Codex-packet (CODEX-001..004)	structural	codex_caught	EXTERNALLY_CODEX_VALIDATED	any RS packet	—
RS5B BI01–BI10	SELF_REPORTED_RS5B_DRAFT	self_reported	SELF_REPORTED_DRAFT	RS5B	all non-RS5B; not a gate

Groups A, B, G are structural/general (file-set, gate/HOLD integrity, codex-packet self-consistency) and apply to any RS packet. Groups C–F encode RS5A-specific content and are scoped to RS5A unless explicitly promoted later.

5. RS5A-specific values must NOT be generic

84 parent IDs / 86 executable scenarios  = RS5A-specific  (not generic RS-series unless promoted)
Q-code order Q00<…<Q50                     = RS5A-specific  (not generic unless promoted)
G02a/G02b/G02c effect→envelope tree        = RS5A-specific  (not generic unless promoted)
RS5B BI01–BI10                             = self-reported draft until Codex reviews RS5B

A checker run carries stage/profile_id; an RS5A rule fires only on RS5A-stage packets. Applying an RS5A count/quorum rule to a non-RS5A packet is a configuration error, not a finding.

6. Status effect

• RS5A profile (CODEX_CAUGHT_RS5A) may be cited as externally grounded (engineering grounding only — still NON_AUTHORITY, not a gate).
• RS5B profile (SELF_REPORTED_RS5B_DRAFT) remains DRAFT / NOT_EXTERNALLY_CODEX_VALIDATED; it may guide surveying and Phase-1 design but must not be called validated and must not be used as a gate (MCB-1 carry-forward).