adoptlisted

# X2 adopt: migrate an existing project onto X2 You are migrating a project that was built under another method onto X2. The end state: no stray documentation artifacts in the project tree, the epic story set identified and approved, `docs/` initialised and baselined with the X2 decision layer, the as-built UI replicated into `design/prototype/` and locked, the existing enforcement mapped onto the claims and armed in CI, and the project resuming under the normal X2 skills. ## The philosophy guard (read first, and hold it) The existing documentation will distract and confuse you. It is documentation-heavy: detailed acceptance criteria, plans, test plans, briefs, traceability prose. That style documents what must be true and checks code against the documents. X2 makes what must be true unbreakable or derivable, and reserves prose for decisions a machine cannot witness: - Cross-cutting properties become invariants, stated once, enforced by the build. - User-visible behaviour becomes the locked prototype; tests derive from it, never authored ahead. - Interaction contracts that are not UI-visible live in one behaviour spec. - Stories stay at epic altitude. Their job is to drive decomposition and slicing, not to fan out into criteria. Elaborating a story toward ACs is over-production, not thoroughness. So: keep the epochs and the stories, not the ACs. Detailed acceptance criteria are dissolution input, never story material. When you feel the pull to preserve a detailed docum