locklisted

# X2 Lock Copy the approved design artifact down into the repo, verify it is complete, stamp its provenance, and request the lock. The lock is the acceptance contract for the slice; everything the builder ships is held to it. The pilot ran without this step and paid twice: the design system was never imported so the client's tokens were scraped from what happened to be readable inline (MET-04), and the prototype was treated as locked for days before anyone asked for the approval (turn 25). ## The import Pull the complete artifact set from the design project into `design/prototype/` (the canonical home, INV-01): - the prototype source (`<name>.dc.html`), - the **complete** design-system export under `_ds/` (the token css, component css, fonts), - the supporting scripts. The sanctioned route is the on-disk export: the owner places the design project's complete export in the repo (a handoff folder under `design/`), the lock copies out what it needs and deletes the handoff. A context-carried import (the design MCP) is the fallback for small artifact sets; it cannot carry binaries, and the third project moved to the on-disk route after channel limits bit. Either way, verify the copied tree against its source: the file inventory matches and no copy artifacts exist (a duplicated or nested directory survived the third project's import verification and was caught only by the owner's eye). Never derive tokens from values readable inline in the prototype source. The pilot did, and