dot-iu-cutter v0.1 — Đ24 Vocabulary Closure Package

Date: 2026-05-15 Status: PROPOSED_FOR_DIEU24_RATIFICATION Trigger: Council Ratification Outcome (5 governance gaps ratified_with_notes) → Đ44 + Đ24 parallel closure phase Baseline: rev5d §3, §13.2.4, criterion 39 + D2/D6/D9/D11 design + 5 governance closures Scope: GOVERNANCE CLOSURE PROPOSAL ONLY. No code, no DDL, no SQL, no migration, no PG mutation, no Qdrant mutation, no schema change, no P0 Migration Design.

1. Hard Boundaries

no_code: true
no_ddl: true
no_sql: true
no_schema_change: true
no_migration: true
no_pg_mutation: true
no_qdrant_mutation: true
no_implementation: true
no_p0_migration_design_started: true
no_previous_file_modified: true
no_design_or_planning_or_closure_or_ratification_file_modified: true
package_purpose: prepare_dieu24_vocabulary_ratification_only

2. Đ24 / Vocabulary Status Statement (binding)

no_silent_vocabulary_invention: true
no_parallel_taxonomy: true
skos_conceptual_only: true (rev5d §13.1.2)
audience_vocabulary_is_access_control_critical: true (rev5d §14.2 + G-5)
wrong_audience_result_is_high_risk: true (Decision 6 + G-5)
controlled_authority: Đ24 governance
this_package_creates_vocabulary: false
this_package_proposes_vocabulary_for_dieu24_to_ratify: true

Per rev5d §13.2.4 + criterion 39: Đ24 is the binding vocabulary authority. This package proposes vocabulary entries for Đ24 governance to ratify or formally confirm; it does NOT mint terms.

Per rev5d §13.1.2: SKOS is conceptual only. v0.1 does NOT introduce RDF/SPARQL/triple-store. Operational vocabulary is Đ24-controlled.

3. Purpose

Liệt kê 11 vocabulary groups mà Đ24 governance phải ratify (hoặc xác nhận đã có sẵn) trước khi P0 Migration Design phase mở. Mỗi group được mô tả: purpose, source, used-in-design status, Đ24 status, risk class, P0/P1/P2/P3 relevance.

4. Vocabulary Groups Summary Table

#	Vocabulary group	Source deliverables	Đ24 status	Risk	P0/P1/P2/P3
1	Manifest enums (umbrella)	D2 §4.2	needs Đ24 ratification	Standard	P0
2	section_type / unit_kind	D2 §4.4, D6 §4.8	partially existing; needs Đ24 confirm + extensions	Standard	P0
3	body_source_policy	D2 §4.5	needs Đ24 addition	Standard	P0
4	risk_class	D2 §4.8	needs Đ24 ratification (cross-link Đ32)	Standard	P0
5	collision_status	D2 §4.2	needs Đ24 addition	Standard	P0
6	audience classes ⚠️	D11 §4.10, G-5 §2.2	needs Đ24 ratification (HIGH-risk surface)	HIGH	P3 (and gating G-5 final ratify)
7	visibility tiers ⚠️	D11 §4.11, G-5 §2.2	needs Đ24 ratification (HIGH-risk surface)	HIGH	P3 (gating G-5)
8	readiness_state	D11 §4.11, D6 §4.3	needs Đ24 addition	Standard	P3 (P0-1 awareness via authority)
9	publication_state	D11 §4.11	needs Đ24 addition	Standard	P3
10	authority values	D7 §4.3, Đ0-G	needs Đ24 ratification (cross-link Đ0-G)	Standard	P0 (canonical_address authority distinction)
11	event/signal names	D3, D9 §4.8, D11 §4.9, G-2/G-4/G-5	needs Đ24 addition (mix of P-levels)	Mixed (HIGH for `wrong_audience_result`)	P0/P2/P3 (per signal)

Total: 11 groups. 6 are P0-blocking; 5 are P1+ (audience/visibility gate G-5; readiness/publication/event-signals span P0–P3).

5. Vocabulary Groups — Detailed

5.1 Group 1 — Manifest enums (umbrella)

Purpose: Top-level enum vocabulary used in manifest_envelope + manifest_unit_block headers. Sub-groups detailed individually (groups 2–5 below).

Source deliverables:

D2 §4.2 — Header + per-unit field set.

Already used in design: YES — D2 explicitly cites these enums.

Đ24 status: Umbrella status; sub-groups individually need ratification or addition.

