02 — Source Map: Current vs Reference vs Superseded

Purpose: stop future agents from reading old technical docs as current implementation truth. Every source below carries a classification, why, allowed use, and forbidden use. When in doubt, prefer the highest-priority CURRENT source from doc 01 and STOP if a doc's classification conflicts with how someone is asking you to use it.

2.1 Classification legend

Code	Meaning
CURRENT_CONTROLLING	Active truth for wording/decisions; cite and obey.
CURRENT_CONCEPT_CANON	Active concept truth (definitions/contracts); reconcile against it; read-only from implementation.
TECHNICAL_REFERENCE_ONLY	Describes live substrate / prior technical work; useful as evidence, not as a governance-concept mandate.
HISTORICAL_REFERENCE_ONLY	Earlier-round provenance; read for lineage, not for current wording.
SUPERSEDED_BY_ROUND4	Its wording/decisions are replaced by Round 4; do not cite as current.
DO_NOT_USE_FOR_IMPLEMENTATION	Must not drive any build (deferred/held content, or stale/conflicting text).
BLOCKER_SOURCE	The evidence base for an open blocker; read to scope the blocker, never to justify proceeding past it.

2.2 The map

Path / folder	Classification	Why	Allowed use	Forbidden use
knowledge/dev/laws/prompt-muc-tieu-mo-for-claude-code.md	CURRENT_CONTROLLING	House operating constitution (no-hardcode, design-only macro, hard gates).	Govern how every macro runs.	Treating it as governance-domain content.
This package …/one-roof-governance-technical-addendum-and-implementation-index-2026-06-01/	CURRENT_CONTROLLING	The active implementation entrypoint.	Start here; write new docs here.	Bypassing it to start from old docs.
knowledge/dev/design/one-roof-governance-concepts/ (00–03)	CURRENT_CONCEPT_CANON	The canonical concept home; definitions/contracts.	Reconcile all design against it; cite M-DEF-1..10, §0-GOV, count>1, open-axis, IU-first-class, invariant v3, Điều 37 hub.	Editing it as part of an implementation track; inferring substrate/DOT/UI from it.
…/one-roof-governance-law-hardening-finalization-round4-2026-06-01/ (00–13)	CURRENT_CONTROLLING	Latest hardened law/clause DRAFT + closed open-question ledger + blocker defs + live-PG snapshot.	Cite clause wording (doc 10), blockers (doc 02/08/11), next prompts (doc 12).	Treating its clauses as enacted; they are DRAFT.
…/patch-canonical-design-one-roof-concepts-round4-2026-06-01/ (00–08)	CURRENT_CONTROLLING (provenance/report)	Record of how the concept canon was produced under CONDITIONAL GO.	Provenance; input to external critique.	Using it instead of the live canon (S2) if they ever diverge — the canon wins.
…/gpt-review-round4-one-roof-governance-ready-for-concept-design-patch-2026-06-01.md	CURRENT_CONTROLLING (external concurrence)	Independent confirmation: concept patch OK; technical/enactment/IU-surface/remediation NOT.	Cite as concurrence; feed the critique prompt.	Reading it as authorizing more than the concept tier.
knowledge/dev/design/registries-pivot-os-agency/ — patched docs 00, 04, 06, 07, 08, 12	CURRENT_CONTROLLING (surface)	These carry the concept-canon references (count>1 dual-sense, grouping-as-governed-axis, orphan/island channel, pin scope→Class-0, 4-phase gate).	Drive the Registries-Pivot integration track (T9).	Reading their technical passages as a buildable governance binding without going through the blockers.
knowledge/dev/design/registries-pivot-os-agency/ — un-patched docs 01/02/03/05/09/10/11/13	TECHNICAL_REFERENCE_ONLY	Surface/technical design that predates the concept patch; some describes shipped substrate.	Evidence about the live surface and data contract.	Using as current governance-concept truth; implementing governance binding from them.
knowledge/dev/design/iu-mow-mot-event-foundation-design.md — IU-first-class concept sections	CURRENT_CONCEPT_CANON	IU recognized as first-class governed object (IU-GOV-1..5).	Cite the IU-first-class concept (T10 / OP-B packet).	—
same file — IU owner-binding / approval-routing / 3-axis-envelope sections	DO_NOT_USE_FOR_IMPLEMENTATION	HELD/DEFERRED behind OP-B (C-3), C-4, SB-3.	Read to scope the deferred work.	Building owner-binding, review_decision routing, or axis generalization from them now.
…/one-roof-governance-decision-pack-2026-06-01/ (Round 1)	SUPERSEDED_BY_ROUND4 / HISTORICAL_REFERENCE_ONLY	Round-1 governed-object contract; superseded by hardened M-DEF wording. Useful fact: ownership is relational (no owner_gov_code column).	Lineage; the relational-ownership fact.	Citing its clause wording as current.
…/one-roof-governance-clause-review-hardening-2026-06-01/ (Round 2)	SUPERSEDED_BY_ROUND4	Round-2 adversarial hardening; folded into Round 3/4.	Lineage of contradictions found.	Citing its wording as current.
…/one-roof-governance-hardening-revision-all-domains-all-axes-2026-06-01/ (Round 3)	SUPERSEDED_BY_ROUND4	Round-3 source of M-DEF-1..9 / open-axis / IU-first-class / Điều 37 hub — but Round 4 is the controlling finalization.	Lineage; deep rationale.	Citing its wording where Round 4 differs.
Governance-alignment fact-finding / audit reports (…full-stack-governance-alignment-audit…, …governance-alignment-followup-fact-finding…)	TECHNICAL_REFERENCE_ONLY	Read-only live-substrate evidence (ownership is relational; CHECK ∈ {law,agency}; APR action-types; approval spine).	Substrate evidence to scope SB-1/2 and ownership model.	Treating point-in-time live counts as current without re-verifying; deriving concept truth from them.
Registries-Pivot ship / macro reports (all project_registries_pivot_* packages)	TECHNICAL_REFERENCE_ONLY + HISTORICAL_REFERENCE_ONLY	Record what the Registries-Pivot surface shipped (route, Nitro endpoints, views, no-hardcode findings).	Evidence of the live surface for T9 integration.	Reading them as a governance-binding spec or as current governance concept truth.
Enacted law files under knowledge/dev/laws/ (Đ37 v3.3, Đ31/35/36/45, etc.)	BLOCKER_SOURCE (L-1/L-2)	Their text drifts from Round-4 wording and live columns; Đ20/23/44/45 unregistered.	Read as drift evidence for the law-cleanup track (T1).	Following stale text as current; patching/enacting them outside the gated T1→human-enact path.
Live directus PG (read-only)	BLOCKER_SOURCE	Substrate evidence for SB-1..9 (action-types, CHECK, axis envelope, approvals, event types).	Read-only verification to scope a blocker.	Reading a count in isolation as a mandate; any committed mutation.

2.3 The trap this map prevents

The most likely future error is an agent finding a Registries-Pivot technical doc or a live PG observation and treating it as the current governance design. Those are TECHNICAL_REFERENCE_ONLY / BLOCKER_SOURCE. The current governance design is the concept canon (S2) plus the Round-4 hardened clauses (S3), and no buildable governance binding exists yet — it is blocked (doc 03). Likewise, an agent finding Round 1/2/3 wording must treat it as SUPERSEDED_BY_ROUND4. And the IU owner/axis sections are DO_NOT_USE_FOR_IMPLEMENTATION until OP-B and SB-3 clear.