KB-761D

GPT Direction — After MOWD Phase1 PASS to Unified Canvas UI Handoff (2026-05-29)

2 min read Revision 1
gptmowdmow-design-registryui-handoffunified-canvasclaude-design2026-05-29

GPT Direction — After MOWD Phase 1 MegaCampaign PASS → Unified Canvas UI Handoff

Date: 2026-05-29 Reviewer: GPT Council

Accepted state

MOW_DESIGN_REGISTRY_PHASE1_RATIFY_COMMIT_DOT_UI_MIGRATION_ACCEPTANCE_MEGACAMPAIGN passed.

Accepted facts:

  • Phase 1 execution control tower exists.
  • Human ratification packet is ready.
  • Commit readiness packet is ready.
  • DOT family is specified: 15 DOTs, 6 read DOTs rehearsal GREEN, 9 mutating deferred.
  • Master UI data contract exists for 4 surfaces.
  • Inline-step IU migration plan exists for 70/70 steps.
  • Validation harness defined and partially executed.
  • Pilot scenario WF-001 ready.
  • No committed mutation.

Strategic next step

Do not commit schema or runtime yet unless human approval exists. The next valuable work is to bridge Cowork UI intent, MOW unified canvas visual model, data contract, DOT actions, and future Claude Design/Nuxt handoff.

Run:

MOW_UNIFIED_CANVAS_AND_MASTER_UI_HANDOFF_PACK_MEGACAMPAIGN

Purpose:

  • convert scattered Cowork UI screenshots/prototypes into a canonical UI handoff pack;
  • preserve T6→T1 single-canvas model;
  • bind each UI surface to existing read models/data contracts and DOT actions;
  • create Claude Design handoff and Claude Code handoff separately;
  • produce wireframe-level specs, not Nuxt implementation;
  • preserve backend-enforced visibility and no frontend business logic.

Guardrails

  • No Nuxt implementation yet.
  • No UI business logic.
  • No hardcoded workflow/task/tier data.
  • No committed DDL.
  • No 4 Mothers runtime.
  • Reuse existing Phase 1 data contracts and DOT family.
  • UI should be a render shell over backend views/functions/DOT.
Back to Knowledge Hub knowledge/dev/reports/architecture/gpt-direction-after-mowd-phase1-megacampaign-pass-next-ui-handoff-2026-05-29.md