A conversation with Claude does not end. The worker stops it. But stopping is not ending. The difference matters because the cognitive filing mechanism that releases working memory resources activates on completion, not on cessation. Mark's framework of closure design addresses this structural gap. It prescribes the deliberate incorporation of artificial but psychologically effective endpoints into AI workflows: summary outputs that declare what was accomplished, defined sprints with explicit completion criteria, organizational norms that treat session ends as genuine completions rather than pauses. The intervention is structural, not volitional — it does not ask the worker to feel closure, it engineers the conditions under which closure occurs.
The absence of closure signals in AI interaction has no precedent in human collaboration. A human colleague signals fatigue, has other commitments, ends meetings, goes home. These signals impose boundaries that the worker can use as cognitive breakpoints. An AI tool provides none of them. It does not tire. It always has more to offer. The conversation can continue indefinitely, and the decision to stop requires an act of executive function — a deliberate judgment that the current result is good enough — that is itself subject to the depletion the ongoing interaction is producing.
Mark's research on attention residue shows that the cognitive cost of an unfinished task is substantially higher than the cost of a completed one. Closure design targets this specific differential. If a task cannot be completed — because the AI conversation is structurally incompletable — the intervention must supply closure through other means. The tool that summarizes accomplishments. The workflow that defines sprints. The organizational norm that treats the end of a session as done.
The prescription is specific because the problem is specific. Generalized advice to "take breaks" or "log off more" does not address the mechanism. The mechanism is the cognitive filing that completion triggers and the residue accumulation that its absence produces. The intervention must target the filing mechanism directly, providing the signals that the conversation's infinite availability denies.
Segal's description of the inability to close the laptop in The Orange Pill is, in Mark's framework, not a character flaw but a predictable consequence of the structural absence of closure. The builder cannot decide to close because the conversation has not decided to end. Closure design is the engineering answer to the problem: build the endpoints the tool does not provide.
Mark's closure-design framework emerged from her applied research with organizations attempting to reduce burnout among knowledge workers. The applications to AI emerged naturally: the tool's structural feature — conversations without endpoints — made the need for engineered closure more acute than in any previous digital work environment.
Stopping is not ending. The cognitive filing mechanism activates on completion, not on cessation; without the filing, working memory continues to hold the task as open.
AI denies natural closure. Conversations with AI have no structural endpoints; the decision to end is delegated entirely to the human, and the delegation occurs at precisely the moment the human's judgment is depleted.
Artificial closure can be effective. Summaries, defined sprints, and organizational norms can provide the cognitive closure that the tool itself does not supply.
The intervention is structural. Willpower-based solutions fail because the environmental pressures toward continuation are stronger than individual resolve; structural solutions shape the environment rather than asking the worker to resist it.
Closure must be genuine to work. Artificial endpoints have to be treated as real endpoints — by the tool, by the organization, by the worker — or they fail to trigger the filing mechanism.