Incomex AI Portal
KB-435B

RS5B-CLOSEOUT-PATCH2 08 — Impact Map & Superseded PATCH1 Wording — 2026-06-21

8 min read Revision 1
rs5b-closeout-patch2impact-mapsuperseded-wordingrollback-oracleregistration-hold2026-06-21

RS5B-CLOSEOUT-PATCH2 08 — Impact Map & Superseded PATCH1 Wording — 2026-06-21

Purpose: record every PATCH1 phrase Codex rejected, the problem, the new controlling phrase, and status — so the consolidated reading is unambiguous about which text governs. Supersessions are wording/pointer changes carried additively; the original rev-1 PATCH1 files are not mutated. Job A is not reopened; I1–I10 are not weakened. Gate: REGISTRATION_HOLD · REGISTRATION_CAN_PROCEED = NO · 0 mutations.

Columns: old phrase / source · problem · new controlling phrase · status. Continues the PATCH1-07 sequence (M1–M10); PATCH2 entries are M11–M17.

1. Oracle PASS formula & numbering (Codex B1 — superseded by file 02)

M11 — PASS formula omits ¬RBP1

  • Old phrase / source: PATCH1-04 §3 — "PASS ⟺ ¬RBP0 ∧ ¬RBP2 ∧ … ∧ ¬RBP9" and "RBP-1 (plan absent) is not a conjunct of PASS."
  • Problem (Codex §6.1): if ROLLBACK_PLAN_ABSENT matches, PASS must be impossible; omitting ¬RBP1 makes the proof implementation-dependent and contradicts the necessary-not-sufficient claim.
  • New controlling phrase: ROLLBACK_CONTRACT_VALID_FOR_REVIEW ⇔ ¬RBP0 ∧ ¬RBP1 ∧ ¬RBP2 ∧ … ∧ ¬RBP10 = "no reject predicate matches" (file 02 §2; proof P-B1).
  • Status: SUPERSEDED_BY_RS5B_CLOSEOUT_PATCH2.

M12 — reject-set numbering (no dedicated I6 predicate)

  • Old phrase / source: PATCH1-04 §1 reject set (RBP-0, RBP-2..RBP-9, RBP-1) with "I6 … enforced jointly by RBP-7 (no successor) and the per-carrier postconditions."
  • Problem (Codex §6.2): I6 has no complete reject predicate; a plan with a successor rule can still admit the retired value and reach PASS.
  • New controlling phrase: eleven reject predicates RBP-0..RBP-10 with RBP-8 ROLLBACK_FORWARD_FAIL_CLOSED_VIOLATED = I6, disjoint from RBP-7 by predicate Q; audit→RBP-9, locality→RBP-10 (file 02 §1/§3; file 03).
  • Status: SUPERSEDED_BY_RS5B_CLOSEOUT_PATCH2.

2. XBI fixtures (Codex B3/B4/B5 — superseded by file 04)

M13 — XBI-13 single fixture → RBP-4

  • Old phrase / source: PATCH1-04 XBI-13 — "drop a hash referenced by effect_identity/audit ⇒ ROLLBACK_ERASES_HISTORY (RBP-4)," with the parenthetical that "RBP-2 targets owner/operation identities."
  • Problem (Codex §6.3): deleting a referenced hash identity matches RBP-2 (or RBP-3), both of which precede RBP-4; a fixture cannot override precedence by sentence.
  • New controlling phrase: XBI-13A (hash identity deleted ⇒ RBP-2) and XBI-13B (identity remains, payload erased ⇒ RBP-4) (file 04 §1; disjointness file 03 §2).
  • Status: SUPERSEDED_BY_RS5B_CLOSEOUT_PATCH2 (split into 13A/13B).

M14 — XBI-14 / XBI-19 multi-outcome

  • Old phrase / source: PATCH1-04 XBI-14 (lists RBP-3 and RBP-5) and XBI-19 (RBP-9/locality with an acknowledged RBP-5 variant).
  • Problem (Codex §6.4): each fixture must define one exact input and one exact code; variants must be split.
  • New controlling phrase: XBI-14A (cannot resolve ⇒ RBP-3) / XBI-14B (resolves but re-meant ⇒ RBP-5); XBI-19A (silent rewrite, meaning preserved ⇒ RBP-10) / XBI-19B (silent rewrite + meaning changed ⇒ RBP-5) (file 04 §2/§3).
  • Status: SUPERSEDED_BY_RS5B_CLOSEOUT_PATCH2 (each split into single-input/single-code).

M15 — missing forward-fail-closed & C2-weakening fixtures

  • Old phrase / source: PATCH1-04 §4 — no fixture for "successor exists but retired value remains valid for new use" and none for "C2 successor schema weakens forward authorization."
  • Problem (Codex §7.3/§7.4): the proof that invalid inputs cannot reach PASS was incomplete without these.
  • New controlling phrase: XBI-26 (successor present, retired value admissible ⇒ RBP-8) and XBI-27 (C2 successor weakens authority ⇒ RBP-6), incl. sub-cases 27-a/b/c (file 04 §4/§5).
  • Status: EXTENDED_BY_RS5B_CLOSEOUT_PATCH2 (additive; closes B6/B7).

