Why do you remember whole weeks as either good or bad?
Someone asks how last week was, and the answer arrives before you have actually thought back through seven days — "rough week," or "pretty good, actually," said with the same confidence you would use for a single fact. A week is not a single fact. It had a Monday and a Friday, a morning that went badly and an evening that did not, days that looked nothing alike sitting right next to each other. Somehow all of that gets filed under one word. The interesting question is not whether the word is accurate. It is why a week ever gets reduced to one word in the first place.
A verdict is cheap to keep. Seven days are not.
Holding seven distinct days in mind, each with its own texture, is expensive — you would need to keep last Tuesday's ordinary tiredness separate from Thursday's actual bad news, and neither would be allowed to bleed into how you remember Wednesday. A single label costs almost nothing to store and takes no effort at all to retrieve. "Bad week" is one bit of information. Seven honest days are seven times that, minimum, and memory is not built to spend that kind of budget on a week that is already over and cannot be changed. So it does not. It compresses, the way anything under storage pressure compresses, and what survives the compression is a summary standing in for the thing itself.
The verdict usually forms before the week is even finished
It rarely waits for Sunday. One bad Tuesday, one hard conversation, one deadline that went sideways — and by Wednesday the week has already been quietly labeled, sometimes out loud, to a friend or a partner: "this week has been awful." Everything that happens afterward gets read through that label rather than judged on its own. A genuinely fine Thursday does not get to overturn a verdict that was reached two days earlier. It just gets absorbed into "awful week" without much resistance, because reopening a verdict once it exists takes more effort than letting the next few days quietly agree with it.
What the label eats on its way to becoming the memory
This is the part that costs something. A week remembered as bad was, almost always, not uniformly bad — it had ordinary stretches and probably at least one actually good hour buried somewhere in it, an hour that would be worth having back if you could find it. But once the verdict has formed, that hour has nowhere to go. It does not fit the label, so it is not the kind of thing that gets retold, and a memory that is never retold is a memory that stops being reachable. A month later, ask what last week's low point was and you will probably remember it in detail. Ask what the one unexpectedly good hour was and most people cannot answer at all — not because it did not happen, but because the label that formed by Wednesday never made room for it.
Good weeks lose detail the same way, just in the other direction
The same compression runs the other way and is just as lossy. A week remembered as "great" tends to keep exactly the highlight reel and quietly drop the two mediocre afternoons and the one argument that happened somewhere in the middle — not because they were minor, necessarily, but because they do not fit a week that has already been labeled great. Either direction, the verdict is doing the same thing: picking a side early and then editing the rest of the week to agree with it.
A line written on Tuesday does not know how the week will be remembered yet
The reason a log resists this is not that it is more honest in some abstract sense. It is a matter of timing. A line written on Tuesday evening is written before Wednesday's verdict exists to distort it. It is not being filed under "good week" or "bad week" because no such folder has been created yet — it is just a sentence about Tuesday, standing on its own. By the time the week's overall shape does get decided, usually days later and often by whichever moment happened to be loudest, the earlier lines are already written and are no longer subject to revision. Going back to read them later, you are not reading your opinion of the week. You are reading the week, entry by entry, before it had an opinion about itself.
What that actually looks like when you reread it
Open the log for a week you remember as bad and it is common to find a Wednesday that reads completely fine — a walk, a decent meal, a text exchange that made you laugh, nothing dramatic either way. That line was never trying to argue with the verdict. It was written before the verdict was there to argue with, and it just sat quietly in the record until you came back and noticed it did not match what you thought the week had been. That gap — between the week you remember and the week you actually wrote down — is usually where the more useful information is.
TimeMap keeps that gap intact by never asking for the verdict in the first place. There is no rating for the day and nothing to score at the end of it — you write a short line about whatever you were doing, whenever you happen to write it, and it stands on its own rather than being pulled toward whatever the week eventually gets called. Later you can open that stretch of days and read them in order, or set one week next to another, and see what was actually there rather than what got remembered.
The label a week ends up with is real, in the sense that it is genuinely what you will recall a year from now if nothing else survives. It is just not the whole week, and it was never trying to be. It was the fastest available summary, written by a mind trying to save effort, and it always leaves something out. A record written before the summary exists is the only way to get some of that back.