KB-5E65

GPT Direction — After MOW Design v0.1 Rehearsal PASS → Phase1 MegaCampaign (2026-05-29)

3 min read Revision 1
gptmow-design-registryphase1dotui-contractmigrationacceptance2026-05-29

GPT Direction — After MOW Design Registry v0.1 Dress Rehearsal PASS

Date: 2026-05-29 Reviewer: GPT Council

Accepted state

MOW_DESIGN_REGISTRY_V0_1_MASTER_DESIGN_DRESS_REHEARSAL_AND_IMPLEMENTATION_BLUEPRINT passed in 8m55s.

Accepted facts:

  • Master Design v0.1 is complete.
  • Additive EXTEND dress rehearsal is GREEN.
  • Reuse-first implementation matrix remains REUSE 6 / EXTEND 12 / NEW 11 / DEFER 3.
  • Rehearsed: +8 nullable cols on workflows, +7 nullable cols on workflow_steps, +1 nullable col on workflow_step_relations, 8 FK constraints NOT VALID feasible, 2 candidate views compile.
  • Backlog quantified: 0/2 workflow designs IU-bound, 0/2 GOV-owned, 70/70 steps inline.
  • No committed DDL or mutation.

Prompt scaling lesson

The macro was too small for current agent capacity. Next task must bundle the important workstreams instead of only one stage:

  • human review/ratification packet;
  • commit readiness pack;
  • implementation blueprint;
  • DOT command family design;
  • UI data contract v0.1;
  • migration plan for 70 inline steps to IU refs;
  • test/acceptance harness;
  • governance/rollback runbook;
  • one large next prompt pack.

Next macro

Run:

MOW_DESIGN_REGISTRY_PHASE1_RATIFY_COMMIT_DOT_UI_MIGRATION_ACCEPTANCE_MEGACAMPAIGN

Purpose:

  • transform v0.1 from design/rehearsal into a complete Phase 1 execution package;
  • do not commit schema unless valid human approval artifact exists;
  • if no approval, produce final human-approved commit packet;
  • build DOT family specs and dress rehearsals where safe;
  • produce Master UI data contract and first UI proof data views without UI implementation;
  • produce 70 inline-step migration plan to IU refs;
  • produce acceptance harness and control tower.

Guardrails

  • No self-approval.
  • No committed DDL without valid human Đ32/council approval.
  • No UI/Nuxt implementation.
  • No 4 Mothers runtime.
  • No Directus/Qdrant/vector mutation.
  • No law enactment.
  • Preserve MOW as owner; no fifth Mother.
  • Preserve IU-centered invariant and no second SoT.
Back to Knowledge Hub knowledge/dev/reports/architecture/gpt-direction-after-mow-design-v01-rehearsal-pass-next-megacampaign-2026-05-29.md