Skip to content

Claude Design handoff — acceptance

Target

This page describes intended behaviour or structure. No implementation is claimed unless a section is explicitly marked Current implementation or Evidence.

A prototype is accepted when every line below is demonstrated with the shared fixtures and recorded in the route-state coverage export.

Operation

  • Keyboard-only completion of all nine flows including every adverse branch; focus visible and restored after dialogs and sheets; escape closes; no traps in embedded views.
  • Desktop 1440×900 and mobile 390×844; drawers become full-screen sheets; tables scroll horizontally with sticky headers; targets at least 24×24.
  • Light and dark schemes with contrast 4.5:1 text and 3:1 UI; the seven status colours carry text and icons.
  • en, ru (LTR) and he (RTL): mirrored rail, chevrons and layout; identifiers, code and logs LTR; dates, numbers and currency per locale.
  • Reduced motion: transitions and animated live updates disabled; streaming text paged.

Coverage

  • Every screen of the screens catalog exists at its route with its global states (loading, empty, validation error, degraded source, permission denied, stale version conflict, success).
  • Every state family is rendered distinctly on the screens that declare it; no colour family is reused across vocabularies.
  • Every role of the permissions catalog is demonstrated, including Maya (observer) seeing no action controls and a denied navigation entry.
  • The prototype alignment is honoured: kept and renamed destinations are dedicated views; merged ones appear as sections; retired ones do not exist.

Experience requirements demonstrated

FUX Demonstration
FUX-01 scope switch that grants nothing; denied switch explained
FUX-02 asset catalog with release readiness; Draft not selectable for a run
FUX-03 run submission with revision, profile and limits
FUX-04 run timeline with freshness; projection lag visible
FUX-05 approval card bound to version 3; 412 renders version 4
FUX-06 artifacts with lineage and citations from the context snapshot
FUX-07 recovery from a Paused run with an uncertain effect; checkpoint restart
FUX-08 usage by status with uncertain separate; quota wait explained
FUX-09 knowledge sources, memory promotion with consent
FUX-10 evaluation verdict and evidence on a release; waiver gated
FUX-11 blueprint → recipe → proposal → pipeline → promotion → operated product
FUX-12 every screen links to its catalog entry and design page

Non-goals

No live backend, production metrics or implementation percentages; no element-level component design beyond the design-system catalog; no new top-level destinations.