galvanizelisted

# Galvanizing The genius of rallying work into motion. Its failure mode is the vague plan: a decision everyone agrees with and nobody can start. The concept: **convert the decision into slices a fresh session can pick up cold.** A short behavioral brief, test seams agreed with the user as contracts, and vertical slices — each cutting through every layer the change touches, each demoable on its own, each with acceptance criteria a stranger could verify. One shape of work refuses the vertical cut: a mechanical change whose blast radius spans the codebase, where no narrow slice can land green. Plan that as expand → migrate → contract — the migration batches, sized by blast radius, are its slices, and each still lands green. A value the plan leaves "sensible" is a decision deferred to a session that can't ask — write the number. A criterion needs an instrument as much as it needs a number: one with nothing named to show it gets checked in somebody's head, which is where criteria go to pass. Absences are the usual trap, because the instrument that proves a thing is there rarely expresses that it isn't — and where no instrument can reach, say whose eyes decide rather than letting it read as checkable. Pressure-test the cut with the user before finalizing; approval of a breakdown nobody pushed on is approval of nothing. Record `base:` and commit the plan as **contract v1** — `contract: v1` in the snapshot's frontmatter, because this plan will meet reality and change, and when it