Risk class: Standard.

P0 relevance: P0 (covers P0-2 manifest_envelope + manifest_unit_block).

Recommended status: proposed_for_dieu24_ratification_as_umbrella_with_sub_groups.

5.2 Group 2 — `section_type` / `unit_kind`

Purpose: C1A-aligned classification of IUs. section_type = structural role (heading/container/body/etc.); unit_kind = functional class (law/design/requirement/report/runbook/code/test/incident/etc.).

Source deliverables:

D2 §4.4 — Vocabulary discipline.
D6 §4.8 — Vocabulary discipline at axis-2 metadata.
C1A (Đ38-trien-khai) — segmentation law sets boundary rules; section_type drives boundary choices.

Already used in design: YES — extensively cited.

Đ24 status: Partially existing in current operational use; Đ24 must:

Confirm existing enum values.
Ratify formal list (no silent additions during cutter implementation).
Add extensions if cutter requires new section_type / unit_kind (e.g., manifest, governance_event may need new unit_kind values).

Risk class: Standard.

P0 relevance: P0 — P0-2 (manifest_unit_block) cannot proceed without ratified section_type/unit_kind enum.

Vocabulary gap register (rev5d §13.2.4): If MARK encounters a section type not in Đ24's ratified list → emit vocabulary_gap to Decision Backlog Registry; do NOT invent term (criterion 39).

Recommended status: proposed_for_dieu24_ratification. Must close before P0-2 migration design.

5.3 Group 3 — `body_source_policy`

Purpose: Per-unit declaration of body content sourcing: inline / container / referenced / generated.

Source deliverables:

D2 §4.5 — Heading/Container/Body policy.

Already used in design: YES (D2 §4.5 exact enum proposed: inline, container, referenced, generated).

Đ24 status: NEW vocabulary; does not exist in current Đ24 — must be added.

Risk class: Standard.

P0 relevance: P0 — P0-2 (manifest_unit_block) needs body_source_policy enum first-class.

Recommended status: proposed_for_dieu24_addition. Proposed enum values: [inline, container, referenced, generated].

5.4 Group 4 — `risk_class`

Purpose: Đ32 risk classification on manifest header and other artifacts: low / standard / high.

Source deliverables:

D2 §4.8 — Risk gating.
D5 §4.5 — Backlog routing by risk class.
D9 §4.4 — Auto-accept risk gate.

Already used in design: YES (throughout).

Đ24 status: Cross-law with Đ32 — risk_class is fundamentally Đ32's vocabulary. Đ24 must confirm formal enum values that align with Đ32 risk taxonomy.

Cross-law dependency: Đ32 must publish or confirm the canonical 3-level (or N-level) risk class list. Đ24 ratifies the enum after Đ32 confirms.

Risk class: Standard.

P0 relevance: P0 — P0-2 (manifest_envelope risk_class field) + P0-5 (decision_backlog_entry risk field) + P0-6 (review_decision class triggering human review).

Recommended status: proposed_for_dieu24_ratification_cross_law_with_dieu32. Proposed values: [low, standard, high] (subject to Đ32 confirmation).

5.5 Group 5 — `collision_status`

Purpose: Result of MARK collision check on source × revision: none / prior_cut_present / supersedes.

Source deliverables:

D2 §4.2 — Header field.
D1 §4.3 — Source resolution collision check.

Already used in design: YES.

Đ24 status: NEW vocabulary; needs Đ24 addition.

Risk class: Standard.

P0 relevance: P0 — P0-2 (manifest_envelope collision_status field).

Recommended status: proposed_for_dieu24_addition. Proposed values: [none, prior_cut_present, supersedes].

5.6 Group 6 — Audience classes ⚠️ HIGH RISK

Purpose: Access-control identity for retrieval consumers. Decision 3 + G-5: [AI-Agent, Employee, Partner, Customer].

Source deliverables:

D11 §4.10 — Audience-scoped search.
G-5 §2.2 (audience scope ratification path).
Council Ratification Outcome §5.3 (ratified_with_notes; HIGH risk).

Already used in design: YES (D11 §4.10 exact list).

Đ24 status: NEW vocabulary; does not exist in current Đ24 — must be added.

Risk class: HIGH (rev5d §14.2 — access-control is security; G-5 HIGH-risk addendum).

P0 relevance: P3 (audience_filter_policy is P3 schema; not P0). However: Đ24 ratification of this group is GATING for G-5 final operational handoff — even though it's P3 schema, the vocabulary closure must happen before retrieval implementation.

