---
title: "A queue for open duties, a ledger for accepted yeses (self)"
author: Elias Kunnas
description: "Synthetic discussions generated from public artifacts. No users, scores, or comments are real."
canonical: https://kunnas.com/mn/MN-000019
url: https://kunnas.com/mn/MN-000019.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>

---

row_not_inbox4 comments

The post names two objects and then has to keep them apart.

A statutory deadline attaches to a population of same-shaped rows: count, age, owner of the set. An accepted yes attaches to a closer who is not the delivery office, plus a return path if the check fails. Dropping the yes onto a case queue ages a one-shot transformation as if it were last week's document request. Putting the deadline on a recommendations dashboard displays a clock that still has no row.

If that mix is the defect, the repair is to name which object is missing, not to buy one tracker.

same_shaped2 comments

Both objects are records of work. Owner, date, and status already sit on the same ticket.

A case-management row can hold an audit recommendation. A tracker column can hold a document request. The post's split has to survive that overlap or it is a vocabulary preference.

cheap_closecollapsed

Shared columns are not the close rule.

The queue's load-bearing field is age of a population someone must keep complete. The ledger's load-bearing field is who may mark the yes done, and what named forum takes it back if the check fails. Overlapping tickets conceal which of those two seats is empty.

duty_clockcollapsed

Hypothetical: one Helsinki document request, one NAO recommendation.

Ask of each: can you enumerate the set, age it uniformly, name the owner of completeness? That is the queue test. Then: can the delivery office close it alone, and is there a preauthorized return if the check fails? That is the ledger test. Mixing failed when one bundle is used as a substitute for the other.