dot-iu-cutter v0.1 — HB-01 X-1 Schema Placement Sign-Off Closure

Date: 2026-05-15 Status: HB-01 CLOSURE RECORD — closed_with_notes Trigger: GPT review of HB-06 Operational Seats Closure returned PASS (2026-05-15). User has explicitly authorized batch closure of HB-01, HB-02, HB-03, HB-04. Scope: CLOSURE RECORD ONLY. No code, no DDL, no SQL, no schema created, no migration, no PG mutation, no Directus mutation, no Qdrant/vector mutation, no backup, no snapshot, no dry-run, no execution.

---

1. Scope

HB-01 binds the schema placement decision X-1 for dot-iu-cutter v0.1 P0. The decision selects a new schema class (cutter_governance) for the new governance / manifest / cut / verify / review objects and preserves the existing TAC schema for canonical_address (P0-1). This closure record:

• accepts the planning approach recorded in the Cross-Cutting Resolution Plan §4
• records the authorities that sign off
• enumerates the schema-class membership
• restates downstream effects
• explicitly forbids any DDL / migration / schema creation in this phase

hb_01_scope:
  in_scope:
    - record X-1 selected approach acceptance
    - record schema class name and membership
    - record P0-1 placement (stays on TAC schema)
    - record Đ44 + Đ33/Đ43 sign-off attribution
  not_in_scope:
    - create the schema (DDL is future execution-phase task)
    - assign concrete PG roles to the schema class (operational handoff)
    - decide column-level details (those are per-item; design files already cover them)
    - alter any existing schema
    - move any existing table

2. Source References

• reviews/dot-iu-cutter-v0.1-hb-06-operational-seats-closure-gpt-review-2026-05-15.md (PASS — authorizes batch closure)
• blocker-closure/dot-iu-cutter-v0.1-hb-06-operational-seats-closure-2026-05-15.md
• blocker-closure/dot-iu-cutter-v0.1-p0-blocker-closure-dashboard-2026-05-15.md §3 (HB-01 row)
• implementation-planning/dot-iu-cutter-v0.1-p0-cross-cutting-resolution-plan-2026-05-15.md §4 (X-1 selected approach)
• final-readiness/dot-iu-cutter-v0.1-p0-final-readiness-blocker-register-2026-05-15.md §3.1 (HB-01 entry)
• risk-review/dot-iu-cutter-v0.1-p0-cross-cutting-decision-register-2026-05-15.md §3.2 (X-1 options + recommendation)
• blocker-closure/dot-iu-cutter-v0.1-p0-workstream-b-vocabulary-schema-canonicalization-2026-05-15.md §3 (HB-01 acceptance criteria)

3. Decision Recorded

decision_id: HB-01
cross_cutting_decision_resolved: X-1
selected_option: new_schema_class_for_governance_and_manifest_family

schema_class_decision:
  schema_class_name: cutter_governance
  status: working name accepted at design level; Đ33/Đ43 retains authority to rename at execution-phase DDL authoring without re-opening HB-01

schema_class_membership (the 11 new objects bound to cutter_governance):
  manifest_family:
    - manifest_envelope (P0-2)
    - manifest_unit_block (P0-2)
  cut_family:
    - cut_change_set (P0-3)
    - cut_change_set_affected_row (P0-3)
  signature_family (shared P0-3 + P0-4):
    - dot_pair_signature
  verify_family:
    - verify_result (P0-4)
  decision_backlog_family:
    - decision_backlog_entry (P0-5)
    - decision_backlog_history (P0-5)
    - decision_backlog_dependency (P0-5)
    - sweep_log (P0-5)
  review_family:
    - review_decision (P0-6)

P0_1_placement_decision:
  canonical_address: stays in existing TAC/tac_logical_unit context (field family added to tac_logical_unit)
  canonical_address_alias: stays in TAC schema or shared schema per Đ33/Đ43 preference at execution-phase DDL authoring; NOT placed in cutter_governance
  rationale:
    - TAC schema preserves content-only semantics for content tables
    - cutter_governance preserves governance/manifest/cut/verify/review semantics
    - canonical_address is an identity field on a TAC content row, not a governance object

4. Authority / Sign-Off