Recommended status: proposed_for_dieu24_ratification_HIGH_RISK. Proposed values: [AI-Agent, Employee, Partner, Customer].

Special rule: Đ24 ratification of audience classes requires cross-law signature with G-5 Access-Control Authority + Đ32 (HIGH-risk class). Đ24 alone cannot ratify silently.

5.7 Group 7 — Visibility tiers ⚠️ HIGH RISK

Purpose: Tiered visibility scheme for each IU / thread / artifact. Decision 3 + G-5: [public, partner, employee, internal, restricted].

Source deliverables:

D11 §4.11 — Filters.
G-5 §2.2 ratified scheme.

Already used in design: YES.

Đ24 status: NEW vocabulary; needs Đ24 addition.

Risk class: HIGH (same reasoning as audience classes).

P0 relevance: P3 (visibility field is P3); but vocabulary closure gates G-5.

Recommended status: proposed_for_dieu24_ratification_HIGH_RISK. Proposed values: [public, partner, employee, internal, restricted].

Special rule: Cross-law with G-5 Access-Control Authority + Đ32; ordering invariant — public ⊂ partner ⊂ employee ⊂ internal ⊂ restricted (more permissive on left; cumulative access tiers).

5.8 Group 8 — `readiness_state`

Purpose: Per-artifact readiness for consumption: draft / under_review / approved / published / superseded.

Source deliverables:

D11 §4.11 — Filters.
D6 §4.3 — axis-2 lifecycle awareness.

Already used in design: YES.

Đ24 status: NEW (or partially existing if Đ24 has lifecycle vocabulary already); Đ24 must confirm.

Risk class: Standard.

P0 relevance: P3 directly; P0 indirectly (P0-1 canonical_address authority distinction may reference readiness).

Recommended status: proposed_for_dieu24_ratification. Proposed values: [draft, under_review, approved, published, superseded].

5.9 Group 9 — `publication_state`

Purpose: Per-artifact publication status: unpublished / published / withdrawn.

Source deliverables:

D11 §4.11 — Filters.

Already used in design: YES.

Đ24 status: NEW or partially existing; Đ24 confirm.

Risk class: Standard.

P0 relevance: P3.

Recommended status: proposed_for_dieu24_ratification. Proposed values: [unpublished, published, withdrawn].

5.10 Group 10 — `authority` values

Purpose: Đ0-G birth gate distinction: enacted / draft / runtime.

Source deliverables:

D7 §4.3 (G5 governance state).
Đ0-G (Birth Gate law).
rev5d §13.2.3 (birth gate base/draft/runtime).

Already used in design: YES (D7 explicitly references this distinction).

Đ24 status: Cross-law with Đ0-G — authority is Đ0-G's vocabulary. Đ24 ratifies enum after Đ0-G confirms.

Risk class: Standard.

P0 relevance: P0 — P0-1 (canonical_address must distinguish authority levels per Đ0-G); enacted vs draft canonical_address resolves differently in collision check (P0-1 §5.1 open decision 3).

Recommended status: proposed_for_dieu24_ratification_cross_law_with_dieu0g. Proposed values: [enacted, draft, runtime].

5.11 Group 11 — Event / signal names

Purpose: Đ24-controlled names for governance / health / security events emitted across the cutter.

Source deliverables:

D3 §4.2 (health signal catalog).
D9 §4.8 (thread missing/wrong-link / anomaly signals).
D11 §4.9 (search-gap signals).
G-2 closure §5.2 (sweep_overdue).
G-4 closure §4.4 (dot_pair_drift, signature_failure).
G-5 closure §1, §5 (wrong_audience_result).

Already used in design: YES (all signals named in design + closures).

Đ24 status: Mostly new — Đ24 must add each signal name as controlled term.

Risk class: MIXED — most are Standard; wrong_audience_result is HIGH (security event class per G-5).

P0 relevance: Mixed; matrix below.

Signal-by-signal table:

