dot-iu-cutter v0.2 — BR-6 Absorption Report

document_path: knowledge/dev/laws/dieu44-trien-khai/v0.2-planning/dot-iu-cutter-v0.2-br-6-absorption-report-2026-05-16.md
revision: r1
date: 2026-05-16
author: Agent (Claude Code CLI, Opus 4.7 1M)
sovereign: User / anh Huyên
verifier: GPT (BR-6 absorption review — PENDING)
phase: v0.2 — BR-6 absorption CONSOLIDATED REPORT (planning only)
mutation_performed: false
ddl_written: false
manifest_design_started: false
production_migration_allowed: false
status: PENDING_GPT_REVIEW (Agent does NOT self-close BR-6)

Consolidates the three BR-6 absorption documents (all 2026-05-16, in knowledge/dev/laws/dieu44-trien-khai/v0.2-planning/):

1. dot-iu-cutter-v0.2-br-6-split-merge-td-analysis-2026-05-16.md
2. dot-iu-cutter-v0.2-br-6-impact-on-p0-2-manifest-design-2026-05-16.md
3. dot-iu-cutter-v0.2-br-6-closure-options-2026-05-16.md

---

§1 — Recommended BR-6 Closure Path

recommended_closure_path: Option_D   # hybrid: minimum manifest hooks + recorded invariants + escalated GOV decisions
meaning:
  - P0-2 manifest schema carries the minimum BR-6 structural hooks
    (operation_kind, block_role, source_span, render_order, soft refs, candidate_edges JSONB)
  - BR-6 invariants are written as binding constraints carried into P0-2 design
  - split/merge EXECUTION stays P1 (event-backed via cut_change_set / verify_result /
    birth_registry / lifecycle_log / alias rows) — unauthorized here
  - three governance decisions are ESCALATED for ratification before P0-2 DDL FREEZE
do_not:
  - do not pull P1 split/merge executor into P0-2
  - do not pull P0-6 review_decision or CUT/VERIFY into P0-2
  - do not couple manifest to the alias table
closure_owner: GPT + User   # Agent recommends; does not self-close

§2 — Can P0-2 Manifest Design Start After GPT Review?

p0_2_design_can_start_after_gpt_review: YES, CONDITIONAL
conditions:
  - GPT reviews these 4 BR-6 absorption docs and accepts Option D (or directs another)
  - GPT/Council ratifies (or schedules) the 3 GOV decisions in §4
  - an explicit User prompt opens the P0-2 design lane (separate session)
clarifications:
  - P0-2 DESIGN may begin once Option D is accepted + explicit prompt issued
  - P0-2 DDL may NOT be FROZEN until GOV-1/GOV-2/GOV-3 are ratified
  - DDL authoring, dry-run, command-review, production each remain separately gated
    (scope-backlog §4 step process is unchanged)
agent_self_advance: PROHIBITED

§3 — Required Constraints to Carry Into P0-2

(From the BR-6→P0-2 impact analysis §6; binding if Option D is accepted.)

1. manifest_envelope.operation_kind ∈ {first_cut, split, merge} (app-layer enum).
2. manifest_unit_block.block_role ∈ {origin, result} (app-layer enum) — mandatory.
3. manifest_unit_block.source_span present and mandatory (split partitions, merge unions).
4. render_order column present; recompute algorithm is P1.
5. Cross-schema references are soft uuid only (no PG FK to tac_logical_unit, cut_change_set, verify_result, canonical_address_alias).
6. In-schema FK only: manifest_unit_block.envelope_id → manifest_envelope.
7. No PG CHECK / trigger / DEFAULT data; tables created empty; DROP TABLE rollback.
8. Edge-redistribution + report intent in JSONB (candidate_edges, payload_summary, report_summary); no edge tables.
9. No manifest↔alias coupling; alias emission is a P1 execution invariant.
10. Envelope exposes escalation_ref (soft → decision_backlog_entry) and soft cut_change_set_ref; review_decision itself stays P0-6 (deferred).

3.1 BR-6 Invariants (bind P1 behavior, recorded now)

• INV-1 canonical_address is immutable; split/merge coins NEW addresses and never reuses/rewrites a live canonical (alias trail mandatory).
• INV-2 a successor cannot acquire higher authority than its predecessor without an explicit re-enactment path.
• INV-3 successors inherit predecessor canonical_address_format_version; never downgraded.
• INV-4 every topology change emits previous_canonical / redirect alias rows at P1 enactment.
• INV-5 a split/merge is review-gated (proposal → review → enact).
• INV-6 all metadata mutation flows through a cut_change_set + verify_result; no out-of-band propagation.

§4 — Open Questions (escalated; block P0-2 DDL FREEZE, not design start)

GOV-1_address_coining_rule:
  question: how are sub-piece / merged-result canonical_addresses coined?
  options: extend v1 grammar (-P{n} / -{n}) | new sequence | hybrid
  owner: Đ24 (canonical-address grammar council) + GPT
GOV-2_authority_inheritance:
  question: does a split of an 'enacted' unit yield 'enacted' or 'draft' children;
            what is the merge-result authority?
  owner: Đ0-G (authority semantics council) + GPT
GOV-3_manifest_alias_linkage:
  question: explicit manifest→alias linkage column, or purely event-backed at P1?
  agent_lean: purely event-backed (no coupling); record as INV-4
  owner: GPT
other_open_items:
  - render_order recompute algorithm (P1 design item; not P0-2)
  - hierarchy re-parenting engine (P1 design item; not P0-2)
  - detection→handling wiring (Q21/Q22 signals → split/merge trigger) is P1

§5 — Explicit Status Flags

mutation_performed: false
ddl_written: false
manifest_design_started: false
production_migration_allowed: false
br_6_self_closed: false
br_6_status: PENDING_GPT_REVIEW
p0_2_dry_run_started: false
production_touched: false
cut_or_verify_performed: false
alias_rows_written: false

§6 — Next Steps (recommended; not self-advanced)

1. GPT reviews the 4 BR-6 absorption docs → accept Option D (or direct alternative) and formally close BR-6 (GPT, not Agent).
2. GPT/Council schedules ratification of GOV-1/GOV-2/GOV-3.
3. On explicit User prompt (separate session): open P0-2 manifest design lane, carrying the §3 constraints + §3.1 invariants. DDL freeze remains gated on GOV rulings; dry-run / command-review / production remain separately gated per scope-backlog §4.

§7 — Hard Boundaries

no_DDL_written: TRUE
no_manifest_design_started: TRUE
no_mutation: TRUE
no_migration: TRUE
no_production_touch: TRUE
no_CUT_or_VERIFY: TRUE
no_alias_writes: TRUE
BR_6_self_closed: FALSE   (left PENDING GPT review)
agent_self_advance: PROHIBITED
output_form: br_6_absorption_consolidated_report

End of BR-6 absorption report.