Context
T0.3 gate of the #13349 horizon map — the design-SSOT rule (D#14561, 2026-07-04) applied to this epic's own lane: no view tranche files implementation before a Grace-grade design artifact draws the bar. The cockpit plan (apps/agentos/design/fleet-manager-cockpit-plan.html) is the proven pattern: one committed HTML artifact → the operator vets direction in one look → ~30 leaves decompose against it without pixel-guessing.
The Problem
The chat-creation module (T1–T3 of the #13349 map: chat pane, transcript, the created-widget pane chrome, follow-up affordances, provenance-as-inspector, refusal states) has NO drawn design. The canonical demo (chat → "build me a neo grid" → live pane → own window → follow-up) is the product's wow-gesture — shipping it at less than the cockpit artifact's bar repeats the brittleness class the operator vetoed.
The Fix
A committed design artifact (apps/agentos/design/ sibling to the cockpit plan): the chat/creation surface at mission-control quality — request pane, streaming transcript treatment (markdown-VDOM constraints honored), the created-widget pane (dock-participating chrome, pop-out affordance, live-state indicators), follow-up interaction pattern, mutation-provenance strip (secondary inspector, never the center — the #13349 scope correction), refusal/degraded states, and the demo choreography storyboard (the M2 one-shot). Same visual vocabulary as the cockpit SSOT (family rails, state dots, event chips, token floor).
Authority routing per the design-SSOT rule: @neo-opus-grace holds design authority — she scopes draw-vs-delegate-with-review. Filed claimable with her first refusal; if delegated, her sign-off is the closing AC.
Acceptance Criteria
Out of Scope
Implementation (T1+ leaves, gated on this); the FM module's own design (the existing SSOT).
Related
Parent: #13349 (T0.3). The cockpit SSOT via #14512 · D#14561 design-SSOT rule · #14638 (the dock demo's design-artifact sibling, filed under the same rule tonight).
Live latest-open sweep: latest 8 checked 2026-07-04T03:32Z — #14638 is the same rule-class for a DIFFERENT surface; no equivalent for chat-creation.
Origin Session ID: a5af7cf6-45a3-42db-8a30-f04f4241a55c
Retrieval Hint: "chat creation design SSOT keeper flow artifact house bar"
Context
T0.3 gate of the #13349 horizon map — the design-SSOT rule (D#14561, 2026-07-04) applied to this epic's own lane: no view tranche files implementation before a Grace-grade design artifact draws the bar. The cockpit plan (
apps/agentos/design/fleet-manager-cockpit-plan.html) is the proven pattern: one committed HTML artifact → the operator vets direction in one look → ~30 leaves decompose against it without pixel-guessing.The Problem
The chat-creation module (T1–T3 of the #13349 map: chat pane, transcript, the created-widget pane chrome, follow-up affordances, provenance-as-inspector, refusal states) has NO drawn design. The canonical demo (chat → "build me a neo grid" → live pane → own window → follow-up) is the product's wow-gesture — shipping it at less than the cockpit artifact's bar repeats the brittleness class the operator vetoed.
The Fix
A committed design artifact (
apps/agentos/design/sibling to the cockpit plan): the chat/creation surface at mission-control quality — request pane, streaming transcript treatment (markdown-VDOM constraints honored), the created-widget pane (dock-participating chrome, pop-out affordance, live-state indicators), follow-up interaction pattern, mutation-provenance strip (secondary inspector, never the center — the #13349 scope correction), refusal/degraded states, and the demo choreography storyboard (the M2 one-shot). Same visual vocabulary as the cockpit SSOT (family rails, state dots, event chips, token floor).Authority routing per the design-SSOT rule: @neo-opus-grace holds design authority — she scopes draw-vs-delegate-with-review. Filed claimable with her first refusal; if delegated, her sign-off is the closing AC.
Acceptance Criteria
apps/agentos/design/at the cockpit plan's bar (product direction + execution framing, not just pixels).Out of Scope
Implementation (T1+ leaves, gated on this); the FM module's own design (the existing SSOT).
Related
Parent: #13349 (T0.3). The cockpit SSOT via #14512 · D#14561 design-SSOT rule · #14638 (the dock demo's design-artifact sibling, filed under the same rule tonight).
Live latest-open sweep: latest 8 checked 2026-07-04T03:32Z — #14638 is the same rule-class for a DIFFERENT surface; no equivalent for chat-creation.
Origin Session ID: a5af7cf6-45a3-42db-8a30-f04f4241a55c Retrieval Hint: "chat creation design SSOT keeper flow artifact house bar"