RS5B-PATCH1 — Codex/GPT Review Packet (Effect/Authorization-Binding Correction) — 2026-06-21

Review request. Verify this narrow wording correction at the contract layer. RS5B-PATCH1 is non-mutating design; acceptance authorizes no runtime act.

1. What RS5B-PATCH1 claims

• Verdict: RS5B_PATCH1_READY_FOR_GPT_REVIEW.
• PASS level: design-review-ready / engineering-design only.
• Gate: REGISTRATION_HOLD retained; REGISTRATION_CAN_PROCEED = NO; 0 runtime mutations.
• Scope: corrects the RS5B-05 item-5 defect and clarifies the dependent effect/authorization intent shorthand in RS5B-03/05; additive; does not overwrite RS5B; does not reopen RS5A-PATCH4.

2. The defect and the fix

• Defect (RS5B-05 item 5): "effect_identity … kept out of the authorization binding (separation)" — inverts the accepted RS4A-PATCH2-02 contract and can permit approval-not-bound-to-effect / authorization-substitution.
• Fix: effect_identity is pure (authority excluded); authorization_binding_digest includes effect_identity and binds it to the authorization envelope. Real separation = authority-out-of-effect, not effect-out-of-binding.

3. Evidence the reviewer can re-check

claim	how to verify
defect is a single occurrence	the phrase "kept out of the authorization binding" appears only in RS5B-05 item 5 (impact map [[03-rs5b-document-impact-map-and-superseded-wording]])
corrected contract matches accepted source	compare [[02-corrected-effect-identity-and-authorization-binding-contract]] to rs4a-patch2/02-effect-identity-with-authorization-binding-separated-2026-06-21.md (read full) — authorization_binding_digest includes effect_identity there too
no fail-open introduced	[[04-codex-style-self-check-and-bad-inputs]] BI-E1..BI-E7 each fail closed
no overclaim	live surfaces still REQUIRED_NOT_PRESENT; REGISTRATION_HOLD retained; design PASS not upgraded

4. Points to adversarially review

1. Direction of binding. Confirm the corrected contract makes authorization_binding_digest include effect_identity (BI-E6) and keeps authority out of effect_identity (BI-E5) — both directions guarded, no opposite hole.
2. Approval-substitution closed. Confirm BI-E4 (same approval, different effect) and BI-E1 (binding without effect) both reject.
3. Scope discipline. Confirm only item 5 is superseded and RS5A-PATCH4 / the rest of RS5B are untouched (no scope drift).
4. Overclaim. Confirm the correction implies no runtime readiness (BI-E7 / AUTHORITY_OVERCLAIM).

5. What acceptance does and does NOT authorize

• Does: confirm the corrected wording is sound and review-ready; allow it to carry into RS5B by reference; permit progression to Codex.
• Does NOT: authorize any write; clear REGISTRATION_HOLD; advance RS5B past its own review gate; substitute for Chairman authorization.

6. Requested outcome

ACCEPT_RS5B_PATCH1 or a specific HOLD/REJECT (…_HOLD_EFFECT_BINDING_STILL_AMBIGUOUS / …_REJECT_SCOPE_DRIFT / …_REJECT_AUTHORITY_OVERCLAIM) with the exact residual. On accept → Codex → corrected item 5 carries into RS5B. Residual ⇒ RS5B-PATCH2.