dot-iu-cutter v0.1 — P0 Implementation Planning Master

Date: 2026-05-15 Status: IMPLEMENTATION PLANNING PHASE — ACTIVE (PLANNING ONLY) Trigger: GPT review of X-A Ratification Closure returned PASS. X-A is now closed_with_notes. Implementation Planning Gate transitioned to OPEN_PENDING_EXPLICIT_PROMPT_APPROVAL. By the user's 2026-05-15 prompt, GPT explicitly approves opening the Implementation Planning Package phase. Scope: PLANNING ONLY. No code, no DDL, no SQL, no CREATE TABLE, no ALTER TABLE, no migration script, no PG mutation, no Qdrant/vector mutation, no Directus mutation, no data write, no implementation execution, no deploy.

1. Phase Scope

The Implementation Planning phase consumes:

8 P0 Migration Design files (logical schema designs)
5 Đ32 Risk Review files (risk catalogue + cross-cutting register + verdicts)
1 X-A Ratification Closure (binds source_span unit ↔ axis_1_drift_unit alignment)

and produces execution-ready planning without producing any executable SQL, code, migration files, or scripts.

Execution-ready planning = the plan is detailed enough that an execution phase, once authorized, could be carried out by translating the planning artefacts into DDL/SQL/migration scripts — but the translation itself is performed in a future execution phase.

phase_id: dot-iu-cutter-v0.1-p0-implementation-planning
phase_type: planning_only
phase_authorization: GPT explicit prompt 2026-05-15 (post X-A ratification closure PASS)
phase_inputs:
  - ratification/dot-iu-cutter-v0.1-x-a-source-span-drift-unit-ratification-2026-05-15.md
  - reviews/dot-iu-cutter-v0.1-x-a-ratification-closure-gpt-review-2026-05-15.md
  - reviews/dot-iu-cutter-v0.1-dieu32-p0-risk-review-package-gpt-review-2026-05-15.md
  - risk-review/dot-iu-cutter-v0.1-dieu32-p0-risk-review-report-2026-05-15.md
  - risk-review/dot-iu-cutter-v0.1-p0-cross-cutting-decision-register-2026-05-15.md
  - migration-design/dot-iu-cutter-v0.1-p0-migration-design-master-2026-05-15.md
  - migration-design/dot-iu-cutter-v0.1-p0-1-canonical-address-migration-design-2026-05-15.md
  - migration-design/dot-iu-cutter-v0.1-p0-2-manifest-envelope-unit-block-migration-design-2026-05-15.md
  - migration-design/dot-iu-cutter-v0.1-p0-3-cut-change-set-rollback-key-migration-design-2026-05-15.md
  - migration-design/dot-iu-cutter-v0.1-p0-4-verify-result-migration-design-2026-05-15.md
  - migration-design/dot-iu-cutter-v0.1-p0-5-decision-backlog-entry-migration-design-2026-05-15.md
  - migration-design/dot-iu-cutter-v0.1-p0-6-review-decision-migration-design-2026-05-15.md
phase_outputs:
  - this master
  - cross-cutting resolution plan
  - migration sequence plan
  - preflight and backup plan
  - rollback test plan
  - canonicalization rule v0.1 planning note
  - operational seat naming plan
  - implementation planning report (final gate status)
phase_completion_signals:
  - 8 files produced under knowledge/dev/laws/dieu44-trien-khai/implementation-planning/
  - 7 cross-cutting decisions documented with selected approach
  - migration sequence specified at planning level for all 6 P0 items
  - preflight/backup/rollback-test plans drafted
  - operational-seat plan drafted
  - explicit gate status recorded in the report
phase_does_not_advance_to: implementation_execution
next_phase_gate: Final Execution Readiness Review (not direct execution)

2. Hard Boundaries

no_code: true
no_ddl: true
no_sql: true
no_create_table: true
no_alter_table: true
no_column_ddl: true
no_index_ddl: true
no_constraint_ddl: true
no_trigger_function_or_rls_policy: true
no_migration_script: true
no_migration_executable: true
no_migration_executed: true
no_pg_mutation: true
no_qdrant_mutation: true
no_directus_mutation: true
no_data_writes: true
no_deploy: true
no_implementation_execution: true
no_auto_open_execution_phase: true
no_modification_of_phase_prior_files: true
output_form: implementation_planning_documentation_in_markdown_only

