Why do you only remember the highlights of a month, not the month itself?

Ask yourself what March was like and what comes back first is rarely March. It is one dinner, one argument, one afternoon that went unexpectedly well — a handful of frames standing in for thirty-one days you can otherwise barely account for. The month itself, the actual bulk of it, is gone. Only the peaks survived, and somewhere along the way one of those peaks quietly became the whole month.

Memory keeps the exception, not the average

You did not lose March. Most of it was never going to be kept in the first place, because most of it was not distinct enough to keep. Memory is not a recording device running continuously in the background; it is closer to a filter that lets the unusual through and lets the ordinary drain away. A Tuesday where you worked, ate dinner, and went to bed leaves nothing behind, because there was nothing about it to file separately from every other Tuesday. A Tuesday where a friend called crying, or a project fell through, or something went unexpectedly well gets kept, because it stood out against the pattern around it. Twenty-six ordinary days and five distinct ones do not survive the month equally — the ordinary ones disappear almost immediately, and the distinct ones are all that is left to answer for the whole thing later.

This is not a flaw so much as a design choice you never got to vote on. A memory that kept every Tuesday in equal detail would be paralyzing to carry around. The trade is that you get to travel light, at the cost of the month itself being replaced, in hindsight, by whichever few hours in it happened to be memorable.

The highlight quietly stands in for the whole thing

The trouble is not that the highlight gets remembered — it is that it gets asked to represent something much larger than itself, without anyone deciding that on purpose. "March was rough" usually means one specific week was rough, and the other three weeks, which were fine, get pulled under the same verdict because there is nothing left in memory to argue on their behalf. "That was a great summer" often rests on one trip, with the ordinary weekends around it folding into the glow without having earned it individually. The label is doing the work of thirty-one days using the evidence of two or three, and it does this quietly enough that you never notice the substitution happened.

It runs the other way too, which is the part worth paying attention to. A single bad stretch inside an otherwise fine month can leave the whole month tagged as bad, the way one splinter changes how you handle an entire plank. You are not misremembering the bad week — that part is accurate. You are misremembering everything next to it, because nothing next to it left a trace strong enough to argue back.

Why the substitution matters

This would be a harmless quirk of memory if nothing rode on it, but plenty does. People decide a relationship is not working based on a compressed sense of "lately," when lately turns out, on paper, to have been one difficult fortnight inside a longer stretch that was actually fine. People decide a job has been bad "for a while" off the back of one brutal sprint that ended months ago and colored everything since without anyone checking whether it was still true. The decision gets made against the highlight reel, because the highlight reel is the only version of the month that is still available by the time the decision needs making.

What a written record gives back

A daily log does not compete with memory for vividness — a line written in passing will never feel as loud as the dinner that went badly. What it does instead is sit next to memory as a second source, one that did not filter anything out on the way in. Reread thirty short lines from March and the highlight is still there, exactly as sharp as you remembered it. What is different is that it is now surrounded by twenty-five other lines describing an unremarkable, perfectly fine month going on around it — work, a walk, a phone call, dinner with someone, nothing dramatic. The highlight turns out to have been real and true and also small, one entry out of thirty, not the month's entire personality.

Nothing about this requires deciding in advance which days will matter. That is exactly the problem a highlight-driven memory has — it only flags a day as worth keeping once it has already turned out to be unusual, by which point every ordinary day around it is already gone. A line written the same evening, before anyone knows whether the day will end up mattering, keeps the ordinary ones too, on the off chance that a month full of them turns out to be the actual story.

TimeMap works this way: a line, a time, a category colour, written whenever something happens, with nothing sorted into "worth remembering" or not at the moment it is written. Flip back through a month later and you get the whole shape of it back — the highlight and the twenty-five days it was quietly standing in for — instead of just the one afternoon memory kept on its own.

The dinner that went badly did happen, and it is allowed to be part of March. It is just not obligated to be all of it.