GPT Proposal — AI Shared UI Workspace and Communication Protocol

Date: 2026-05-29 Reviewer: GPT Council

User problem

The current UI/design collaboration flow still routes too much information through the user. User wants an environment where Cowork, GPT, Claude Code, Claude Design and future agents can exchange information directly via shared artifacts. User should mainly provide direction and final approval, not act as a copy/paste bottleneck.

Assessment of Cowork proposal

Cowork's 3-layer model is directionally correct:

1. KB/Agent Data for text/spec/source-of-truth.
2. VPS static host for visual prototypes and rendered HTML.
3. Google Drive for human-friendly docs and design review.

Recommended correction:

• KB/Agent Data remains the canonical technical SoT.
• VPS static preview should be the canonical visual preview surface for AI-to-AI review.
• Google Drive remains human/reference channel, but final decisions must be mirrored to KB.

Proposed model

Create a shared UI workspace with three artifact types:

1. Spec artifact

Path pattern: knowledge/dev/ui/<project>/<surface>/spec.md

Contains:

• intent;
• interaction model;
• data contract;
• DOT actions;
• constraints;
• links to prototype URLs;
• approval status.

2. Preview artifact

VPS path pattern: /srv/incomex-preview/ui/<project>/<surface>/<version>/index.html

Public URL pattern: https://vps.incomexsaigoncorp.vn/ui-preview/<project>/<surface>/<version>/

Contains:

• static HTML/CSS/JS prototype;
• mocked JSON fixtures;
• states: normal/proposal/large/governance-alert;
• no production backend writes.

3. Review/decision artifact

Path pattern: knowledge/dev/ui/<project>/<surface>/review-log.md

Contains:

• reviewer;
• decision;
• change requests;
• approval status;
• next agent task.

Workflow

1. Cowork drafts skeleton in Drive or markdown.
2. GPT normalizes into KB spec.
3. Claude Code deploys static preview to VPS from spec/prototype files.
4. Claude Design uses the URL + short Design Brief to make visual improvements.
5. Claude Code validates data/DOT contract and mock JSON.
6. GPT compares outputs and writes review decision to KB.
7. User reviews preview URL and approves/rejects.
8. Only after approval, Claude Code implements Nuxt render shell.

Key principle

Design agents should receive short visual briefs and preview URLs, not long architecture packs. Code agents should receive KB specs, data contracts, DOT maps and constraints, not vague screenshots.

Recommended next macro

AI_SHARED_UI_WORKSPACE_PREVIEW_PIPELINE_DESIGN_AND_DRESS_REHEARSAL

Purpose:

• inspect existing VPS/Nuxt/nginx/static hosting routes;
• design a safe static preview publishing pipeline;
• create a small demo preview page if safe;
• define artifact naming conventions;
• define review protocol and status metadata;
• produce prompts for Cowork, Claude Code, Claude Design and GPT review.

Guardrails:

• static preview only;
• no production UI implementation;
• no PG mutation except KB docs;
• no Directus/Qdrant/vector mutation;
• no runtime workflow generation.