Don't forget — obligation as automation

Agents forget. Written rules and chat promises are soft — they compete with context, get skipped under pressure, and vanish in new sessions.

Default: when the user asks for something that must happen repeatedly or was forgotten before, encode it in executable machinery the next agent cannot bypass without breaking the build.

The agent picks the highest tier that fits this repo — CI step, hook, failing test, codegen diff, npm script chain, etc. The "software" is whatever executable gate matches the obligation and trigger; not a fixed recipe.

Not "AI safety guardrails" — enforcement: repo machinery that fails when an obligation was skipped.

When to use

• User says: always, every time, never forget, on each deploy, before every commit, don't let this slip again
• Same instruction was given in a prior session and not followed
• A counter, check, sync step, or enforcement must survive session handoff
• User prefers "put it in the build" over "remember to do X"

When NOT to use