All writing
Notes on building

Generate, Don't Maintain

The spreadsheet on your screen is not the truth. It is a photograph of the truth, and the day you start editing the photograph is the day it begins to lie to you.

June 10, 2026 · 4 min

Most of the working documents in a business are not sources of truth, even though they are treated as if they were. A workbook, a report, a menu, a dashboard. They look like the record, but they are artifacts: a rendering of something underneath, which is the actual data. The trouble starts the moment you forget that and begin treating the rendering as the thing itself.

Picture a job-cost workbook, the kind a contractor lives inside all day. It started clean, every number tied back to where it came from. Then a job got added by hand. Then a column was nudged so a total would look right. Then someone typed a figure straight into a cell because the import was a hassle that particular afternoon. Six months on, nobody can say which numbers are real and which were patched in. The file still opens. It still adds up. It is just quietly wrong, and it has been wrong for a while.

Generate, don't maintain — a maintained copy drifts from the source over time while a generated one stays locked to it A chart over time. A flat gold line, "generated," sits on the source-of-truth baseline and is refreshed at intervals. A gray dashed line, "maintained," forks off the same start point and drifts steadily upward and away, opening a labeled gap of silent error by the right edge. PRINCIPLE — GENERATE, DON'T MAINTAIN The copy drifts. The render doesn't. Maintain a document and it wanders from the truth. Regenerate it and it cannot. drift time maintained — drifts silently generated — regenerated, always current silent error Edit the artifact and error accumulates unseen · regenerate it and every version is current

The rendering is not the record

The fix is not more discipline about how you edit the workbook. The fix is to stop editing it at all. You keep one place where the real inputs live, and you generate the workbook fresh from those inputs whenever you need it. The file on your screen becomes disposable, a print made from the negative rather than the negative itself. If it comes out wrong, you do not repair the print. You correct the input and print it again.

Two things happen when you work this way, and both of them are the whole point. New things flow through on their own: add a job to the source and it simply appears, in every total, without anyone having to remember to wire it in. And bad inputs get caught instead of absorbed. A generator can refuse to render a file it cannot trust, where a person maintaining a workbook by hand will paste the mess in and keep going, because stopping feels like the bigger problem. A hand-kept file fails silently. A generated one fails loudly, and a loud failure is the only kind you can actually fix.

My restaurant runs this way now, in places I no longer think about. The daily sales summary is not a file anyone updates; it is regenerated from the register's own records every morning, so a day I had forgotten about still shows up correct. The menu on the website is not typed by hand; it is rendered from a single table, so a price change happens in one place and lands everywhere at once. Nearly every time I have been burned over the years, it was because I had quietly started maintaining a copy instead of regenerating it, and the copy had drifted somewhere I was not looking.

So when someone hands me a spreadsheet they have been faithfully keeping current for a year, my first question is no longer whether it is right. It is where this comes from, and whether we could simply make it again. A document you maintain decays the moment you look away from it. A document you generate is correct the instant you ask for it, and it has the decency to tell you when it cannot be.

/ar/