02 — Open-Axis, IU First-Class & Điều 37 Hub Concepts (One-Roof Concept Canon, Round 4, 2026-06-01)
02 — Open-Axis, IU First-Class & Điều 37 Hub Concepts
Tier: Concept / principle only. Technical implementation DEFERRED. No axis store, no IU surface/owner-binding, no envelope generalization, no DOT, no UI designed here. Source: Round-4 docs 05/06/10. DRAFT clause cards — not enacted, not version-bumped.
1. Open-axis model [Đ37 §4.15-quater — OWN]
M-DEF-8 — An axis is a governed object
- VN: Một trục (axis) là chiều bất kỳ mà các đối tượng được phân loại / đếm / nhóm / pivot / sắp / liên hệ / hiển thị theo đó. Trục khác với đối tượng nó tổ chức và bản thân là một đối tượng được quản trị (hồ sơ
AXIS). Thành viên = phép thử sự-thật-chung áp lên việc đổi định nghĩa / từ vựng / chính sách nhóm của trục. - EN: An axis is any dimension along which objects are classified / counted / grouped / pivoted / ordered / related / displayed. An axis is distinct from the objects it organizes and is itself a governed object (profile
AXIS). Membership applies the shared-truth test to changing the axis's definition / vocabulary / grouping policy. - Test: a new pivot group-by on an unregistered dimension →
axis_unregistered. - Blocker: none at concept; SB-3 at the IU substrate (see §3).
Why "open". The model deliberately admits future axes that do not exist yet. A 4th, 5th, … axis is not a special case requiring code; it is the same governed-object contract applied to a new dimension. There is no fixed axis array anywhere in the concept model.
2. Axis Registry concept [Đ37 §4.15-quater; REF Đ2/Đ0-G — OWN model]
M-DEF-9 — the Axis Registry
- VN: Sổ Đăng ký Trục là một sổ đăng ký được quản trị (Lớp 2) liệt kê mọi trục đang hoạt động theo chín thuộc tính (mã trục, họ trục, chủ-mỗi-phạm-vi, phạm vi, sổ-nguồn-từ-vựng, chính-sách-nhóm, quy-tắc-phủ, đường-sự-cố, vòng đời). Trục tương lai = một dòng mới (dữ liệu). Không có mảng trục cố định ở bất kỳ đâu. Vắng mặt chính nó =
inventory_gap(critical). - EN: The Axis Registry is a Class-2 governed registry enumerating every active axis by nine attributes (axis_code, axis_family, owner-per-scope, scope, vocabulary-source-registry, grouping-policy, coverage-rule, issue-path, lifecycle). It is the ground-truth axis inventory. A future axis is a row, never a schema change. The registry's own absence =
inventory_gap(critical). - Test: an axis-bearing surface absent from the registry →
axis_unregistered; the registry itself absent →inventory_gap. - Blocker: SB-2 (axis ownership is born/owned via the object-ownership edge, which the live
governance_relationsCHECK forbids — concept references the model; apply waits); SB-3 (the IU envelope). Vocabulary homes stay specialized (Đ24 label vocab, Đ26 pivot, Đ0-B species, Đ39 KG, Đ44 IU axes) — see §5.
3. IU as a first-class governed domain [Đ37 §4.15-e; REF Đ44/Đ38 — OWN concept; surface/owner HELD]
CLAUSE — IU first-class (concept only)
- VN: Đơn vị Thông tin (miếng thông tin) là một lĩnh vực được quản trị hạng nhất; mọi lớp IU ánh xạ tới một hồ sơ phủ + một chủ chịu trách nhiệm mỗi phạm vi; IU tái dùng mái che trung tâm và không được duy trì đảo quản trị. Ba trục hiện tại (nguồn/gốc, chuyên-ngành, cha-con-cháu) là ví dụ, không phải danh sách đóng; trục IU tương lai = dòng Sổ Trục. Bất biến IU không-miễn-trừ: tái-dựng, toàn-vẹn-quan-hệ, nhất-quán-vector, phủ-quản-trị.
- EN: The Information Unit (miếng thông tin) is a first-class governed domain; every IU class maps to a coverage profile + one accountable owner per scope; IU reuses the central roof and must not maintain a governance island. The current 3 axes (origin/source, specialization, parent-child-grandchild) are examples, not a closed list; a future IU axis is an Axis-Registry row. Non-exemptable IU invariants: reconstruction, relation-integrity, vector-consistency, governance-coverage.
- Test: an IU cut that breaks reconstruction →
reconstruction_integrity_fail; vector not reindexed →iu_vector_drift.
HELD — out of scope for this concept canon (do NOT design here):
- OP-B — the IU family has no accountable owner assigned (no
GOV-IUagency;owner_refis free-text on all 219 IUs;conformance_status='open'on all 219). IU owner-binding and IU surface design are NO-GO until the council assigns the owner-per-scope and the sovereign ratifies (C-3 / H-2).- C-4 — whether IU's internal
review_decision_idcounts as a governed approval-adapter exception or must route through central Đ32 is a council decision; recorded, not designed here.- SB-3 — the live
iu_three_axis_envelopehardcodes exactly three axes (axis_a_*,axis_b_*,axis_c_*; 216 rows). The "no fixed axis array" claim is therefore contradicted at the IU substrate today. Generalizing it (Axis Registry as ground truth; a genericiu_axis_value(unit_id, axis_code, value, …)store keyed byaxis_code; envelope demoted to a hot-cache projection) is IU technical design, DEFERRED to a later tier after OP-B. Concept-true now; substrate-false until generalized.
4. Điều 37 hub model — Own / Reference / Specialize [OWN]
Principle: Điều 37 owns the definitions and the contract; specialized laws keep their mechanisms and reference Đ37. Exactly one roof; Đ37 does not absorb every law (anti-bloat).
Disposition vocabulary: OWN (define directly in Đ37) · REFERENCE (Đ37 names it + points to the specialized law) · SPECIALIZE (stays in the specialized law; Đ37 cross-links) · EXCLUDE (not law — config/registry/CI) · DEFER.
4.1 What Đ37 OWNs (the centralization list)
The One-Roof principle · the governed-object definition + 13 classes + Class 0 · the count>1 rule · governance-orphan/anarchic + 12 gap types · the local-island rule · the accountable-owner / responsibility-scope model · the governed-exception contract · the open-axis model + Axis Registry contract · the coverage invariant v3 · the detection obligation · the readiness gate · and the §0-GOV hook. These are definitions and contracts — the shared vocabulary the whole system reconciles against.
4.2 What stays SPECIALIZED / REFERENCED (anti-bloat)
Đ37 must NOT absorb the mechanisms; it references them:
| Topic | Disposition | Home |
|---|---|---|
| Detector mechanism | REFERENCE | Đ31 (System Integrity) + Đ19 (orphan scanner) |
| DOT scan/propose/apply/audit lifecycle | SPECIALIZE | Đ35 (DOT governance) + GOV-DOT; dot_coverage_required rows |
| Approval spine | REFERENCE | Đ32 + apr_action_types (needs SB-1/C-2) |
| Event/queue substrate (register-before-emit) | REFERENCE | Đ45 + system_issues/event_type_registry (needs L-2 registration) |
| Audit substrate | REFERENCE | governance_audit_log (activate, dormant) + registry_changelog + event_outbox |
| DOT linkage | REFERENCE | Đ35 + dot_tools (paired_dot) |
| Label vocabulary | REFERENCE | Đ24 (Label Law) |
| Pivot mechanics | REFERENCE | Đ26 (Pivot/Counting) |
| Species / composition | REFERENCE | Đ0-B |
| Knowledge graph | REFERENCE | Đ39 |
| Birth registry | REFERENCE | Đ0-G / Đ19 |
| Display / render | REFERENCE | Đ28 (agency-orphaned today → C-5) |
| IU schema / axes | REFERENCE | Đ44 (draft) / Đ38 |
| Host / deploy | REFERENCE | Đ41 |
This preserves one roof without one giant law.
5. Specialized-law reference pattern [Đ37 cross-link — PATTERN]
- VN: Luật chuyên ngành giữ cơ chế của mình và tham chiếu Đ37 cho định nghĩa/hợp đồng; Đ37 không sao chép cơ chế. Mỗi luật chuyên ngành mang một dòng tham chiếu Đ37 + khối §0-GOV.
- EN: Specialized laws keep their mechanisms and reference Đ37 for definitions/contracts; Đ37 never duplicates a mechanism. Each specialized law carries a single Đ37-reference line + a §0-GOV block. (The full specialized-law → Đ37 patch matrix, Đ0-G..Đ45, lives in Round-4 doc 07 and is content-only / law-tier, not patched here.)
- Test: Đ26's pivot group-by references the Đ37 axis model, not its own.
- Reference example (concept): the Registries-Pivot surface design (
…/registries-pivot-os-agency/) consumes Đ26 (pivot), Đ24 (label), Đ28 (render), Đ31/Đ45 (issue/event), Đ19/Đ23 (orphan/scan) — each of which references this canon's governance contracts rather than minting local ones. The surface design's Round-4 concept-patch sections point back here.
Cross-tier note
§§1–2 (open-axis + Axis Registry) and §4 (Đ37 hub) are concept-ready now. §3 (IU first-class) is concept-ready only at the coverage-contract level; its owner-binding, surface, approval-adapter, and axis-envelope generalization are all HELD behind OP-B / C-4 / SB-3 and are not designed in this canon. See doc 03 for the full blocker register and the readiness gate.