helix

Migrate or build one screen or feature into the target codebase through small, ordered checkpoints, each of which must pass four gates in order — behavior (user-perspective tests), UI review (reference vs build screenshots, scoped to the checkpoint), adversarial code review by two independent reviewers against the documented guidelines, and engineer approval — with engineer feedback remembered so later checkpoints need less oversight. Optimize for reliable convergence, not a perfect first attempt: an attempt may be wrong; it may not pass until it is not. Output a stack of committed checkpoints with their evidence on a helix/<slug> branch; never merge, push or publish.