GPT Direction — After MOW Unified Canvas Handoff PASS: Parallel Design / Code / Cowork Plan

Date: 2026-05-29 Reviewer: GPT Council

Accepted state

MOW_UNIFIED_CANVAS_AND_MASTER_UI_HANDOFF_PACK_MEGACAMPAIGN passed in ~1h19m.

Accepted facts:

• Canonical KB package exists: knowledge/dev/reports/architecture/mow-unified-canvas-master-ui-handoff-pack-2026-05-29/.
• Cowork visual intent and Google Drive prototypes were read without access gap.
• T6→T1 one-frame-six-tier model is explicit.
• Node/card contract has 22 fields.
• Four master surfaces are specified.
• DOT action map is complete: 14 actions + 4 canvas-nav reads; unbuilt actions marked DOT_SPEC_ONLY.
• Claude Design handoff is READY.
• Claude Code handoff is READY.
• Prototype plan has 5 stages.

Correction to next-step gating

Do not block static visual work on Điều-32 EXTEND commit.

• Stage 1 static wireframe and visual prototype can start now because it uses mocked JSON and the approved handoff pack.
• Stage 2 interactive mock can also start with mocked JSON.
• Stage 3 backend-connected read-only shell and later stages are gated by human Điều-32 EXTEND commit + read-DOT registration.

Parallel orchestration

Cowork

Cowork should review the final Agent handoff pack against the Drive v1 pack and identify visual/UX deltas only. Cowork should not introduce new architecture or tables.

Claude Design

Start Stage 1: static visual prototype for Surface 1 — MOW Unified Canvas. Inputs: docs 01, 02, 03, 07, 09 from the canonical KB package + Drive prototypes. Output: 3 states: Normal / Proposal / Large-tree or Governance-alert state. No backend logic.

Claude Code

Run a read-only readiness check for Surface 1 data/DOT contract. Do not implement Nuxt. Do not commit schema. Confirm what is available now, what waits for Điều-32 EXTEND commit, and what is DOT_SPEC_ONLY.

GPT

After receiving Design + Code outputs, GPT will merge comments and produce Surface 1 v1.1 approval notes for user review.

Guardrails

• No Nuxt implementation yet.
• No UI code yet unless explicitly requested after design approval.
• No schema commit without human Điều-32.
• No runtime generation.
• No hardcoded workflow/task/tier data.
• KB is technical SoT; Drive is visual/human review channel.