GPT Direction — Parallel Agent/Cowork UI Handoff Orchestration

Date: 2026-05-29 Reviewer: GPT Council

Current situation

Agent is running MOW_UNIFIED_CANVAS_AND_MASTER_UI_HANDOFF_PACK_MEGACAMPAIGN to create the canonical KB handoff package. Cowork has independently created MOW_UNIFIED_CANVAS_UI_HANDOFF_PACK_v1 in Google Drive and uploaded knowledge/dev/ui/mow-unified-canvas-handoff-pack-v1.md to KB.

Council assessment

Cowork's direction is accepted with two corrections:

1. Claude Code does not write business-specific UI, but it may later implement reusable shell components after Claude Design/User approval.
2. Correct order is: Handoff Pack → Claude Code validates data/DOT readiness → Claude Design creates visual/wireframe → User approves → Claude Code implements shell.

Parallel orchestration

Cowork now

• Maintain the Google Drive visual/reference pack.
• Keep Surface 1 only: MOW Unified Canvas.
• Add/verify six required sections: Intent, Interaction, Data Contract, DOT Actions, Visual References, Constraints.
• Do not expand to all 4 surfaces yet.
• Do not request implementation.

Agent now

• Finish KB canonical handoff pack.
• Reconcile Cowork v1 with the existing MOWD Phase 1 data contracts and DOT family.
• If Cowork v1 exists in KB, explicitly compare it against the canonical pack and produce merge notes.
• No UI code, no Nuxt, no PG mutation.

GPT after Agent report

• Review the Agent package and Cowork v1 together.
• Produce a single approved MOW Unified Canvas Surface 1 Handoff v1.1 if needed.
• Then issue two separate prompts:
  1. Claude Code: data/DOT contract validation only.
  2. Claude Design: visual/wireframe prototype for Surface 1.

Governance

KB remains the canonical technical source of truth. Drive remains the human/visual reference channel. Any final decision must be reflected in KB.

Do not do yet

• No Nuxt implementation.
• No shell component code.
• No UI implementation across all 4 surfaces.
• No committed DDL.
• No runtime.