RS5B-CLOSEOUT-PATCH1 — Index — 2026-06-21

Package: knowledge/dev/laws-new/reports/rs5b-closeout-patch1/ (11 files) + reports-level rollup. Verdict: RS5B_CLOSEOUT_PATCH1_READY_FOR_GPT_REVIEW (not forced). Gate: REGISTRATION_HOLD · REGISTRATION_CAN_PROCEED = NO · 0 mutations (KB-only, design-only, no live runtime read). Closes: Codex HOLD REJECT_LEGO_BOUNDARY_INSUFFICIENT / stop RS5B_CLOSEOUT_P2_ENTRY_HOLD_DEPENDENCY_SAFE_ROLLBACK_AND_GATE_SPLIT_REQUIRED. Scope: narrow Job-B patch — dependency-safe rollback, rollback validity (not presence), new XBI, C7 conditionality, baseline-vs-P2-open gate split. Job A not reopened (Codex §3/§12). No P2 opened, no runtime, no rollback executed.

---

Reading order

1. 01-source-register-and-codex-hold-reconstruction-2026-06-21.md — Codex-mode reconstruction (mandatory posture); direct-read register (Codex HOLD 13156 + 10 closeout files + rollup, all truncated=false); the eight Job-B residuals R1–R8 with exact Codex sections; additivity proof.
2. 02-dependency-safe-rollback-contract-c1-c7-2026-06-21.md — invariants I1–I10; per-carrier allowed/forbidden/postcondition (C1–C7); coverage matrix; "deletion is not rollback"; ROLLBACK_CONTRACT_VALID_FOR_REVIEW necessary-not-sufficient.
3. 03-carrier-dependency-map-and-reference-preservation-2026-06-21.md — explicit 8-edge graph (E1–E8); per-edge producer/consumer/reference field/break/safe-rule/post-rollback invariant/bad input.
4. 04-rollback-validity-oracle-and-new-xbi-fixtures-2026-06-21.md — RBP-0..RBP-9/RBP-PASS classifier + total precedence; proof that a destructive-but-present plan cannot PASS; XBI-11..XBI-25.
5. 05-c7-conditionality-policy-mode-resolution-2026-06-21.md — approval_mode ∈ {APPROVAL_USED, APPROVAL_NOT_USED_BY_POLICY}; Rule A/Rule B; "all seven before P3" superseded.
6. 06-two-gate-sequencing-baseline-vs-p2-open-2026-06-21.md — Gate A P2_BASELINE_ENTRY_DESIGN_ACCEPTED vs Gate B P2_OPEN_AUTHORIZED_FOR_NAMED_CARRIER_PLAN_ONLY; no "Gate A → P2 open" transition.
7. 07-impact-map-and-superseded-closeout-wording-2026-06-21.md — M1–M10 superseded phrases; §5 NOT-reopened list (Job A intact).
8. 08-codex-style-adversarial-self-review-2026-06-21.md — 10 attack sections + A1–A20 result table; all rejected before any PASS.
9. 09-decision-packet-2026-06-21.md — verdict, why-not-another, must-not-do compliance, carried blockers, single next step.
10. codex-review-packet-rs5b-closeout-patch1-rollback-gate-split-2026-06-21.md — what to verify, adversarial checks, allowed verdicts, what acceptance does/does-not authorize.
11. ../macro-rs5b-closeout-patch1-rollback-gate-split-2026-06-21.md — macro rollup (reports level).

One-line thesis

A rollback is valid only if it preserves stable identity, historical evidence, reference integrity, prior-envelope semantics, and authority strength — and is versioned, auditable, and local. A rollback that deletes a referenced identity, orphans a dependency, erases history, weakens authority, or opens P2 early is rejected by the contract before any PASS — proven by the RBP oracle precedence (file 04 §3), not asserted by the word "rollback."

Boundaries (held in every file)

REGISTRATION_HOLD retained · REGISTRATION_CAN_PROCEED = NO · 0 mutations · no P2 opened · no carrier/Owner/scope/register_dot/APR/approval/handler created · no canonical-operation runtime rows · no registrar/validator patch · no RS-VALIDATOR · no rollback executed · no Chairman authorization asserted · Job A not reopened · no mega-registry/mega-graph/mega-birth pipeline · approval authority not inherited into registration/activation · classifier totality ≠ runtime totality · design fixtures DEFINED_NOT_EXECUTED · engineering/contract PASS ≠ authority/runtime PASS · rollback-contract validity ≠ rollback-execution authorization.

Single next step: GPT review of this PATCH1 only → Codex review → corrected Job-B wording carries into the closeout (the Gate A baseline). Residual ⇒ future RS5B-CLOSEOUT-PATCH2.