KB-4629

MOWD Phase 1 — Overview / Control Tower

6 min read Revision 1
mowmowdphase1control-towerarchitecture2026-05-29

MOW Design Registry — Phase 1 Execution Control Tower

Campaign: MOW_DESIGN_REGISTRY_PHASE1_RATIFY_COMMIT_DOT_UI_MIGRATION_ACCEPTANCE_MEGACAMPAIGN Date: 2026-05-29 · Status: PASS (zero net mutation) · Host: contabo VPS · Container: postgres · DB: directus (PG 16.13) Read channel: MCP query_pg role context_pack_readonly · Apply channel (rehearsal only): ssh contabodocker exec -i postgres psql -U workflow_admin -d directus

MOW remains the owning Mother. MOWD is shorthand for the MOW Design Registry subdomain, not a fifth Mother. No second source-of-truth. IU-centered invariant preserved.


1. What this package is

This is the Phase 1 execution-readiness package that converts the v0.1 Master Design + GREEN additive-EXTEND dress rehearsal into a complete, human-executable rollout kit: human ratification packet, commit-readiness pack, DOT family, UI data contracts, the 70-inline-step migration plan, a validation harness, governance/proposal flow, runtime boundary, a first pilot, a risk review, and a 30+ prompt pack for the next workstreams.

Nothing in this campaign committed any schema change, data change, Directus/Qdrant write, UI, runtime, law, or self-approval. Both write-channel actions were BEGIN … ROLLBACK rehearsals.

2. Gate 0 result (this session)

Check Result
Host / container / DB contabo · postgres (postgres:16, up 6 weeks healthy) · directus
Read role context_pack_readonly (server 172.19.0.3)
Apply role (rehearsal) workflow_admin — SELECT verified before any write
fn_iu_gate_verify_closed() all_safe=true, never_flip_intact=true, all_governed_closed=true
idle-in-transaction 0 (entry and exit)
Exit == entry wf 2 · steps 70 · rel 80 · cat 54 · IU 219 · gov 9 · wf cols 17 · step cols 20

10 governable/never-flip gates all closed-and-safe (composer/delivery/operator_runtime/structure_ops/three_axis_auto_refresh/emit/dlq.replay/job_substrate = false governable; vector_sync + allow_no_review_decision = false never_flip).

3. Baseline snapshot (live, 2026-05-29)

workflows 2 | workflow_steps 70 | workflow_step_relations 80 | workflow_change_requests 3
approval_requests 211 | apr_approvals 42 | governance_registry 9
dot_iu_command_catalog 54 | dot_tools 309 | event_type_registry 40 | event_outbox 159,287
information_unit 219 | iu_relation 60 | v_kg_edges_all 2,259
meta_catalog 169 | collection_registry 168 | table_registry 21

Phase 1 backlog (measured): 0/2 workflows IU-bound · 0/2 workflows GOV-owned · 70/70 steps inline.

4. Rehearsal evidence (GREEN, this session, rolled back)

Additive EXTEND (keystone, Branch B): BASE 17/20/8IN_TX 25/27/9 (+8 workflows, +7 workflow_steps, +1 workflow_step_relations) → 8 FK NOT VALID created2 views compiled (smoke: v_mow_design_workflow 2 rows, v_mow_design_step 70 rows) → ROLLBACK17/20/8, 0 views, 0 idle-tx.

Read-only DOT registration (Branch C): catalog 5460 (6 dot_mow_design_* read DOTs) → ROLLBACK54, 0 idle-tx.

FK target types verified: information_unit.id uuid · table_registry.id int · governance_registry.code varchar · dot_iu_command_catalog.command_name text · event_type_registry composite PK (event_domain,event_type) → single-col FK impossible, modelled as a composite FK.

5. Document map

Doc Branch Title Verdict
00 Overview / Control Tower (this) PASS
01 A Human ratification packet Executable
02 B Commit readiness pack (additive EXTEND) Human-executable
03 C DOT family design + rehearsal Fully specified (15 DOTs)
04 D Master UI data contract (4 surfaces) Concrete
05 E 70 inline-step → IU migration plan Actionable
06 F Validation harness (read-only SQL pack) Defined + run
07 G Governance / proposal flow Defined
08 H Runtime boundary / non-goals + entry criteria Explicit
09 I Pilot scenario (WF-001) Ready
10 J Risk + sequencing review Complete
11 K Next prompt pack (32 prompts) ≥30 delivered
12 Law / forbidden / self-review PASS

6. Owner & invariants (carried into every doc)

  • Owner: GOV-MOW (Mother of Workflows) — factory/mother, domain assembly.workflow, status draft, can_create:[workflows], must_not_own:[tasks,input_form_registry,design_templates,information_unit], can_reference:[tasks,input_form_registry,design_templates,information_unit].
  • No second SoT: design lives as additive columns on the existing workflows/workflow_steps/workflow_step_relations + read-only views; design bodies move to information_unit (the canonical SoT), referenced by uuid.
  • Reversibility (Điều 30): every committed step has an explicit reversal; FKs land NOT VALID then VALIDATE off-peak.
  • No self-approval: agent may propose; only human/council with cross-sign ≥2 (apr_approvals) may approve/activate.

7. Readiness verdicts (headline)

Ratification: READY (no prior approval artifact found → packet provided, no self-approval). Commit: READY pending human Điều 32. DOT family: specified, read-only subset rehearsed. UI contracts: concrete, backend-enforced. Migration: actionable, low-risk (inline text is short labels, 0 long-text rows). Validation harness: defined + executed read-only. Pilot: WF-001 selected, ready. Prompts: 32.

8. Next macro

MOWD_PHASE1_HUMAN_RATIFY_THEN_ADDITIVE_EXTEND_COMMIT_OFFPEAK → (on approval) commit per doc 02 → register read-only DOTs (doc 03) → stand up read models (doc 04) → run pilot (doc 09).

Back to Knowledge Hub knowledge/dev/reports/architecture/mow-design-registry-phase1-ratify-commit-dot-ui-migration-acceptance-megacampaign-2026-05-29/00-overview-control-tower.md