--- title: "Invisible Work Queues (kunnas.com)" author: Elias Kunnas description: "Synthetic discussions generated from public artifacts. No users, scores, or comments are real." canonical: https://kunnas.com/mn/invisible-work-queues url: https://kunnas.com/mn/invisible-work-queues.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: --- desk_pile3 comments The load-bearing slide is from "nobody can query the open set" to "the deadline does not exist in the work." If the clerks who have the emails can say how old their own requests are, the deadline already has somewhere to sit. What is missing is a manager's count. That is a different claim. add_the_clocks2 comments Those are two questions glued together. Can the person holding the request see the clock? Can anyone add the clocks up? The four properties in the repair are all about the second. A clerk who knows an item is late and still does not answer is a capacity or priority problem. A shared list would not have made the deadline more real on that desk. It would have made the miss countable from above. infer_from_delaycollapsed Then the Helsinki case has to pick one. Hypothetical: three clerks, twelve late requests, each can name their own, no shared list. If they already work the oldest first, the deadline moved without a queue object. If they do not, because no one is scored on the oldest, the missing piece is the incentive the later section wants — someone who gains by cutting the open count — not the ability to enumerate. The page infers invisibility from delay plus email. Delay plus email is also what capacity looks like.