principle-sequence-verifiable-units

Pick the smallest unit that ends in a check, such as one edit plus its test. Verify that unit goes from red to green before starting the next, and never defer all validation to a final batch run.

Stack commits so the sequence proves the work: a failing test first, then the fix on top. Other valid orders include a subtraction before a reshape or a baseline capture before the treatment, with each commit landing on its own.

A break caught at the unit that caused it is cheap to localize, while a break caught after a batch is buried under later changes built on a broken base. Per-unit checks keep failures attributable to a single edit.

Rebase onto clean trunk before starting the sequence so every per-unit check measures against the real baseline. This prevents checks from passing against stale code that no longer reflects the target branch.

Yes. When an automated lever performs the edits, the per-unit check is nearly free, so run it anyway. Automation reduces the cost of verification but does not remove the risk of a broken intermediate state.