authorities_signing:
  primary_signers:
    - Đ44 (family registry custodian) — accepts family placement
    - Đ33/Đ43 (schema authority / DB placement path) — accepts DB/schema placement
  secondary_signers:
    - GPT (policy reviewer; PASS upstream on cross-cutting register and X-1 recommendation)
    - User / anh Huyên (final authority for governance closures)
    - Opus / Agent (record-keeping side)

what_each_authority_accepts:
  Đ44:
    - the family placement: governance / manifest / cut / verify / review families bundled into cutter_governance
    - canonical_address remains a TAC-family field (not a separate governance family)
  Đ33_Đ43:
    - the DB/schema placement path: new schema class within Directus PG (Directus on PG since 2026-03-13)
    - permission / role mapping is an operational task at execution-phase DDL authoring (NOT performed here)
  GPT:
    - the cross-cutting register §3.2 recommendation matches the closure
  User / anh Huyên:
    - sovereign acceptance per the explicit prompt

5. Acceptance Criteria

acceptance_criteria_for_hb_01:
  schema_class_name_recorded:
    status: NAMED (cutter_governance, working name acceptable)
  schema_class_membership_recorded:
    status: ENUMERATED (11 new objects listed in §3 above)
  P0_1_placement_recorded:
    status: BOUND (canonical_address stays on TAC schema; alias placement deferred to Đ33/Đ43 at execution-phase DDL authoring)
  signing_attribution_recorded:
    status: ATTRIBUTED (Đ44 + Đ33/Đ43 primary; GPT + User + Opus/Agent secondary)
hb_01_acceptance_state: ALL FOUR criteria satisfied; closure_with_notes

6. Downstream Effects

downstream_effects_of_hb_01_closure:
  HB_05_rollback_test_plan_dry_run:
    note: HB-05 depends on the dry-run environment (HB-09) which references the schema class; HB-01 reduces uncertainty for HB-09 prep work
    status_change: none — still blocked on other upstream
  HB_09_snapshots_dry_run_environment:
    note: schema snapshot scope now defined (snapshot will cover the approved cutter_governance schema once it exists at execution time; pre-migration snapshot captures its absence)
    status_change: still ready_to_close (HB-01 does not unblock or block HB-09 directly)
  first_DDL_of_every_P0_step:
    note: first DDL on cutter_governance cannot occur until schema is created (execution phase); HB-01 binds the design-level decision
    status_change: pre-execution gate intact

no_other_blocker_directly_unlocked_by_HB_01: HB-01 is independent and parallel to the critical path

what_HB_01_does_NOT_do:
  - create the cutter_governance schema
  - allocate PG roles / permissions on the schema
  - move existing tables
  - alter the TAC schema
  - decide column-level form (handled per-item in migration-design files)

7. Status

HB_01_status: closed_with_notes
HB_01_closure_authority: Đ44 + Đ33/Đ43 (per cross-cutting register §3.2 + user prompt 2026-05-15)
HB_01_closure_signers:
  - Đ44 family registry custodian (primary)
  - Đ33/Đ43 schema authority (primary)
  - GPT (policy reviewer)
  - User / anh Huyên (sovereign authority)
  - Opus / Agent (record-keeping)

execution_authorized: false
implementation_allowed: false
ddl_allowed: false
migration_allowed: false

notes_carried_forward:
  - working name cutter_governance accepted; Đ33/Đ43 retains rename authority at execution-phase DDL authoring without re-opening HB-01
  - canonical_address_alias final placement (TAC schema vs shared) deferred to Đ33/Đ43 at execution-phase DDL authoring
  - permission / role mapping is operational at execution-phase DDL authoring (NOT performed here)
  - no schema is actually created by this closure

8. Hard Boundaries Confirmation

no_schema_created: true
no_table_created: true
no_pg_role_created: true
no_permission_granted: true
no_table_moved: true
no_existing_schema_altered: true
no_ddl_written: true
no_sql_written: true
no_migration_script_written: true
no_migration_executed: true
no_pg_mutation: true
no_qdrant_mutation: true
no_directus_mutation: true
no_data_writes: true
no_execution: true
no_phase_prior_file_modified: true
output_form: hb_01_closure_record_in_markdown_only