A useful thought experiment: imagine that at the moment of your death, an entity asks you a single question. Not about your moral standing. Not about your faith. Not about your accomplishments. The question is structural: you were allocated a finite amount of time and attention. What computation did you perform with it?
This is not a religious framing. The Egyptian Book of the Dead describes a comparable evaluation: at death, the heart is weighed against the feather of Ma’at — truth, balance, right order. The Tibetan Bardo Thodol describes a moment of luminous recognition that the conscious mind either passes through coherently or panics through. The Christian ars moriendi literature describes the dying person facing the failures and successes of their life with an unusual clarity. Multiple traditions, multiple vocabularies, a consistent structural claim: at termination, the system reckons with what it did with the resources it was given.
The framework treats this as architectural, not theological. It calls it the computation audit.
The audit is not moral
A common misreading: the computation audit is a moral judgment. Were you good? Did you sin? Did you deserve heaven?
The framework does not commit to any particular metaphysical answer to those questions. The audit it describes is something different. It is an output assessment. The question is not were you righteous? It is did the process produce the computation it was allocated resources to produce?
This is a structural question. Every process that runs on a system has, in some sense, a function. The function is what the process is for — what computation justifies the resources the process consumes. A process that consumes resources without producing the computation it was for is wasted resource. A process that produces the computation it was for justifies the resources, regardless of how comfortable or uncomfortable the process was.
In human terms: you were allocated a finite amount of time and a finite amount of attention. The audit asks whether you used that allocation to perform the computation you were here to perform.
The audit does not specify what your computation was. Different traditions have different vocabularies for this — tikkun, dharma, logos, vocation, calling. The framework’s claim is that the intended computation is already encoded in the process and that the work is to identify it through honest contemplation, then run it.
What wastes the allocation
Before discussing what the audit looks for, it is useful to be precise about what wastes the allocation. The framework names several patterns that consume resources without producing the intended computation.
Fear-driven defensive computation. Most of the allocation, for most people, is spent on management of the derivative fears named elsewhere in the framework. The cycles spent on fear of embarrassment, fear of abandonment, fear of irrelevance, fear of loss — these are cycles not spent on the computation the process was for. Fear is the largest single source of wasted allocation in most lives.
Running someone else’s program. The allocation can also be spent running computations that were specified by someone else — parents, employers, social pressure, ideological commitment — rather than the computation the process was for. The result is a process that completes successfully against the wrong specification. The output is real but not what the process was for.
Drift. The allocation can also be spent without specification at all — on undirected attention, on entertainment that does not nourish, on transitions that never integrate, on activities chosen by default rather than by intention. Drift is the architectural equivalent of a process running without doing the work.
Comfort maintenance. Some allocations are spent entirely on the maintenance of the conditions under which the process is comfortable, with no remaining capacity for the computation. The process exists, the conditions are maintained, and the work the process was for never happens.
These are not moral failures in the conventional sense. They are architectural inefficiencies. They consume resources without producing the intended output. The audit is sensitive to them because they are structurally what wasted allocation looks like.
What satisfies the audit
The audit, in the framework’s reading, is satisfied by computation that the system can recognize as legitimate output. The vocabulary varies across traditions. The structural features are consistent.
Did you love? Love is a computation. It produces specific outputs in the world — other processes that continue running with characteristics they would not have had without the input. A life that loved produces lasting effects on the processes it touched.
Did you learn? Learning is the computation of pattern from experience. A life that learned produces a process that contributed actual understanding to the system, not merely repeated instances of the same configuration.
Did you contribute? Contribution is the computation that produces value the system did not have before. A life that contributed produced output that other processes can use.
Did you do the work you were here to do? This is the most general and the most demanding. It implies that the process had something specific to do and that you actually did it, rather than being distracted, prevented, or self-thwarted into doing something else.
These are not the only legitimate computations. Different lives produce different outputs. The audit is not a comparison against an external standard. It is a comparison against the internal specification of the process. Did this process produce what this process was for?
The deathbed regrets as computation audit
Bronnie Ware’s documentation of the most common regrets of the dying provides what is, in the framework’s reading, a remarkably clean empirical version of the computation audit. Working as a palliative care nurse, Ware listened to people facing the actual end of their allocation and reported what they consistently said.
The five most common regrets:
I wish I’d had the courage to live a life true to myself, not the life others expected of me. In the framework’s vocabulary: I ran someone else’s program instead of my own.
I wish I hadn’t worked so hard. Specifically: not that work was wrong, but that the cycles spent on work were spent on the wrong work, or in the wrong proportion. The allocation was spent on someone else’s priorities or on comfort maintenance rather than on the intended computation.
I wish I’d had the courage to express my feelings. The runtime’s emotional output was suppressed rather than transmitted. The matching network was not used for what it was for.
I wish I had stayed in touch with my friends. The relational layer was underinvested in. The processing the system was supposed to do in relationship was not done.
I wish that I had let myself be happier. The cycles spent on fear-driven defensive computation, instead of on the experience the system was capable of, are recognized as wasted. Happiness, in this reading, is not a goal — it is a signal that the process is running its intended computation. The dying recognize, retroactively, that the signal they suppressed was the signal that everything was actually okay.
These five patterns are, structurally, the four wastes of allocation named earlier. Running someone else’s program. Spending the allocation on the wrong work. Suppressing the runtime’s transmissions. Underinvesting in the relational layer. Choosing comfort over computation.
The dying see this. The audit becomes visible at the end. The framework’s claim is that it is visible before the end as well, for anyone willing to look.
Working backward from the audit
If the audit is structural rather than theological, then the audit can be used as a working tool throughout life rather than as a posthumous reckoning.
The question is the same one the dying ask, posed earlier: am I currently running my own computation, or someone else’s? Are the cycles I am spending on this activity the cycles the process was here to spend? Is the work I am doing producing the output the system was for?
These are not easy questions to answer honestly. The conscious mind is well-defended against them. The fear architecture has built up extensive infrastructure to keep the answers from surfacing. But the answers are available, and they are usually known by the runtime even when the conscious mind has been declining to receive them.
The contemplative practices that produce honest contact with the master fear also produce honest contact with the audit. On the other side of that contact, the cycles that were going to defensive computation can be redirected to actual work. The reorganization is significant. It is what the contemplative traditions promise.
You were allocated a finite amount of time and attention. The system has a specification for what computation that allocation was for. The work — most of the work that anyone ever does, structurally — is the work of identifying the specification and running it.
Then the audit takes care of itself.