RS5A-PATCH1-03 — Bootstrap Authority and Next-Step Correction — 2026-06-21

Macro: RS5A-PATCH1 · Mục tiêu B + R2 · Deliverable: 03 of 10. Supersedes: every RS5A phrase of the form "the Owner-of-record executes / the Owner makes the G2 designation on accept" — RS5A-12 §6, RS5A-10 §4, RS5A-index §3, rollup §6, codex-packet §5.

1. The circularity Codex identified

RS5A required, to create the first ownership row, an applied assign_governance_owner APR — but ([[rs5a-02]] live):

• governance_object_ownership = 0 ⇒ no bound Owner exists;
• assign_governance_owner.handler_ref = 'unimplemented' ⇒ fn_apr_block_unimplemented_handler blocks it at →applied;
• therefore no entity can execute the G2 designation merely because RS5A is accepted. Instructing "the Owner executes on accept" is circular bootstrap + execution drift.

2. Corrected next-step wording (authoritative)

On ACCEPT_RS5A_PATCH1: proceed to RS5B — G2 Owner-of-record execution-design / authorization-design.

• RS5B is non-mutating unless separately authorized later.
• RS5B must solve bootstrap authority (how the first accountable head is legitimately created when none exists and the mint action is unimplemented).
• RS5B must not create Owner / scope / APR / register_dot by default.

This replaces "Owner executes/performs G2 designation on accept" everywhere.

3. Bootstrap unresolved-state markers (carried, fail-closed)

marker	meaning
BOOTSTRAP_AUTHORITY_UNRESOLVED	no legitimate path exists today to mint the first accountable head
OWNER_MINT_PATH_FAIL_CLOSED	assign_governance_owner unimplemented + apply-time block ⇒ mint blocked
G2_EXECUTION_REQUIRES_SEPARATE_AUTHORIZATION	Codex acceptance of a design is not authorization to execute it

Explicit statements (required by Codex §4/§14):

• There is no bound Owner today.
• assign_governance_owner is unimplemented.
• Therefore no entity may execute G2 designation merely because RS5A (or this PATCH1) is accepted.
• Codex acceptance of RS5A-PATCH1 authorizes only producing RS5B (design) — not any write.

4. What RS5B must solve (scope statement, not solution)

RS5B (a later, separately-authorized macro) must design — design only — the legitimate bootstrap: e.g. how a constitutional/founding authority or an out-of-band governed act could create the first assign_governance_owner capability or the first accountable head, with audit, rollback, and a read-only dry-run, then present a Codex/Owner authorization packet. RS5B writes nothing by default; any mutation needs its own separate authorization gate (P2 in [[rs5a-patch1-02]]).

5. Status

BOOTSTRAP_AUTHORITY_UNRESOLVED is acknowledged, not hidden ⇒ the HOLD state …UNRESOLVED_BUT_UNACKNOWLEDGED does not apply. R2 CLOSED (fail-closed): next step is RS5B design + separate authorization, never immediate execution.