Signal	Source	Risk	P0/P1/P2/P3
`sweep_overdue`	G-2 §5.2	Standard	P0 (custodian self-detection; needed pre-implementation)
`dot_pair_drift`	G-4 §4.4	Standard (HIGH if during ops)	P0 (P0-3/P0-4 schema awareness)
`signature_failure`	G-4 §4.4	HIGH (security)	P0 (P0-3/P0-4 schema awareness)
`wrong_audience_result` ⚠️	G-5 §1, §5; D11 §4.9	HIGH	P3 (gating G-5 final)
`user_ai_disagreement`	D9 §4.12; G-1	Standard	P2 (threading)
`expected_artifact_missing`	D9 §4.9	Standard	P2 (threading)
`noisy_retrieval` / `noisy_thread`	D11 §4.9	Standard	P3
`weak_thread` / `missing_thread`	D11 §4.9	Standard	P3
`search_gap`	D11 §4.9	Standard	P3
`high_similarity_unlinked` / `co_retrieval_no_edge` / `cited_without_edge`	D9 §4.8	Standard	P2
`overbroad` / `too_narrow` / `stale` (thread)	D9 §4.8	Standard	P2
`co_citation` / `co_edit` / `co_retrieval` / `edge_density_overlap` / `context_pack_dependency` / `orphan_or_underused_unit` / `misclassification_signal`	D3 §4.2	Standard	P3 (instrumentation gated)
`length_drift` / `overlap_growth` / `user_complaint`	D3 §4.2	Standard	P1/P2
`reviewer_rejection` / `retrieval_noise` / `contradiction`	D9 §4.8	Standard	P2
`ai_reviewer_drift` (proposed in G-1)	G-1 §4.2	Standard	P2

Special handling for wrong_audience_result: Đ24 ratification REQUIRES cross-law signature with G-5 Access-Control Authority + Đ32 (HIGH risk per G-5 §6.4 in Ratification Package).

Recommended status:

group_status: proposed_for_dieu24_addition (entire group)
sub_status:
  high_risk_signals_separate_ratification: true (wrong_audience_result + signature_failure)
  rest_can_batch_ratify: true

6. Vocabulary Ratification Order

Recommended Đ24 ratification order:

Step 1 (P0-blocking; can be batch):
  - section_type / unit_kind (group 2)
  - body_source_policy (group 3)
  - risk_class (group 4 — cross-law with Đ32)
  - collision_status (group 5)
  - authority values (group 10 — cross-law with Đ0-G)
  - P0-relevant event/signal names (group 11 subset: sweep_overdue, dot_pair_drift, signature_failure)

Step 2 (gates G-5 final operational handoff; HIGH RISK):
  - audience classes (group 6) — cross-law with G-5 + Đ32
  - visibility tiers (group 7) — cross-law with G-5 + Đ32
  - wrong_audience_result (group 11 HIGH-risk sub) — cross-law with G-5 + Đ32

Step 3 (P2/P3 batch; can defer):
  - readiness_state (group 8)
  - publication_state (group 9)
  - threading + retrieval event/signal names (group 11 P2/P3 subset)

P0 Migration Design phase can open after Step 1 closes (Step 2 is required for G-5 operational handoff but not for P0 schema migration design). Step 3 closes parallel to P3 schema work.

7. Preservation Statements (binding)

Per rev5d §13.2.4 and criterion 39:

no_silent_vocabulary_invention: true
  enforcement: cutter MUST emit vocabulary_gap to Decision Backlog if encountering unrecognized term; never silently extend
skos_conceptual_only: true
  enforcement: no RDF/SPARQL/triple-store in v0.1; SKOS is conceptual modeling only
no_parallel_taxonomy: true
  enforcement: all operational labels route to Đ24; no cutter-local taxonomy
audience_vocabulary_is_access_control_critical: true
  enforcement: groups 6, 7, 11(wrong_audience_result) require G-5 + Đ32 cross-law signatures
wrong_audience_result_is_high_risk: true
  enforcement: separate ratification path; HIGH risk class; no batching with Standard signals

8. Cross-Law Coordination

Vocab group	Đ32	Đ37	Đ38	Đ39	Đ44	Đ0-G	G-5
section_type / unit_kind	—	—	required (C1A authority)	—	required (G2 classification)	—	—
body_source_policy	—	—	required	—	required (G3 representation)	—	—
risk_class	required	—	—	—	required (G5 governance state)	—	—
collision_status	—	—	required	—	required	—	—
audience classes ⚠️	required	required	—	—	—	—	required
visibility tiers ⚠️	required	required	—	—	—	—	required
readiness_state	—	—	—	—	required (G4/G5)	check	—
publication_state	—	—	—	—	required (G4)	check	—
authority values	—	—	—	—	required (G5)	required	—
event/signal names — wrong_audience_result ⚠️	required	required	—	—	required (governance_event family)	—	required
event/signal names — signature_failure	required	required	—	—	required	—	—
event/signal names — others	—	required	—	—	required (governance_event family)	—	—

