RS5B-PATCH2-04 — Impact Map and Superseded Wording — 2026-06-21

Macro: RS5B-PATCH2 · Deliverable 04 of 6 · design-only · scoped correction. Purpose: scan RS5B-PATCH1 and RS5B documents for the tokens affected by R1/R2 and classify each occurrence OK / SUPERSEDED / NEEDS_PATCH. Additive only — no existing file is overwritten.

1. Scan scope (verified inventory)

• knowledge/dev/laws-new/reports/rs5b-patch1/ — 7 files (index, 01–05, codex-review-packet) confirmed via list_documents.
• knowledge/dev/laws-new/reports/rs5b/ — 9 files (index, 01–07, codex-review-packet) confirmed via list_documents.
• Upstream comparison: knowledge/dev/laws-new/reports/rs4a-patch2/02-effect-identity-with-authorization-binding-separated-2026-06-21.md.

2. Tokens scanned

operation = "register_dot" · canonical_operation · kept out of the authorization binding · authorization_binding_digest · BI-E1 · BI-E6 · APPROVAL_NOT_BOUND_TO_EFFECT_IDENTITY · AUTHORIZATION_BINDING_MISSING_EFFECT.

3. Occurrence classification

#	file · locus	token / phrase	classification	disposition
1	rs5b-patch1/02 §2	operation = "register_dot" inside the effect_identity formula (the general founding formula)	SUPERSEDED	replaced by the general canonical_operation formula in PATCH2-02 §1
2	rs5b-patch1/02 §5	replacement prose using a bare generic operation in the effect formula	NEEDS_PATCH → superseded-wording	clarified: the operation field is canonical_operation (PATCH2-02 §1–§2); the §2/§5 internal inconsistency is resolved in favor of canonical_operation
3	rs5b-patch1/02 §3	authorization_binding_digest = H(… effect_identity REQUIRED …) field set	OK	unchanged (Codex §5 PASS); only the effect_identity it carries takes the general form
4	rs5b-patch1/04	BI-E1 input = "binding carrying owner/approval, but no effect_identity" → APPROVAL_NOT_BOUND_TO_EFFECT_IDENTITY	SUPERSEDED	re-homed to the Layer-2 approval-binding domain (digest includes effect, approval not bound to it) — PATCH2-03 §2
5	rs5b-patch1/04	BI-E6 input = "binding digest does not include effect_identity" → AUTHORIZATION_BINDING_MISSING_EFFECT	NEEDS_PATCH → superseded-wording	refined to the Layer-1 digest-shape domain (input schema omits effect), evaluated first — PATCH2-03 §2; reject code unchanged
6	rs5b-patch1/04	adversarial-table rows for BI-E1 and BI-E6	SUPERSEDED	replaced by the PATCH2-05 table reflecting the layered domains
7	rs5b-patch1/04	BI-E2 ARTIFACT_HASH_MISMATCH, BI-E3 AUTHORIZATION_SCOPE_MISMATCH, BI-E4 APPROVAL_NOT_BOUND_TO_EFFECT_IDENTITY, BI-E5 EFFECT_IDENTITY_IMPURE, BI-E7 AUTHORITY_OVERCLAIM	OK	unchanged (Codex §7: BI-E2–BI-E7 already have canonical outcomes); BI-E2 note re-affirmed under the general formula (artifact hash is still an input of effect_identity)
8	rs5b-patch1/05 (decision)	"New reject codes: AUTHORIZATION_BINDING_MISSING_EFFECT, EFFECT_IDENTITY_IMPURE"	OK	codes remain valid; PATCH2 adds design-level clarifying labels only (PATCH2-02 §7)
9	rs5b-patch1/05 + codex-review-packet	references to "the corrected formula" / BI-E1 / BI-E6 directions	NEEDS_PATCH → pointer	these pointers now resolve to the PATCH2 general formula and layered BI domains; the packets themselves are not rewritten (additive)
10	rs5b-patch1/01 (defect map), rs5b-patch1/03 (impact map), rs5b-patch1/index, rollup	restatements of the PATCH1 binding-direction fix	OK	binding-direction (effect-in-binding, authority-out-of-effect) is accepted (Codex §3) and unchanged; PATCH2 sits on top
11	rs5b/05 element 5	"the business-only effect digest (PATCH2 effect-identity) for the intended act, kept out of the authorization binding (separation)"	already SUPERSEDED_BY_RS5B_PATCH1	not reopened by PATCH2; PATCH1 fixed the direction. PATCH2 only notes the effect digest is the general canonical_operation form, "for the intended act" already implies per-act operation
12	rs5b/03 (candidate models), rs5b/05	dependent shorthand "effect/authorization intent"	OK	not reopened (Codex §6); PATCH2 does not touch the candidate models or the 13-element packet structure
13	rs4a-patch2/02 §1	operation = "register_dot" (# fixed canonical operation) and canonical_target_dot_code	OK (domain-scoped)	remains valid as the register_dot specialization of the general formula (PATCH2-02 §6); must NOT be used as the general RS5B founding formula
14	(whole KB)	canonical_operation	introduced-by-PATCH2	the term does not pre-exist (KB search returns no defining document); PATCH2 introduces it at design level only; vocabulary REQUIRED_NOT_PRESENT

4. Minimum-supersede checklist (from the mandate)

• ✅ RS5B-PATCH1-02 formula with operation="register_dot" → SUPERSEDED (rows 1–2).
• ✅ RS5B-PATCH1-04 BI-E1/BI-E6 overlapping domain → SUPERSEDED / refined (rows 4–6).
• ✅ RS5B-PATCH1 decision/codex packet repeating the old formulation → pointer-superseded (row 9); files not overwritten.

5. Non-reopening attestation

PATCH2 does not modify or reopen: the accepted authorization_binding_digest field set (row 3), the binding-direction fix (rows 10–11), RS5B candidate models / 13-element packet (row 12), RS4A-PATCH2 register_dot semantics (row 13), RS5A-PATCH4 quorum/G02/total-Q-order, owner/bootstrap/handler posture, or U1/U2/U3. All superseded items are wording/pointer changes carried additively in the PATCH2 files; the original files retain their content and revisions.

REGISTRATION_HOLD retained · CAN_PROCEED = NO · 0 mutations.