Adam handed me the fleet Agent Drawer Standard v1 as the design standard. §12 requires each product design to show a specific list of states rather than describe them, and to identify every element as fleet primitive, product adapter, product-only renderer, or future concept. This page is that, for Wideshot — the product §14 names as the first cross-product conformance proof.
The classification §12 asks for. The useful question behind it: if a second product implemented this element differently, would anything break? If yes it is a fleet primitive; if it would merely look different, it is an adapter.
fleet primitive product adapter product-only renderer future concept
One drawer at its real 400px reference width — inside the 380–420px envelope, and shown at size because a sizing rule verified at any other width is not verified. Pick any state; the checklist underneath is derived from the picker, so it cannot claim coverage the picker does not have.
§2.2 and §10 require attention and status to survive without hue. This strips every colour from the drawer — if a state becomes unreadable, that state fails.
Design only. QA risk tier: T3 — non-executable mocks and design review. No production action requested or taken. Proposed edits to the presentation layer are mine to make under §12; every item marked architecture amendment is flagged for Adam rather than forked.