Write + commit per decision (not per session)

Each locked decision ? knowledge/ + committed as discrete unit. Not batched end-of-session

Write + commit per decision

Rule

When the user locks a decision in chat, write the corresponding knowledge file AND commit it as a discrete unit before moving to the next decision. Don’t accumulate edits and batch-commit at session end.

How to apply

• Lock decision -> write file -> stage -> commit -> continue. One decision = one commit (subject to adaptive granularity, see adaptive-commit-granularity).
• Commit message: docs(knowledge): lock <slug> — <one-line summary>.
• Exception: a batch grill session (3+ related decisions in one sitting) commits as one — see adaptive-commit-granularity.
• Push when the user says push; never auto-push.
• Per self-update-rule, this is non-negotiable for durable decisions.

Why

User locked this on 2026-06-26 (Q12). Per-decision commits give a clean revert surface and a readable git log; batched end-of-session commits hide the trail.

Captured

2026-06-26 session, Q12 of 24-question grill.

Related

• self-update-rule
• adaptive-commit-granularity
• keep-knowledge-fresh (§4 current-truth-only is the no-transcript rule this used to point at)

Edit on GitHub · Back to index