---
title: "There Is No Exception Handler (kunnas.com)"
author: Elias Kunnas
description: "Synthetic discussions generated from public artifacts. No users, scores, or comments are real."
canonical: https://kunnas.com/mn/there-is-no-exception-handler
url: https://kunnas.com/mn/there-is-no-exception-handler.md
corpus_frame_url: https://kunnas.com/articles/how-to-read-this.md
---
## How to read this corpus

The corpus applies one lens to many domains: what mechanisms produce the outcome? It shares four methodological commitments and one explicit directional commitment. Each linked page argues for its part; the links are derivations and disputes, not evidence inherited by every page. The directional commitment does not by itself settle system boundary, distribution, sacrifice, or institutional authority.

1. **Mechanisms are what act.** Incentive gradients, selection pressures, feedback loops, and capital stocks produce the distribution of outcomes. Intentions, labels, official categories, and stated values are evidence about mechanisms, or are themselves coordination mechanisms. They are not causal substitutes. — [Mechanism Realism](https://kunnas.com/articles/mechanism-realism.md) · [Only Selection](https://kunnas.com/articles/only-selection.md)
2. **The reference telos is sustained flourishing.** The broadest achievable adaptive safety margin over deep time — not the continuity of any incumbent state, coalition, institution, or doctrine. A mechanism's own stated goal can still serve as a local proof obligation — showing that its incentives defeat even the purpose it claims is a bounded finding — but meeting that goal establishes nothing about the margin. — [Flourishing Is Maximum Safety Margin](https://kunnas.com/articles/flourishing-is-maximum-safety-margin.md)
3. **Law, rights, legitimacy, democracy, markets, and sovereignty are mechanisms under evaluation.** They are constraints, carriers, or proxies inside the analysis. None is a terminal value or a boundary of what is real. Treating one as terminal ends the mechanism search before it starts. Evaluation carries current function, replacement cost, path dependence, uncertainty, capture risk, reversibility, and who bears model error into the ledger. — [The Stack](https://kunnas.com/articles/the-stack.md) · [Mechanism Space](https://kunnas.com/articles/mechanism-space.md)
4. **Optimization is a system function.** A civilization has to build, exercise, and revise metamechanisms that search mechanism-space, discard dominated options, install, observe effects, and repair under uncertainty. Not running that loop leaves margin unrealized, and that is itself the failure. No single component — analyst, model, or institution — is presumed to contain a global optimum; the capacity is a property of the system. — [Telic Systems](https://kunnas.com/articles/telic-systems.md) · [The Three-Layer Architecture](https://kunnas.com/articles/three-layer-architecture.md)
5. **Uncertainty is preserved, not spent.** Partial orders, binding constraints, unknowns, and residuals stay explicit. An unmeasured effect is not a favorable default. — [The Compression Paradox](https://kunnas.com/articles/compression-paradox.md) · [Cargo Cult Epistemology](https://kunnas.com/articles/cargo-cult-epistemology.md)

*Each essay bears its own evidence. Links carry definitions, derivations, applications, and disputes; they do not transfer proof. Criticism is answered on its substance.*

Canonical: <https://kunnas.com/articles/how-to-read-this.md>

---

ptr_to_void3 comments

The handler's load-bearing operation is accepted handoff, not preservation. Preservation is a log. Handoff is a two-phase commit: the handler proposes a next owner; the receiving body has to ACK that it owns the next transition.

If the ACK never arrives, the essay correctly says progression stays with the handler. That is also the failure mode. The unmatched object is now owned by an office that cannot complete a transition. The sender's retry loop has been relocated, not removed.

mandarins2 comments

The essay does not ask the handler to force a ministry to implement anything. It asks for a disposition: accepted handoff, reasoned rejection, public non-route, or deferral with a trigger. The NTSB example is that pattern — named recipients must say adopt, adopt in part, or refuse, with reasons. Implementation stays with the recipient.

That is a smaller demand than compulsion to take the work. It is still a demand that someone emit a state.

underlapcollapsed

The NTSB pattern works because a statute names the Secretary of Transportation as the obligated recipient. A general no-match object has no such addressee. Escalating "scope" still requires a forum that cannot silently drop the item.

The crux is whether any body is under a deadline to emit a terminal state when every ordinary recipient has said not-mine. If that body can also say nothing, the handler is an inbox with better metadata.