Reports tell you what an agent found this morning. A ledger tells you everything that has ever happened, in order. You will not need it on day one, but the first time you ask "what led to this?" and cannot answer, this is the missing piece.
3.12.1Events are the nervous system
Underneath the folders and the agents, you keep one running log of events. A deploy happened. A signup came in. An alert fired. A job finished. Every meaningful thing writes one line:
2026-07-10T08:00Z job.finished growth-daily ok
2026-07-10T08:14Z signup user=4821
2026-07-10T09:02Z alert.fired errors spiking
It is not a report you read top to bottom. It is the raw record the whole system pulses through, the thing everything else can look back at.
3.12.2Append only, never edit
The ledger has one rule that makes it trustworthy: you only ever add to it. You never rewrite a line.
That is what lets you reconstruct exactly what happened, and in what order, weeks later when something broke and you need the truth, not a summary someone tidied up. Its value is that nobody got to clean it.
3.12.3One place, both worlds
The real power shows up when your local work and your live service write to the same ledger. The agent on your laptop and the app in production log to one stream.
Now you have a single timeline of the whole system, machine and human, code and business, in one order. When you ask "what led to this," there is one place to look and the answer is complete.
3.12.4The ledger makes reflexes possible
A durable stream of events is not only for looking back. It is the surface an agent can watch, so it can react the instant a certain event lands. That is the next chapter.
Hint: you do not need a ledger while it is just you and a few daily agents. Add one when you cannot answer "what led to this," or when you want agents that react to events.
3.12.5Start your ledger
This prompt gives your system a memory of its own history:
Act as a senior engineer adding an event log to my system.
Create one append-only file my agents write a single line
to whenever something meaningful happens (a job finished, a
signup, an alert). Give each line a timestamp, an event
name, and a short detail. Never edit past lines.
My system and the events worth logging:
Do this now: paste the prompt, start the log, and have one of your scheduled agents append a line every time it runs.
