11 — Human Work and User Reality

A legal file is not handled by an abstract machine. It is handled by a human being.

That sounds obvious, but serious systems often forget it. They are designed as if the user were a perfectly stable reader with infinite patience, clean uninterrupted concentration, excellent memory, and no cognitive wear from repetition, interruption, stress, or uncertainty. Real users are nothing like that. They get tired. They get distracted. They get interrupted. They lose the thread. They return after time away. They carry multiple files at once. They make provisional judgments under imperfect conditions. They are affected by pressure, by fatigue, by volume, by confusion, and by the simple fact that attention is finite.

That reality is not a side issue. It is one of the core reasons SUMMA exists.

A weak system quietly assumes the user will compensate for structural weakness through private effort. The user will remember what mattered. The user will remember what changed. The user will remember which summary was current. The user will remember the contradiction they noticed three days ago, the witness pressure that felt important last week, and the reason one exhibit mattered more than another. In small files, people can sometimes get away with that. In serious files, they usually cannot. The burden becomes too heavy, and the hidden cost starts rising long before anyone says so aloud.

This is why good structure should be understood as mercy, not decoration.

When a file is shaped well, the user does not have to rebuild the same context from scratch every time. When anchors are strong, the user does not have to rely entirely on memory to find the exact place that mattered. When issue bundles are clear, the user does not have to rediscover the same problem repeatedly across scattered material. When handoff is strong, the next person does not have to inherit chaos as if chaos were normal. Structure reduces unnecessary suffering. It does not eliminate hard work, but it stops multiplying the hard work for no good reason.

That matters because real legal work is cognitively expensive even before the file becomes badly shaped.

A serious reviewer is already carrying a great deal: factual uncertainty, legal consequence, procedural timing, witness instability, document comparison, strategic pressure, and the emotional burden of working with difficult material. Add poor structure to that, and the user starts paying a tax on every action. Every return takes longer. Every comparison costs more. Every interruption becomes riskier. Every handoff becomes weaker. The system may still “function” in the shallow sense, but the human cost becomes quietly punishing.

This is one of the reasons interruption matters so much.

Very little serious review happens in a perfectly protected window of uninterrupted time. People are pulled into calls, hearings, emails, side issues, other matters, urgent requests, and ordinary life interruptions. The result is that file work is often fragmented. A reviewer may enter a dense issue, get halfway through it, then get pulled away before the issue has been stabilized. Later they return and try to restart from memory. If the structure around them is weak, the restart cost is high. If the structure is strong, the file itself helps them recover context. That is a major difference in lived experience.

The same is true of fatigue.

Fatigue does not only mean being sleepy. It means diminishing clarity, diminishing patience, weaker discrimination, and reduced willingness to keep sorting carefully through ambiguous material. A tired reviewer is more likely to accept shallow coherence, overlook a gap, treat a summary as safer than it is, or avoid reopening a problem that feels expensive. That is not because the reviewer is careless in character. It is because human judgment under fatigue changes. A serious system has to be built with that fact in mind.

This is also where attention diversity matters.

Different users do not work the same way. Some are naturally systematic. Some are intuitive first and structured later. Some can hold large mental maps. Some need more external scaffolding. Some can tolerate clutter better than others. Some are especially vulnerable to context loss or cognitive overwhelm when too many loose ends are left open at once. A serious product should not be built only for the most naturally orderly user. It should help ordinary intelligent users work better than they otherwise could, especially under real pressure.

That principle matters deeply in the SUMMA worldview.

The goal is not to flatter the user with artificial simplicity. The goal is to build a structure strong enough that the user can do serious work without being crushed by avoidable disorder. In that sense, the product is not only about files. It is about cognitive load. It is about preserving attention where attention should be spent on legal thought rather than on reconstructing file shape over and over again.

Handoff pain is another major part of user reality.

A great many systems are built as if the same person will always remain inside the file and will always remember enough to continue. Real work does not behave that way. Files move between people. Senior lawyers depend on junior review. Junior lawyers depend on previous summaries. Teams divide tasks. People go on leave. Priorities change. Someone else inherits the file. If understanding has not been externalized into a usable structure, the next person starts in a fog. They are not inheriting a case. They are inheriting the consequences of someone else’s private memory failing to become transferable.

That is why SUMMA puts so much emphasis on continuity, session summaries, issue state, anchor materials, and structured exports. These are not “nice extras.” They are human survival devices inside a complex review environment.

Another part of user reality is emotional drag.

Not every file is emotionally neutral. Some materials are disturbing. Some are repetitive in a deadening way. Some are technically dense. Some are morally ugly. Some combine boredom with consequence, which is one of the hardest combinations for a human being to handle well. A serious system should not pretend that users are unaffected by what they work on. It should aim to reduce the unnecessary friction surrounding that work so that the user’s energy is spent on the real problem rather than wasted on pointless structural pain.

This is one of the reasons clarity matters so much.

Clear naming, clean anchors, current summaries, visible issue state, strong re-entry paths, and honest preservation of uncertainty all reduce the number of invisible decisions the user has to make just to stay oriented. That is not a minor benefit. Invisible decision load is one of the main reasons intelligent people become overwhelmed in weak systems. Every hidden ambiguity costs something. A good system removes as many of those costs as it can.

At its best, then, SUMMA should feel less like “more software” and more like cognitive reinforcement.

It should not infantilize the user. It should not overpromise perfect control. It should not claim to eliminate difficulty. What it should do is give the user a stronger working environment: one that remembers more reliably, organizes more honestly, preserves source better, and reduces avoidable rework. In practical terms, that means helping the user spend more of their mind on judgment and less of it on reconstruction.

That is one of the deepest forms of value in the entire product.

The reader should leave this chapter with one central understanding: the real difficulty in serious file work is not only the record itself, but the strain it places on human attention, memory, continuity, and judgment. SUMMA matters because it is designed not only for the file, but for the human being trying to survive the file.