KB-206A

RS5A-11 — LEGO Boundary and Non-Mega Coupling Check — 2026-06-21

4 min read Revision 1
rs5ag2lego-boundaryno-mega-systemcoupling-check2026-06-21

RS5A-11 — LEGO Boundary and Non-Mega Coupling Check — 2026-06-21

Macro: RS5A · Mục tiêu 3.11 · Deliverable: 11 of 15. Claim under test: RS5A introduces no mega-system. Every block is born / tested / changed / rolled back separately and joined only by explicit contract.

1. Anti-mega assertions

forbidden mega-pattern RS5A status evidence
mega-registry (one table/owner for all authority) avoided reuses existing governance_object_ownership (1 row per scope), governance_registry, governance_responsibility_scope; creates no new registry
mega-graph (universal-edges-style coupling) avoided scopes joined by named admission edges ([[rs5a-04]] §3), not a graph; no universal_edges use
mega-birth pipeline (one pipeline mints everything) avoided each ownership row, scope, and action is an independent governance act; register_dotactivate_dotassign_governance_owner
mega-owner (one head owns all scopes) avoided by design, allowed only if explicitly bound Option B splits heads; MUST_NOT_IMPLICIT_INHERIT ([[rs5a-04]] §1/§4)

2. Per-block separability ledger

block born by tested by changed by rolled back by coupling to others
Owner concept ([[rs5a-03]]) role lattice doc A/B test groups edit role rules revert doc reject codes only
9 object scopes ([[rs5a-04]]) one scope_code + ownership row each C/H/I groups per-scope supersede per-row rollback_ref explicit admission edges
candidate matrix ([[rs5a-05]]) governance_registry read re-evaluate feeds Option B
register_dot action ([[rs5a-06]]) one apr_action_types row D/E/F groups deprecate/retire retire action FK to action types
authority envelope ([[rs5a-07]]) attempt-record digest E/G groups re-version envelope drop digest references U1, never mutates it
quorum obligations ([[rs5a-08]]) existing functions F group re-bind approval predicate only

3. Coupling edges are explicit (not implicit)

  • registration → activation: explicit separate action+scope (never implicit) — defeats "register ⇒ active".
  • effect_identity (U1) ↔ authority envelope: reference only; authority never re-enters U1 ([[rs5a-07]] §1).
  • ownership → scope/head: FK edges (scope_fkey, owner_gov_code_fkey) — DB-level, explicit.
  • head-uniqueness: one partial unique index per (object,scope) — not a global lock.

4. Rollback isolation proof

Each ownership row carries its own rollback_ref; lifecycle_status supersession is per-row. Revoking the head of DOT_ACTIVATION_AUTHORITY does not touch DOT_REGISTRATION_AUTHORITY (no shared row, no cascade). Retiring register_dot (status='retired') does not retire register_axis. ⇒ rollback is block-local.

5. Verdict

LEGO_BOUNDARY_HELD — no mega-registry, no mega-graph, no mega-birth pipeline, no forced mega-owner. RS5A is additive at the contract layer and decomposable at the substrate layer.

Back to Knowledge Hub knowledge/dev/laws-new/reports/rs5a/11-lego-boundary-and-non-mega-coupling-check-2026-06-21.md