Planning documentation includes: chosen approaches per cross-cutting decision, migration sequence with logical preconditions/validations/rollback notes, backup-and-preflight plan, rollback test scenario matrix, canonicalization rule prose-planning, operational-seat placeholders, blockers register, gate status.

Planning documentation EXCLUDES: SQL/DDL syntax, signing-scheme primitives, canonicalization-rule executable form, actual backups, actual migrations, actual signature generation, actual rollback dry-runs, role creation, environment changes.

3. Planning Objective

The objective is to convert the design and risk-review record into an execution-ready plan that an authorized Final Execution Readiness Review can sign off on. The plan must:

State an approach for each remaining planning-level cross-cutting decision (X-1..X-8 minus X-A which is already ratified).
Specify the per-item migration order with preconditions, validation criteria, rollback notes.
Specify the preflight + backup requirements that any execution phase must satisfy.
Specify the rollback test plan structure (scenario matrix, expected outcomes) that must be dry-run before any real CUT.
Specify the canonicalization rule v0.1 plan (prose plan; not executable form).
Specify the operational-seat plan for governance gaps G-1..G-5 with Đ37 dependency.
Emit a planning report that classifies remaining blockers by execution gate and confirms the execution gate remains closed.

4. Execution Remains Forbidden

execution_status_during_this_phase: forbidden
execution_status_after_this_phase: still_forbidden_pending_final_execution_readiness_review
execution_gate_does_NOT_open_by_phase_completion: true
execution_gate_opens_only_after:
  - this phase complete
  - GPT review of planning package (PASS)
  - Final Execution Readiness Review signed
  - all execution-level blockers closed (per the planning report)
  - explicit user prompt to authorize execution (separate prompt)

5. Dependency Graph (carried from migration-design master §3)

                  [P0-5 decision_backlog_entry]              ← foundational; no upstream
                              │
                              ▼
                  [P0-1 canonical_address]                    ← upstream: P0-5 (governance trail)
                              │
                              ▼
                  [P0-2 manifest_envelope + manifest_unit_block]
                              │                               ← upstream: P0-5, P0-1
                              ▼
                  [P0-6 review_decision]                      ← upstream: P0-2, P0-5
                              │
                              ▼
                  [P0-3 cut_change_set + rollback_key]        ← upstream: P0-2, P0-6, P0-5
                              │
                              ▼
                  [P0-4 verify_result]                        ← upstream: P0-3, P0-2, P0-6, P0-5

This dependency graph drives the migration sequence (migration sequence plan §3).

Joint pairs preserved:

P0-2 envelope + manifest_unit_block (composite identity)
P0-3 + P0-4 (shared dot_pair_signature schema)

6. Implementation Planning Lanes

lane_resolution:
  purpose: resolve or plan resolution for the 7 planning-level cross-cutting decisions (X-1, X-2, X-3, X-4, X-6, X-7, X-8) per the Cross-Cutting Decision Register
  file: dot-iu-cutter-v0.1-p0-cross-cutting-resolution-plan-2026-05-15.md
lane_sequence:
  purpose: specify per-item migration sequence with preconditions, validations, rollback notes
  file: dot-iu-cutter-v0.1-p0-migration-sequence-plan-2026-05-15.md
lane_preflight:
  purpose: specify backup + snapshot + dry-run + failure-stop requirements
  file: dot-iu-cutter-v0.1-p0-preflight-and-backup-plan-2026-05-15.md
lane_rollback_test:
  purpose: specify scenario matrix for rollback + verify dry-runs covering P0-3/P0-4 HIGH-risk surface
  file: dot-iu-cutter-v0.1-p0-rollback-test-plan-2026-05-15.md
lane_canonicalization:
  purpose: prose plan for canonicalization_rule_v0.1; no executable form
  file: dot-iu-cutter-v0.1-p0-canonicalization-rule-v0.1-planning-note-2026-05-15.md
lane_operational_seats:
  purpose: G-1..G-5 placeholder plan; Đ37 dependency
  file: dot-iu-cutter-v0.1-p0-operational-seat-naming-plan-2026-05-15.md
lane_report:
  purpose: final planning report; gate status
  file: dot-iu-cutter-v0.1-p0-implementation-planning-report-2026-05-15.md

7. Risk Gates

Risk gates persist across this phase. Each gate has a clear status during planning and an explicit close condition for the next phase.

