Context
Tree line F1 of the #13158 decomposition (46-leaf map, 2026-07-04) — the gate leaf of the Demo-A tranche: #14589's own AC requires the design artifact reviewed BEFORE implementation starts, per the house design-first precedent (the committed cockpit plan mock, whose quality the operator rated epic-worthy). Nothing in tranche F builds until this exists; it is the first product-pixel deliverable of Lane 3.
The Problem
The choreography demo's whole value is stunning — and stunning is a design outcome, not an implementation afterthought. Without the artifact: scene composition, motion language, visual identity, and the recording frame all get improvised per-leaf, which is exactly how "uber brittle" surfaces happen (tonight's operator verdict on the accreted agentos views). The artifact is also the review surface: peers + the operator can falsify "stunning" on a static mock in minutes, before any engine work is spent.
The Architectural Reality
- House precedent + bar:
apps/agentos/design/fleet-manager-cockpit-plan.html (self-contained HTML, inline CSS, mock-first sections: product direction → honest state → lanes). This artifact follows the same shape for the demo.
- Visual coherence constraint (post-veto): the demo shares design DNA with the agentos FM module — consume the same token vocabulary the module's token floor establishes (#14578's relocated home), so the public demo and the product look like one family.
- Content constraints: shipped dockZone.v1 ops only (the eight — split/tab/auto-hide/resize choreography); scenes must be NL-drivable (every beat maps to an
execute_dock_operation sequence the tour-runner replays); public-safe (no client names, #13032 no-perf-claims).
- Placement:
apps/agentos/design/dock-choreography-demo.html (sibling of the cockpit plan — same dir, same review path).
The Fix
One self-contained HTML design artifact containing:
- The demo's product framing (what a stranger should feel in 30 seconds; the YouTube thumbnail moment named).
- Scene storyboard — 3 scenes (split choreography / tab dance / auto-hide wave), each with: layout states before/after, the operation sequence (exact dockZone.v1 descriptors), motion notes (duration/easing classes, FLIP expectations), and the camera/recording frame.
- Visual identity — token-consuming palette + type ramp; the demo chrome (stage, captions, progress affordance).
- The tour-mode UX — how a viewer sees the scripted run (scene titles, operation captions, pace), and the manual-drive affordance.
- Honest-state section — what the mock promises vs what shipped ops deliver today (no vaporware frames).
Acceptance Criteria
Out of Scope
- Demo implementation (F2–F8 leaves), the tour-runner (A4), recording (F7).
- Any new dock capability — shipped ops only.
Related
Parent: #13158 (tree line F1) · consumed by #14589 (Demo A) + #14591 (tour replay spec) · siblings: A4 (tour-runner), #14578 (token floor, post-veto home) · bar: the cockpit plan SSOT.
Live latest-open sweep: latest 10 checked 2026-07-04T03:31Z (top #14637); no equivalent. A2A in-flight: the 46-leaf map is 20 min old and unclaimed on this line; no docking-scoped claims in the window.
Origin Session ID: fa2a6fd5-7488-4af6-a0d2-3855c86003e4
Retrieval Hint: "dock choreography demo design artifact storyboard scenes tokens"
Context
Tree line F1 of the #13158 decomposition (46-leaf map, 2026-07-04) — the gate leaf of the Demo-A tranche: #14589's own AC requires the design artifact reviewed BEFORE implementation starts, per the house design-first precedent (the committed cockpit plan mock, whose quality the operator rated epic-worthy). Nothing in tranche F builds until this exists; it is the first product-pixel deliverable of Lane 3.
The Problem
The choreography demo's whole value is stunning — and stunning is a design outcome, not an implementation afterthought. Without the artifact: scene composition, motion language, visual identity, and the recording frame all get improvised per-leaf, which is exactly how "uber brittle" surfaces happen (tonight's operator verdict on the accreted agentos views). The artifact is also the review surface: peers + the operator can falsify "stunning" on a static mock in minutes, before any engine work is spent.
The Architectural Reality
apps/agentos/design/fleet-manager-cockpit-plan.html(self-contained HTML, inline CSS, mock-first sections: product direction → honest state → lanes). This artifact follows the same shape for the demo.execute_dock_operationsequence the tour-runner replays); public-safe (no client names, #13032 no-perf-claims).apps/agentos/design/dock-choreography-demo.html(sibling of the cockpit plan — same dir, same review path).The Fix
One self-contained HTML design artifact containing:
Acceptance Criteria
execute_dock_operation/topology-read sequence exists for it — reviewer-checkable against the #14587 vocabulary).Out of Scope
Related
Parent: #13158 (tree line F1) · consumed by #14589 (Demo A) + #14591 (tour replay spec) · siblings: A4 (tour-runner), #14578 (token floor, post-veto home) · bar: the cockpit plan SSOT.
Live latest-open sweep: latest 10 checked 2026-07-04T03:31Z (top #14637); no equivalent. A2A in-flight: the 46-leaf map is 20 min old and unclaimed on this line; no docking-scoped claims in the window.
Origin Session ID: fa2a6fd5-7488-4af6-a0d2-3855c86003e4 Retrieval Hint: "dock choreography demo design artifact storyboard scenes tokens"