RS5B-PATCH2 — Codex/GPT Review Packet (Canonical Operation and BI Domain Separation) — 2026-06-21

For: GPT review first; then Codex review. Verdict requested on: RS5B-PATCH2 only.

1. Summary

• Verdict: RS5B_PATCH2_READY_FOR_GPT_REVIEW (not forced).
• PASS level: design-review-ready / engineering-design only.
• Gate: REGISTRATION_HOLD retained; REGISTRATION_CAN_PROCEED = NO; 0 runtime mutations (KB-only, design-only).
• Scope: closes exactly the two residuals from Codex NEED_RS5B_PATCH2. Additive; does not overwrite RS5B-PATCH1 or RS5B; does not reopen the accepted authorization_binding_digest field set, RS5A-PATCH4, owner/bootstrap/handler, U1/U2/U3, or registration prerequisites.

2. Residuals closed

• R1 (Codex §4, §10.1): RS5B-PATCH1-02 §2 hardcoded operation="register_dot" in the general founding effect_identity. Fix: general formula uses canonical_operation (governed action/effect type per act) and a generalized target pair (canonical_target_object_type, canonical_target_object_ref). register_dot is the example value for register_dot admission only; founding owner-designation and scope creation are distinct operations → distinct effect identities; authority changes do not mint a new effect; vocabulary REQUIRED_NOT_PRESENT (no rows invented). Purity unchanged. → PATCH2-02.
• R2 (Codex §7, §10.2): RS5B-PATCH1-04 BI-E1 and BI-E6 overlapped (both "binding lacks effect") with different codes. Fix: two-layer disjoint domains — BI-E6 = digest-shape (schema omits effect; Layer 1, first) → AUTHORIZATION_BINDING_MISSING_EFFECT; BI-E1 = approval/evidence binding (schema has effect, approval not bound to it; Layer 2) → APPROVAL_NOT_BOUND_TO_EFFECT_IDENTITY. Disjoint by predicate P; secondary precedence MISSING_EFFECT < NOT_BOUND; oracle total. → PATCH2-03, PATCH2-05.

3. What reviewers should verify

1. Operation genericity (R1). Confirm no general effect_identity formula contains operation="register_dot", and that register_dot appears only as the register_dot-admission example / specialization (PATCH2-02 §1, §3, §6). Expect WRONG_CANONICAL_OPERATION_FOR_EFFECT for a founding act mislabeled register_dot (OP-BI-1/2), and AUTHORITY_CHANGE_IS_NOT_NEW_EFFECT for authority-only change (OP-BI-3).
2. Vocabulary honesty (R1). Confirm CANONICAL_OPERATION_VOCABULARY_REQUIRED_NOT_PRESENT is declared and no canonical-operation rows are invented (PATCH2-02 §4; OP-BI-4).
3. BI disjointness (R2). Confirm no single malformed input can match both BI-E1 and BI-E6 — the predicate P = (effect_identity ∈ digest input schema) partitions inputs and the layers are ordered (PATCH2-03 §2–§3; PATCH2-05 §1).
4. Purity preserved. Confirm effect_identity still excludes authority/credential/execution fields incl. founding_authority_ref (BI-E5 / EFFECT_IDENTITY_IMPURE).
5. Binding direction unchanged. Confirm authorization_binding_digest still REQUIRES effect_identity (BI-E6) — the accepted PATCH1 direction is not reversed.
6. No overclaim / no mutation. Confirm design PASS is not promoted to authority/runtime/registration PASS (BI-E7 / AUTHORITY_OVERCLAIM), and REGISTRATION_HOLD is retained.
7. Scope discipline. Confirm only the two residuals are touched; RS5A-PATCH4 quorum/G02/total-Q-order and the RS5B candidate models / 13-element packet are untouched (PATCH2-04 §5).

4. Files in this package (additive)

rs5b-patch2/: index · 01 closure-map · 02 canonical-operation (R1) · 03 BI-domain-separation (R2) · 04 impact-map · 05 self-check/bad-inputs · 06 decision-packet · this review packet; plus ../macro-rs5b-patch2-… rollup.

5. Requested outcome

ACCEPT_RS5B_PATCH2 or a specific stop state with the exact residual:

• RS5B_PATCH2_HOLD_OPERATION_STILL_HARDCODED
• RS5B_PATCH2_HOLD_BI_DOMAIN_STILL_OVERLAPS
• RS5B_PATCH2_REJECT_SCOPE_DRIFT
• RS5B_PATCH2_REJECT_RUNTIME_MUTATION
• RS5B_PATCH2_REJECT_AUTHORITY_OVERCLAIM

On accept → the canonical-operation formula and layered BI domains carry into RS5B; the only next step is GPT→Codex review, not P2/runtime/registration. Residual ⇒ RS5B-PATCH3.

REGISTRATION_HOLD remains active. REGISTRATION_CAN_PROCEED = NO.