KB-158C

RS5A-01 — Codex RS4A-PATCH2 Acceptance and Caveat Register — 2026-06-21

4 min read Revision 1
rs5ag2codex-acceptancecaveat-registerregistration-holddesign-only2026-06-21

RS5A-01 — Codex RS4A-PATCH2 Acceptance and Caveat Register — 2026-06-21

Macro: RS5A · Mục tiêu 0.1 · Deliverable: 01 of 15 · design-only Gate carried unchanged: REGISTRATION_HOLD · REGISTRATION_CAN_PROCEED = NO Class: read-only; non-enacting; non-authorizing; no implementation; no runtime mutation.

1. Controlling acceptance read directly from KB

Source: knowledge/dev/laws-new/reports/codex/codex-review-rs4a-patch2-effect-identity-head-uniqueness-suite-id-reconciliation-2026-06-21.md (read in full this macro, revision 1, truncated=false).

Field Value
STATUS PASS_WITH_CAVEATS
VERDICT ACCEPT_RS4A_PATCH2
Stop state RS4A_PATCH2_ACCEPTED
Corrected contract RS4A + RS4A-PATCH1 + RS4A-PATCH2 accepted as design-only contract
Registration gate REGISTRATION_HOLDREGISTRATION_CAN_PROCEED = NO
Runtime observation by Codex NO_CODEX_LIVE_READ
Single next step authorised G2 Owner-of-record decision

Codex confirmed package completeness: 8 files under reports/rs4a-patch2/ + 1 rollup, all revision 1, none empty/missing/truncated. Codex read governing SSOT v7.58 / Constitution v4.6.3 / Incomex skill directly.

2. Caveat register — every caveat is binding on RS5A

These caveats are carried verbatim into RS5A and may not be cleared by this macro.

ID Caveat (from Codex acceptance) RS5A obligation
CV-1 ACCEPT_RS4A_PATCH2 is not runtime approval RS5A produces a decision dossier only; no execution
CV-2 U1/U2/U3, status CHECK, carrier, audit sink, Owner/APR still absent or unproven RS5A re-verifies live (file 02) and keeps each fail-closed
CV-3 No Owner execution RS5A creates no governance_object_ownership row
CV-4 No APR RS5A creates no approval_requests / apr_approvals row
CV-5 No register_dot RS5A designs the action contract; does not create the action type
CV-6 No implementation RS5A authors contract/test artifacts only
CV-7 No registration REGISTRATION_HOLD retained end-to-end

3. What "G2 Owner-of-record decision" means here

G2 is the deciding-authority blocker first opened in RS3B/RS4A (governance_object_ownership = 0 ⇒ no Owner-of-record ⇒ fail-closed). Codex authorised a decision dossier for that blocker — i.e. what the Owner-of-record must be, where it is drawn from, the conditions to become an accountable head, and how register_dot authority is boundnot the execution of the decision.

RS5A is therefore explicitly a decision package, not an execution package. The boundary between "designate" (Owner action, out of scope) and "design the designation contract" (RS5A) is the central safety line of this macro.

4. Non-reopening clause

RS5A does not reopen any RS4A / PATCH1 / PATCH2 part accepted by Codex (effect-identity business-only, authorization-binding-separated, U3 current-head policy, Phase-4 no-success-audit, PX2 registry, count=111). Those are referenced as fixed inputs. RS5A only adds the authority/owner decision layer that Codex named as the single next step.

5. Cross-references

  • Owner concept: [[rs5a-03]] · Scopes: [[rs5a-04]] · Candidate matrix: [[rs5a-05]]
  • register_dot action: [[rs5a-06]] · Authority envelope: [[rs5a-07]] (binds to PATCH2 authorization_binding_digest)
  • Quorum obligations: [[rs5a-08]] · Negative tests: [[rs5a-09]] · Options/rec: [[rs5a-10]] · Decision packet: [[rs5a-12]]
Back to Knowledge Hub knowledge/dev/laws-new/reports/rs5a/01-codex-rs4a-acceptance-and-caveat-register-2026-06-21.md