Prototype to final development
A sequence of evidence gates, not a list of impressive features.
Prototype gate
Demonstrate the core mechanic with deliberately limited art and systems. Resolve the largest unknown first. Preserve a reproducible source snapshot and record what the prototype proves, what it does not prove and what will be discarded.
Vertical slice gate
Build one representative end-to-end experience with the intended controls, feedback and state handling. Use it to validate the production approach, screen system and device performance before multiplying levels or modes.
Feature-complete gate
Close the agreed scope, remove development-only controls and review lifecycle, persistence, errors and optional services. Confirm licences and asset provenance. Freeze new features unless a change resolves a release-critical problem.
Release-candidate gate
Identify the exact build, run regression tests and request independent review through Eleanor. Liam owns implementation coordination, Daniel owns supporting infrastructure. A candidate becomes ready only when the recorded acceptance conditions are met; the website must not skip intermediate states.