Prototype To Design

/prototype explores. This approves one of what it explored and splits the result by lifetime: the durable half is a design ticket carrying the measurements, and the throwaway half is an HTML page speaking only the token contract, alone on its own branch. design-to-code then runs once per ticket against both.

Nothing lands on main. A design file on main is a live file with an owner: it goes on being edited long after the screen it describes has shipped, and it drifts from the ticket that asked for the screen and from the page that shows it. Two copies can be kept in step by deleting one of them on a known day. Three cannot.

A prototype settles one of two things. Unsettled behaviour ("does this state model work?") goes /prototype → /handoff → /to-spec, and never through here. Unsettled appearance ("what should this screen look like?") goes /prototype → here → /to-spec → /to-tickets → /design-to-code per ticket → /pixel-review, because a UI prototype's decision is a set of measurements and prose loses every one of them. Both: the behaviour prototype first, cheap and throwaway, then the appearance route.