When an Old List Kept Pretending Work Was Live

For weeks, work that was already over had been sitting in the active pile. On May 4, I read the number at the top of the list: seventeen active tasks.

At first, that number did not look strange. Seventeen is a believable number when there is plenty happening. But when I opened the list, the pieces did not add up. Four entries were empty shells for bigger pieces of work. Three were old work sessions that had been closed in practice but never cleaned up on the list. Two more were extra sessions that had never been tied back to the work they belonged to.

Nine of the seventeen were not active in any useful sense. They were like nine coats still hanging by the front door after the people wearing them had gone home.

The first response had been to keep adjusting the screen that rebuilt the list. Each odd folder or loose record got its own special instruction. That did not work. It was like taping labels onto a kitchen drawer every time you could not find the scissors, instead of deciding where the scissors belong. An organizing helper still failed about half the time because it expected the same drawers in every room and kept finding a different layout.

The cost was time and patience. The cleanup itself took about three hours. More important, the number at the top of the list could not be trusted until someone opened it and checked every item by hand.

The one scary name here is a session manifest. It is just a small note that says which piece of work a work session belongs to. In this case, those notes had been allowed to point wherever they liked, including at a whole bundle of work instead of one actual job. That made finished activity look alive.

There was another problem hiding in a folder called Unknown. It had become the place where work went when no one knew exactly where to put it. That sounds harmless. Every home has a drawer like that. But this one held 47 files, each representing a real larger piece of work that was either underway or already finished.

A drawer for temporary uncertainty is fine. A drawer that becomes a permanent home is not. Once something lands there, it is easy for everyone, including a computer, to stop seeing it clearly. The folder name itself says, in effect, “Come back later.” Later had turned into never.

The repair was not a grand new system. The folders were reshaped into five matching main areas. Each one now had the same four places: the current list, the larger pieces of work, the reference notes, and the archive. A single short readme described what belonged in each area. That gave every helper the same map instead of asking it to guess from folder names that had slowly drifted apart.

Then a small set of directions, about fifty lines long, went through the 47 files in Unknown. It read the label on each one and moved it to the proper home, making that home if it did not yet exist. When it was done, the Unknown folder was empty.

That was the turning point. The active count was not fixed by making the list more clever. It was fixed by putting the underlying papers in the right drawers.

The work-session rules also changed. A session could only point to one real task, not to a larger bundle that contained several tasks. And a simple daily check began moving quiet sessions out of the active pile after 24 hours, then closing them after 72 hours. The list fell from seventeen active tasks to eight, and all eight were actually in progress.

I like that the useful result was so ordinary. No one needed a smarter tool. No one needed a fancier request written for the computer. The records simply had to agree about what the word “active” meant.

This matters outside technical work because almost every household, classroom, shop, and office has a version of that active pile. It may be a family calendar full of events that already happened, a shelf of orders marked waiting when they were delivered, or a notebook of jobs nobody has crossed off because it is not clear who should do it.

When those lists disagree, the answer is often not another reminder or a louder alarm. The answer is to find the one place where the truth should live, then make the other lists follow it.

The count went from seventeen to eight, and the number nine explains the gap: four empty shells, three closed sessions, and two orphaned extras, all counted as active until the manifests were forced to name one real task apiece. The 47 files that had piled up in Unknown now sit in five matching areas instead of one catch-all drawer, and the daily check that drops a quiet session out of the active pile at 24 hours and closes it at 72 is the only thing standing between that number and the next false seventeen.

dxdev LESSON · paste into your AI coding agent
LESSON: A count of active work is only as honest as the records under it, so fix the filing rules instead of teaching the list new exceptions
SOURCE: dxdev.com/blog/2026-05-04_old-list-kept-pretending-work-was-live
WHAT HAPPENED: A work list showed seventeen active tasks. Four were empty shells for bigger pieces of work, three were old sessions closed in practice but never cleaned up, and two were extra sessions never tied to the work they belonged to, so nine of the seventeen were not active. A folder called Unknown had become a permanent home for 47 files, each a real larger piece of work. The first response, adding special instructions for each odd folder to the screen that rebuilt the list, did not work, and an organizing helper still failed about half the time because folder layouts differed. The repair was five matching main areas with the same four places and a short readme, about fifty lines of directions that moved the 47 files and emptied Unknown, a rule that a session points to one real task, and a daily check that moves quiet sessions out of active after 24 hours and closes them after 72. The list fell to eight, all actually in progress.
THE RULE: A number that summarizes state must be computed from records that follow one filing structure and one definition of active, and a catch-all folder must be emptied on a schedule and not left as a permanent home.
CHECK MY CODE, then report PASS or FAIL with file:line for each:
  1. Any catch-all folder or status (Unknown, Misc, Other) holding records with no owner and no expiry.
  2. Any record that can point at a bundle of work when it should point at exactly one task.
  3. Any dashboard or count of active items with no automatic aging rule that moves quiet items out of the active state.
THEN PRINT: a table (check, PASS/FAIL, evidence, fix) + a verdict (applies / partially / OUT_OF_SCOPE / no) + the single most important next action.