Angle

Three volunteers overseeing a building's renovation keep every email, set of minutes and quote, and still spend twenty minutes at every meeting getting level again. A shared case can only be picked back up if its current state is maintained during the work: the chronological order in which emails, minutes and conversations file information keeps everything without situating anything, and the situation of the case then stays in heads that each hold a different version of it. Picking back up is not carrying on; it requires a current state kept apart from the history, one that also takes in verbal information with its status and names only one next action — and it's because this current state lives during the work, not at the moment someone leaves, that picking the work back up stops depending on people.

Synthesis

The starting point is a paradox: nothing is missing from the case and nobody knows how to pick it back up. So the flaw isn't one of archiving but of order; the archive follows the order of production, the work needs the order of decision.

Several consequences follow. Hallway information, which arrives first, has nowhere to go and either gets lost or hardens into fact. Everyone overestimates what the others know. The same sentences come back at the start of meetings — and they're the same ones you retype to an AI, which shows the AI doesn't create the problem: it exposes it.

The answer isn't to archive better or to make to-do lists, but to separate three functions — current state, history, pickup — and to maintain the first during the work. The resulting page is short, read in the order of need, and names only one action; it makes the course visible without freezing it.

What the whole says that no single note says: the ability to pick work back up is a property of the object, not of people. It's built through small deposits as you go, and that is precisely what makes it available at the moment nobody has time to build it.

Tensions / contradictions

Keeping the current state up during the work and writing it at the end of a session from a newcomer's question are two compatible but competing instructions: the first relies on brief, continuous deposits, the second on a deliberate effort at the moment you're least available.

A single next action makes the page readable; it assumes you know what unblocks the rest, which uncertain cases don't always say.

Questions

• In a group without hierarchy, who carries the maintenance of the current state when dropping things in as you go relies on everyone's goodwill?
• How can you know a case can be picked back up before an absence puts it to the test?