A Summary Written After the Fact Tells a Plausible Story, Not a True One

Three hundred fifty-five old work sessions turned into 1,748 separately tracked pieces of work in one pass, and the very first thing the process that checked them caught was a mislabeled record, a piece of work credited to the wrong source.

That result changed how I think about a single stretch of work sitting in a chat log or a meeting note. It isn’t a blob of context that just evaporates once the conversation ends. It’s a real piece of work, with a beginning, a sequence of decisions, a result, and a claim about that result that can actually be checked later, if you bother to build it that way.

The reason to do this at all was a weekly habit that had quietly become unreliable: trying to remember what had happened over the past week well enough to report on it honestly. That’s a different problem than it sounds like. A summary written from memory, even an honest one, can only tell a plausible story about what happened. It genuinely cannot answer more specific questions, like which part of a long session actually shipped, which conclusion got verified against something real, or where a particular claim in this week’s report actually came from. Memory smooths things into a narrative. A narrative isn’t evidence.

The fix was treating each session as something to break down into its real, individual pieces of work, each one carrying its own status, whether it was verified, and what actually happened, tied back to the real record, not to how the week felt in hindsight. Everything else, a weekly report, a daily note, this very sentence, is meant to be a view over that underlying record, never a replacement for it, because a surprising or disputed number in a report should always be traceable back down to the specific pieces of work that produced it.

Doing this at scale came with its own trap. The first instinct was to backfill everything, all of history, in one unbounded pass, and that risked running away across years of records with no natural stopping point. The fix there was ordinary and easy to overlook: explicit, bounded batches, with a separate routine to pick up anything still left over afterward, rather than one process trying to swallow everything at once.

The most useful part of the whole effort wasn’t the final count. It was what the verification step caught while building it: a real attribution bug, crediting work to the wrong source, and a couple of other genuine mistakes in the system doing the recording, each one fixed at its actual source rather than patched over in whatever report happened to be showing it. A manually patched report isn’t a record. It’s a document with better formatting.

If your own team reports on its work from memory

Ask, honestly, whether last week’s summary could survive someone asking “show me exactly where that came from.” If the honest answer is “I remember it that way,” that’s not the same thing as a record. A summary built after the fact will always sound plausible. Only a record built at the moment work actually happens, broken into pieces small enough to check individually, can tell you what’s actually true.

dxdev LESSON · paste into your AI coding agent
LESSON: Only a record built at the time work happens can answer what actually shipped
WHAT TO SHARE: Describe how your team currently reports on what got done, whether it's a weekly summary, a status meeting, or a report pulled together after the fact.
ASK YOUR AGENT TO:
1. Identify whether the current reporting method is built from a record made at the time work happened, or reconstructed afterward from memory or a general summary.
2. List a few recent claims from a status report or summary that couldn't easily be traced back to a specific, verifiable piece of work.
3. Propose the smallest change that would make future reporting a view over a real record, rather than a retelling from memory.
RETURN: A short table of current reporting method, whether it's traceable, and the smallest fix.
BOUNDARY: Analysis only. No agent should run an unbounded backfill or bulk process across your history without an explicit limit set by a person first.