The Four-Word Answer That Ends Every Household Disagreement
"I did it yesterday." That sentence, and the argument that follows it, is the reason this template exists. Household task disputes are not fundamentally about effort or fairness—they're about the absence of a factual record. Memory is selective. Memory is self-serving. Memory degrades unevenly across people living in the same space. A timestamp in a database is none of those things.
The Chores template in Memento Database documents what was done, when, and to what degree—with a five-option completion status that goes beyond done/not done to capture the nuance of shared household reality.
The Five-Option Status System and Why "Partially" Matters
Every task in this template offers five response options: "Did it!", "Did it partially.", "Didn't do 'cause didn't need it.", "Didn't do at all & it needed it.", and a separator line. Four of those five are real states that map to real situations.
The kitchen dishwasher can be loaded but not run. The stovetop can be wiped around the burners but not under them. The dining room can be cleared of dishes but not straightened. "Did it partially" is the honest answer in all of those cases, and having it as an explicit option prevents the false binary that turns "I mostly did the kitchen" into either "I did the kitchen" or silence.
"Didn't do 'cause didn't need it" is the option that prevents manufactured compliance—logging a task as complete because the log needs to show it, when the task genuinely didn't require doing that day. This matters for tasks like running the dishwasher, which is irrelevant when the dishwasher is already running, and for tasks like wiping the stovetop, which is unnecessary if nobody cooked that day.
"Didn't do at all & it needed it" is the accountability entry. It is the honest log entry for the person who looked at the full sink and kept walking.
What the Kitchen Section Actually Covers
The kitchen section of this template is the most granular section for a reason: the kitchen generates the most task-related household friction, and it contains the most tasks that are frequently misclaimed or left half-complete.
Counters have both Organize and Wipe as separate tasks, because organizing the counter—moving things back to their designated spots—and wiping the counter are not the same action and do not always happen together. The dishwasher has three separate tasks: Run, Empty, and Load. All three must happen for the cycle to complete. Logging "Kitchen: Dishwasher: Run" as "Did it!" while "Kitchen: Dishwasher: Empty" sits at "Didn't do at all & it needed it" for three days captures the actual failure mode accurately.
Dirty pots and pans, hand-washing, sink loading, stovetop wiping, garbage and recycling, and paper and plastic are all separate entries. None of them is assumed to be included in any other.
The Snake Room and the Honesty of Specificity
The inclusion of "Pick-up: Snake Room" as a named room category—with both General and Make Bed entries—is the kind of domain specificity that makes this template feel real rather than generic. Someone in this household has a snake. The snake has a room. That room requires general pickup and bed-making on the same schedule as every other room. The template reflects the actual household rather than a hypothetical one.
The Bicycling field—tracking twice-weekly minimum exercise as a household accountability item—applies the same documented-commitment logic to a personal health behavior that has been agreed upon as a shared household norm. Logging it alongside kitchen and laundry tasks treats it with the same seriousness, because the person who agreed to do it twice per week apparently needs the same level of documented accountability as the dishwasher.
The datetime stamp on every record anchors the completion log to a verifiable moment in time. Three weeks of records sorted by date show not just what was done but when, and at what frequency. That's the end of the "I do it all the time" argument.