gate_X_A:
  status: closed_with_notes (ratified 2026-05-15)
  effect_on_planning: opens planning phase; placeholder canonicalization rule bound for byte→token conversion
gate_X_7_canonicalization_rule_prose:
  status: open; Đ24 ratification path
  effect_on_planning: planning documents prose; ratification remains pending; does NOT block planning completion; DOES block execution
gate_X_8_rollback_test_plan:
  status: planning-level authoring done in this phase; dry-run execution remains pending
  effect_on_planning: scenario matrix authored; execution dry-run is execution precondition
gate_X_1_schema_placement:
  status: planning approach selected here; final schema-class authority sign-off pending Đ44/Đ33/Đ43
  effect_on_planning: planning lists approach; sign-off is execution precondition
gate_X_2_primary_id_form:
  status: planning approach selected here (uuid + human aliases)
  effect_on_planning: planning fixes the choice; execution adopts it
gate_X_3_jsonb_validation_policy:
  status: planning approach selected here (application-layer v0.1; PG jsonb_check FUTURE)
  effect_on_planning: planning fixes the choice
gate_X_4_enum_implementation_strategy:
  status: planning approach selected here (Đ24 lookup FK)
  effect_on_planning: planning fixes the choice; Đ24 lookup table population pending operational handoff
gate_X_6_dot_pair_signature_shape:
  status: planning polish; shape already designed in P0-3 §4.3
  effect_on_planning: planning records polish; G-4 sign-off is execution precondition
gate_operational_seats:
  status: placeholders drafted; named-human assignment is operational; gates execution for some items
  effect_on_planning: planning records dependency; execution-level blocker for HIGH-risk items
gate_dot_pair_registration:
  status: pending G-4 Custodian seat naming
  effect_on_planning: planning notes dependency; execution precondition
gate_final_execution_readiness_review:
  status: not_started
  effect_on_planning: planning prepares inputs for this gate; this gate must sign off before execution

8. What Must Be Resolved Before Execution

Aggregated from Đ32 Risk Review Report §7.3 + the cross-cutting register + per-item designs:

execution_preconditions:
  cross_cutting_closures:
    - X-7 canonicalization rule v0.1 prose ratified by Đ24
    - X-8 rollback test plan dry-run executed with synthetic data
    - X-1 schema placement sign-off (Đ44 + Đ33/Đ43)
    - X-6 dot_pair_signature shape sign-off (G-4)
  operational_seats:
    - G-1 Threading Roles seat named
    - G-2 Backlog Custodian seat named
    - G-3 Capability-Intake Reviewer seat named
    - G-4 DOT-Pair Signing Authority seat named
    - G-5 Access-Control Authority seat named
  dot_pair_registration:
    - dot-iu-cutter executor DOT registered via G-4
    - dot-iu-cutter-verify verifier DOT registered via G-4
  signing_scheme_implementation:
    - v0.1 hash-based pseudo-signature implementation accepted (cryptographic FUTURE)
  signal_routing:
    - dot_pair_drift / signature_failure routed to G-2 backlog
  canonicalization_rule_library_scaffolding:
    - v0.1 scaffolding present (placeholder per X-A: NFC + LF + trim for markdown)
  directus_backup:
    - directus full backup taken immediately before execution; restore tested
  final_execution_readiness_review:
    - signed off by Đ32 (HIGH-risk path) + Đ44 + Đ37 + G-4 Custodian
  user_authorization:
    - explicit user prompt to authorize execution (separate from this planning prompt)

9. Cross-File Linkage

Each subsequent planning file in this package follows a shared skeleton:

1. Purpose
2. Source inputs (controlling files)
3. Scope (planning-only; no executable form)
4. Substantive planning content (per the file's lane)
5. Preconditions / dependencies
6. Blockers classified by gate
7. Explicit "no DDL / no SQL / no migration / no PG mutation / no execution" confirmation

The Implementation Planning Report (file 8) aggregates the planning decisions, blockers, and gate status.

10. Status

master_document_status: COMPLETE
files_in_package_target: 8 (this master + 6 lane files + 1 report)
implementation_planning_phase: ACTIVE
implementation_execution_allowed: false
code_written: false
ddl_written: false
sql_written: false
migration_executed: false
pg_mutation: false
qdrant_mutation: false
directus_mutation: false
no_phase_prior_file_modified: true
gpt_input: PASS verdict on X-A ratification closure (2026-05-15) and explicit prompt approval to open implementation planning