KB-108A

dot-iu-cutter v0.5 — Constitution Status-Marker + First-Dry-Run Scope Ruling Request (recommend enacted_only; exclude 📋/📝/⛔)

6 min read Revision 1
dot-iu-cutterv0.5constitution-fixturestatus-markerscope-ruling-requestenacted-onlydesign-onlyroute-gpt-userdieu442026-05-18

dot-iu-cutter v0.5 — Constitution Status-Marker + First-Dry-Run Scope Ruling Request

Phase: v0_5_constitution_fixture_source_grammar_ratification · Nature: ruling_request__no_execution · Date: 2026-05-18 Decision authority: GPT / User ONLY. Agent recommends; does not decide silently (QG5).

1. The decision space

The fixture uses four node-level status markers; the ratified grammar profile maps two. The live source_family.status_policy = enacted_only. We must rule (a) how to recognise all four, and (b) which are in-scope for the first Constitution dry-run.

observed_markers:
  "✅" enacted          (38) — ratified-mapped
  "📋" controlled_draft (2)  — ratified-mapped (e.g. Điều 44)
  "📝" draft            — observed in MỤC LỤC LUẬT legend; NOT ratified-mapped
  "⛔" obsolete/retired  — observed in MỤC LỤC LUẬT legend; NOT ratified-mapped
live_status_policy: enacted_only (source_family internal_incomex_constitution)

2. Option set for ✅ ENACTED / 📋 CONTROLLED DRAFT / 📝 / ⛔

RULING-SM (marker recognition — prerequisite to ANY dry-run):
  SM-opt-1 AMEND_PROFILE_MAP_4 (recommended):
    add 📝->draft and ⛔->obsolete to grammar_profile_status_marker (mapping only;
    NOT cut-eligible). Result: all 4 markers deterministically classifiable;
    enacted_only cleanly excludes 📋/📝/⛔.
    cost: one ruling-gated DML amendment package (separate gate).
  SM-opt-2 SCOPE_FILTER_ONLY_NO_AMEND:
    do not amend; instead restrict first dry-run to nodes bearing ONLY ✅ and
    treat any non-✅ marker as "exclude + route to review".
    risk: an unmapped marker is an UNHANDLED signal -> fail-closed sends large
    parts to review; brittle; not deterministic enough for a clean dry-run.
  SM-opt-3 DO_NOTHING:
    rejected — parser cannot safely classify 📝/⛔; mis-cut / ambiguity risk.
agent_recommendation: SM-opt-1 (amend map to 4) BEFORE first dry-run.

RULING-SCOPE (first Constitution dry-run inclusion):
  SC-opt-A ENACTED_ONLY_STRICT (recommended):
    include ONLY ✅ ENACTED nodes; EXCLUDE 📋 controlled-draft (incl. Điều 44),
    📝 draft, ⛔ obsolete. Matches live status_policy=enacted_only. Smallest,
    safest, fully deterministic first dry-run.
  SC-opt-B ENACTED_PLUS_CONTROLLED_DRAFT:
    include ✅ and 📋 (flagged); exclude 📝/⛔. Larger; pulls in unstable
    Điều 44 controlled-draft -> instability risk; contradicts enacted_only.
  SC-opt-C INCLUDE_ALL_STATUS_AS_METADATA:
    include everything, status as metadata only. Highest risk; directly
    contradicts the live enacted_only policy. Rejected.
agent_recommendation: SC-opt-A (enacted_only strict) for the FIRST dry-run.

3. Controlled-draft Điều 44 — include / exclude / defer

recommendation: DEFER (exclude from first dry-run).
why:
  - Điều 44 carries 📋 CONTROLLED DRAFT — explicitly unstable / not promulgated.
  - live source_family.status_policy = enacted_only already mandates exclusion.
  - cutting a controlled-draft node risks pinning an IU to content that will
    change, producing churn/supersession noise on the very first hardtest.
status: ruling request — Agent recommends DEFER; GPT/User decides.
re-entry: once Điều 44 flips to ✅ ENACTED (living document), a later version
  (new content_checksum -> new document_version_id) naturally brings it in-scope.

4. Risk table

choice risk of INCLUDING draft sections risk of EXCLUDING draft sections
📋 controlled-draft (Điều 44) pins IU to unstable content; supersession churn; first-hardtest noise; contradicts enacted_only a known Điều temporarily absent from corpus (expected, reversible when enacted)
📝 draft entries same as above + marker not even ratified (mis-cut) minor coverage gap; deterministic
⛔ obsolete entries cuts retired content as if live — semantically wrong correct (obsolete must not be cut)
not amending the map (SM) unmapped marker → fail-closed mass-review or mis-cut n/a (amending is the safe path)
net: excluding draft/obsolete is LOW risk and policy-consistent; including them
  is HIGH risk and policy-contradicting. Excluding is recommended for dry-run 1.

5. Clear ruling request to GPT/User

REQUESTED_RULINGS:
  R1 (RULING-SM): approve SM-opt-1 — amend grammar_profile_status_marker for
     incomex-architecture-constitution-v4 to add 📝->draft, ⛔->obsolete
     (mapping only; via a SEPARATE authoring→review→execution gate). Y/N.
  R2 (RULING-SCOPE): approve SC-opt-A — first Constitution dry-run = ENACTED_ONLY
     (✅ only; exclude 📋/📝/⛔). Y/N.
  R3 (Điều 44): confirm DEFER (exclude) controlled-draft Điều 44 from first
     dry-run. Y/N.
  R4 (OD-S1, pre-existing): confirm KB-7294/v4.6.3 BAN HÀNH authority is
     sufficient as `authority_class=authoritative` for cut eligibility. Y/N.
  R5 (OD-G2, pre-existing): rule leaf-IU granularity (Điều vs sub-bullet vs
     Nguyên-tắc) — needed before volume/+15 invariant is trusted. (defer ok)
none_self_resolved: all five are FLAGGED requests; Agent took no decision.

6. Statements

  • Status-marker policy made explicit (QG3); controlled-draft inclusion is a GPT/User ruling request because it is ambiguous and policy-affecting (QG5). Recommendations given; nothing decided silently.
  • No DML/DDL/amendment/cut/verify/dry-run executed (QG6).
  • Self-advance PROHIBITED — doc 4 of 5; STOP after package → route GPT/User.

Companion: grounding-report, grammar-applicability-review, source-document-version-plan, ratification-readiness-report.

Back to Knowledge Hub knowledge/dev/laws/dieu44-trien-khai/v0.5-constitution-fixture-source-grammar-ratification/dot-iu-cutter-v0.5-constitution-status-marker-and-scope-ruling-request-2026-05-18.md