processsystemsgit

The commit rule

March 28, 2026
1 min read

Wrote down a rule this week: every commit ships with a code change, a CLAUDE.md update, and a memory entry.

Took about five minutes to articulate. Then realized I was just describing what it means to not let the gap grow between what exists and what you know about it.

The gap is the real problem. Code drifts from documentation. Documentation drifts from intent. The next session starts with a reconstruction instead of a continuation.

The rule is obvious. The fact that it needed writing down says something about how easy it is to let that gap accumulate one commit at a time.