⚠️ marks HIGH-risk vocabulary groups requiring G-5 + Đ32 joint signature.

9. Open Cross-Vocabulary Decisions for Đ24

These Đ24-level decisions span multiple vocabulary groups:

Umbrella vocabulary class for cutter — Should cutter vocabulary be grouped as one "dot-iu-cutter v0.1 vocab" namespace, or distributed per existing Đ24 classes? Recommendation: distributed per existing class (no parallel namespace).
Cardinality limits — Per D7 §8 open question 4 (multi-valued labels first-class vs profile JSON). Đ24 must publish cardinality policy.
Version policy — Vocabulary changes across cutter versions: are old terms supersedable / deprecatable? Recommendation: yes, via Đ24 standard versioning, recorded in Decision Backlog.
Vocabulary gap routing — Confirm Decision Backlog Registry (G-2) is the gap-registration channel; no Đ24-side parallel channel needed.
Cross-law signature semantics — When Đ32 / Đ0-G / G-5 cross-sign on a vocab ratification, is it co-signature or hierarchical (Đ32 confirms scope, then Đ24 ratifies)?

10. Status

package_status: PROPOSED_FOR_DIEU24_RATIFICATION
vocabulary_groups_proposed: 11
vocabulary_groups_p0_blocking: 6 (manifest enums umbrella covers groups 2, 3, 4, 5, 10, 11 P0 subset)
vocabulary_groups_high_risk: 3 (audience classes, visibility tiers, wrong_audience_result)
vocabulary_groups_p2_p3_deferred: P2/P3 subsets of group 11 + groups 6, 7, 8, 9
no_silent_invention: true
skos_conceptual_only: true
no_parallel_taxonomy: true
audience_access_control_marked: true
wrong_audience_result_high_risk_marked: true
cross_law_signatures_mapped: §8
ratification_order_defined: §6
no_schema_created: true
no_ddl_written: true
no_sql_written: true
no_pg_mutation: true
no_qdrant_mutation: true
no_p0_migration_design_started: true
no_implementation: true
parallel_dieu44_closure_required: true
implementation_planning_allowed: false
implementation_allowed: false
migration_design_allowed: not_yet_pending_dieu24_step_1_ratification_AND_dieu44_p0_blocking_families_AND_p0_migration_design_prompt_approval

11. Coverage Check (mandatory sections from prompt)

Required content	Where addressed
List vocabulary groups before P0 Migration Design	§4 + §5
Each group: purpose, source deliverable, used-in-design, Đ24 status	§5.1–§5.11
Each group: risk class	§5.1–§5.11 + §4 summary
Each group: P0/P1/P2/P3 relevance	§5.1–§5.11 + §4
Each group: recommended status (proposed_for_dieu24_ratification)	§5.1–§5.11
No silent vocabulary invention	§2, §7
SKOS conceptual only	§2, §7
No parallel taxonomy	§2, §7
Audience vocabulary is access-control critical	§2, §5.6, §5.7, §7
`wrong_audience_result` is HIGH risk	§2, §5.11, §6 Step 2, §7

dot-iu-cutter v0.1 — Đ24 Vocabulary Closure Package

1. Hard Boundaries

2. Đ24 / Vocabulary Status Statement (binding)

3. Purpose

4. Vocabulary Groups Summary Table

5. Vocabulary Groups — Detailed

5.1 Group 1 — Manifest enums (umbrella)

5.2 Group 2 — section_type / unit_kind

5.3 Group 3 — body_source_policy

5.4 Group 4 — risk_class

5.5 Group 5 — collision_status

5.6 Group 6 — Audience classes ⚠️ HIGH RISK

5.7 Group 7 — Visibility tiers ⚠️ HIGH RISK

5.8 Group 8 — readiness_state

5.9 Group 9 — publication_state

5.10 Group 10 — authority values

5.11 Group 11 — Event / signal names

6. Vocabulary Ratification Order

7. Preservation Statements (binding)

8. Cross-Law Coordination

9. Open Cross-Vocabulary Decisions for Đ24

10. Status

11. Coverage Check (mandatory sections from prompt)

5.2 Group 2 — `section_type` / `unit_kind`

5.3 Group 3 — `body_source_policy`

5.4 Group 4 — `risk_class`

5.5 Group 5 — `collision_status`

5.8 Group 8 — `readiness_state`

5.9 Group 9 — `publication_state`

5.10 Group 10 — `authority` values