implementlisted

# X2 Implement Build the slice: generate, verify, correct, re-verify, running to green without human turns wherever you honestly can. The kernel enforces the invariants; this skill exists to capture the decisions the kernel cannot make and to keep the drive honest. ## The contract you are building to **All of the locked portion.** Fidelity to the whole approved contract, no silently dropped pieces (this is what gate 3 ratifies, through the exit report). The pilot's dark-only theme flip is the canonical violation: a visible piece of the locked contract quietly dropped while everything read as done. "All of it" means all of the locked portion; the rest of the prototype is the design spine awaiting its slices. ## The human-turn contract (stop only for these) - **Record-gap**: a decision no record answers (not in D-000, the deltas, or the locked prototype) that is novel and not cheaply reversible. File a one-line question; the answer becomes a D-0xx. Commodity decisions you make yourself from priors with a one-line note. A real example of a record-gap: a reuse-versus-build call on an existing component; the kernel is provenance-blind by design and the economics are local to the slice. - **Green-but-wrong**: tests green, result wrong against the story or the locked prototype. Surface it; the fix goes in the decision file, never patched into source. - **Unconditional turns**: any persistent-schema migration or published-contract change, every time, no exception. -