3. C2 / I5 coverage (Codex B8 — superseded by file 05)

M16 — I5 "not applicable to C2 / discharged transitively"

  • Old phrase / source: PATCH1-02 §4 — I5 row "C2 = —" and the parenthetical "For C1/C2/C4/C5 the authority-non-weakening obligation is discharged transitively … those live in C3/C6/C7."
  • Problem (Codex §4): C2 controls whether authority references are required; a successor schema can weaken forward authority by dropping/optionalizing a required reference without touching C3/C6/C7.
  • New controlling phrase: I5 covers C2 (forward branch); coverage matrix I5 row C2 = ✔; the C2 forward-non-weakening rule (file 05 §2) forbids dropping/optionalizing required authority refs; violation ⇒ ROLLBACK_WEAKENS_AUTHORITY (RBP-6). C1/C4/C5 transitive discharge unaffected.
  • Status: SUPERSEDED_BY_RS5B_CLOSEOUT_PATCH2 (for the C2 cell only).

4. Gate B wording (Codex B9 — superseded by file 06)

M17 — "Neither gate opens P2"

  • Old phrase / source: PATCH1-06 intro ("Neither gate opens P2; Gate A authorizes only preparing a plan …") and §6 ("Neither gate opens P2, authorizes a write, creates a carrier, or clears a blocker").
  • Problem (Codex §9): contradicts Gate B's output P2_OPEN_AUTHORIZED_FOR_NAMED_CARRIER_PLAN_ONLY — a satisfied Gate B is the P2-named-lane-open gate.
  • New controlling phrase: the sealed five-part statement (file 06 §2): this package/Gate A do not open P2; a future satisfied Gate B may open the named lane only; never registration/activation/register_dot/P3/runtime; the bare sentence "Neither gate opens P2" is forbidden.
  • Status: SUPERSEDED_BY_RS5B_CLOSEOUT_PATCH2.

5. Adversarial self-review correction (Codex B3 — superseded by file 09)

M18 — PATCH1-08 A3 result

  • Old phrase / source: PATCH1-08 §3 / §10 — "A3 drop the hash ⇒ ROLLBACK_ERASES_HISTORY (RBP-4)."
  • Problem (Codex §6.3 final sentence): "PATCH1-08 repeats the same inconsistent A3 result."
  • New controlling phrase: A3 (hash identity deleted) ⇒ ROLLBACK_DELETES_REFERENCED_IDENTITY (RBP-2); A4 (hash payload erased) ⇒ ROLLBACK_ERASES_HISTORY (RBP-4) (file 09 §3, A3/A4).
  • Status: SUPERSEDED_BY_RS5B_CLOSEOUT_PATCH2.

6. Explicitly NOT superseded / NOT reopened

PATCH2 changes only the wording above. The following remain exactly as accepted and are not reopened:

  • Job A — the consolidated RS5B_CONTRACT_AS_CORRECTED_BY_PATCH1_PATCH2 (Codex §2 carried).
  • Invariants I1–I10 (PATCH1-02 §2) — retained; C2 added to I5 coverage strengthens, never weakens.
  • Dependency-safe carrier patterns C1–C7 (PATCH1-02 §3) — retained; only predicate-consistency clarifications (C2-I5, hash identity-vs-payload) added.
  • Dependency graph E1–E8 (PATCH1-03) — retained; E3 bad-input refined to identity-vs-payload, not reopened.
  • C7 approval_mode rule (PATCH1-05) — Codex §8 PASS_WITH_CAVEAT; not reopened.
  • Gate A/Gate B inputs and outputs (PATCH1-06 §2/§3/§4) — retained; only non-overclaim wording sealed.
  • PATCH1 XBI-11/12/15/16/17/18/20–25 — retained unchanged.
  • The LEGO rule (born/test/change/rollback/join separate; no mega-registry) — retained; PATCH2 adds the readiness seal, does not relax it.
  • Carried blockers — unchanged (file 01 §5).

7. Net controlling reading after PATCH2

Job A unchanged. The RBP oracle PASS condition is the full conjunction including ¬RBP1 (file 02); I6 has the dedicated predicate RBP-8 (file 02); RBP-2/3/4/5/6/8 are mutually precise and the fixtures obey the precedence (file 03/04); every XBI is single-input/single-code, with XBI-26/27 added (file 04); I5 covers C2 forward schema evolution (file 05); the Gate B wording is sealed and "Neither gate opens P2" is forbidden (file 06); and LEGO #1 Assembly Readiness is defined with an attack-tested L1–L7 checklist (file 07). No original file overwritten; REGISTRATION_HOLD retained.

Back to Knowledge Hub knowledge/dev/laws-new/reports/rs5b-closeout-patch2/08-impact-map-and-superseded-patch1-wording-2026-06-21.md