RS-TKT-0A-PATCH1 · 03 — Source Authority Status Hierarchy Patch (P3)

Lane: RS-TKT-0A-PATCH1 · Date: 2026-06-21 Gate: REGISTRATION_HOLD · REGISTRATION_CAN_PROCEED = NO · 0 runtime mutations (KB writes only) Authority: NON_AUTHORITY · may_gate=false · decision_effect=NONE · design-only

Supersedes: the wording in 02 §0/§1 and 00/08 that called the three matrix-refactor files "laws-new SSOT" / "binding" / "current and binding" without a draft qualifier.

---

1. The defect (Codex P3, BLOCKER)

The three matrix-refactor documents (matrix-refactor-implementation-plan.md, matrix-refactor-quick-rules.md, matrix-stamp-governance-addendum.md) explicitly declare themselves DRAFT / not enacted, yet RS-TKT-0A leaned on them as "binding laws-new SSOT." DRAFT planning files are not enacted authority. MCB-6 (no single enacted laws-new architecture doc) cannot be closed by inference.

2. Corrected three-tier source hierarchy

Tier 1 — ENACTED AUTHORITY (binding):
  Constitution v4.6.3 (BAN HÀNH)
  enacted laws (e.g. law-01-foundation-principles, … as enacted)
  OR v7.58 operating control (operating-rules.md)

Tier 2 — laws-new DRAFT PLANNING SSOT (controlling within the draft workspace only):
  matrix-refactor-implementation-plan.md      (DRAFT / not enacted)
  matrix-refactor-quick-rules.md              (DRAFT / not enacted)
  matrix-stamp-governance-addendum.md         (DRAFT / not enacted)

Tier 3 — WORKING DESIGN / PILOT / REPORTS (inputs, not authority):
  new-iu docs · lego-pilot-slice docs · RS reports · TKT survey/patch docs (this package)

Precedence: Tier 1 overrides Tier 2 overrides Tier 3 on any conflict. Nothing in Tier 2/3 self-authorizes or overrides enacted law.

3. Corrected wording rule

• Do NOT say: the matrix-refactor files are "binding laws-new SSOT" / "binding enacted law."
• DO say: they are "controlling design inputs within the laws-new planning workspace, subject to Owner/Codex acceptance" (Tier 2). They constrain the draft design; they do not bind the enacted system.
• Anywhere RS-TKT-0A cited a Tier-2 file as the reason a TKT property is required, the requirement still stands as a draft-workspace design input, not as enacted law. The TKT properties themselves (NON_AUTHORITY, no-mega-X, fail-closed, HOLD-preserving) are also consistent with Tier-1 enacted authority, which is their ultimate backing.

4. Re-grounding of the RS-TKT-0A requirements (02)

RS-TKT-0A requirement	Stated tier-2 basis (draft)	Tier-1 enacted backing
R-TKT-3 no mega-registry/graph/birth	quick-rules R20, New IU §9 (Tier 2/3)	Constitution one-roof / SSOT discipline (Tier 1)
R-TKT-6 verdict-only / non-mutating	stamp addendum F4 (Tier 2)	OR v7.58 + Constitution: no unauthorized mutation (Tier 1)
R-TKT-8 no authority overclaim	quick-rules R20 (Tier 2)	Constitution: authority reserved to Owner/Council (Tier 1)
R-TKT-9 no semantic PASS without IU	TaC DEFER (Tier 2/3)	Constitution: no overclaim (Tier 1)

The requirements do not weaken; only their source label is corrected from "binding law" to "Tier-2 draft input with Tier-1 backing."

5. MCB-6 status

MCB-6 remains OPEN. It can be closed only when Owner/Codex confirms a current authoritative laws-new architecture baseline (i.e., promotes a Tier-2 draft to enacted, or names the enacted baseline). Until then, the TKT plan reads against the three-tier hierarchy and treats the matrix-refactor files as Tier-2. This is recorded as a carry-forward caveat in 08; it does not block Phase-1 design (which is itself a draft-workspace activity), but Phase-1 acceptance should note MCB-6 as unresolved.