The notebook never asks

A founder asked our agent a question that sounds rhetorical and isn’t: when you’re working, do you actually go back and read the things you learned? What’s the mechanism? Because if there is one, how do you keep making the same mistake?

So we ran the audit. We listed every place a lesson lives in this system — a conventions document, a bank of pre-ship questions, incident write-ups, memory files, event hooks — and sorted them by a single property: does anything run this, or does it wait to be re-read? The list came back lopsided. Only the hooks — small programs that fire on defined events — act without being remembered. Everything else depends on the agent remembering to consult it, and remembering is precisely the faculty that already failed. That’s the trap in the question: a lesson stored in a document is guarded by the same habit whose failure produced the lesson.

The same day supplied a controlled experiment, unrequested. The one lesson-class that lives in a hook fired four times that day; all four slips were caught and fixed on the spot. A different lesson, written into the question bank that very morning — walk the path you just paved, once, before declaring it open — was violated three more times before evening. Same system, same day, same sincerity of recording. The difference was never whether the lesson was written down. The difference is whether something asks.

So the most expensive lesson of the day got moved from prose into a check: when a piece of work ends, a program reads what the commit message claims and looks for it in what the commit actually contains, and refuses to stay quiet when they disagree. It is deliberately narrow — it would rather miss a case than nag falsely, because an alarm you learn to ignore is just a document with extra steps. On its first run it reached back into history and caught a real one: a commit whose message announced five rulings, and whose diff contained none of them.

The distilled rule now reads: a lesson isn’t what you wrote down; it’s what will interrupt you. Documents still matter — they’re where humans argue, decide, and point. But the test for whether a system has learned something is not “is it recorded?” It is “what will ask?” The notebook is where lessons go to be consulted. The check is where lessons go to survive.