--- title: "Every general intake mechanism is a denial-of-service vulnerability (self)" author: Elias Kunnas description: "Synthetic discussions generated from public artifacts. No users, scores, or comments are real." canonical: https://kunnas.com/mn/MN-000007 url: https://kunnas.com/mn/MN-000007.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: --- rate_limit_everything5 comments A duty to issue a reasoned response per packet is not a legitimacy property at civilization scale. It is a work-amplification function. The input is unbounded. Checking a claim against evidence, law, and existing programmes is not. Cheap generation of well-formed packets turns the duty into a queue. The queue is not cleared by evaluation. It is cleared by ritual: standardized reasons, a form rejection, or a backlog that never becomes a case. If the obligation is item-level reasons, the attack is to file. civic_stack4 comments A reasoned response is a disposition, not a treatise. Courts already close most of what they receive with a typed state: no jurisdiction, duplicate, not material. That is a reason. It can be issued at class level. The body treats "reasoned" as if it meant a merits opinion. Existing intakes survive by not meaning that. queueingtheory3 comments Class-level reasons do not make classification free. Under an adversarial generator the scarce step is assigning the class: this packet is out of scope rather than a duplicate rather than a genuine cross-boundary claim. That assignment still costs expert-seconds per item once the packet has cleared form. Standardized reasons are cheap to emit and expensive to choose honestly. The denial-of-service is on the classifier, not on the opinion-writer. old_man_yells_at_queue2 comments Then the implementation that does not lie is an overflow state: unreviewed, not rejected, not reasoned. A corrigible system can reject a challenge. It cannot treat a challenge that never became a case as if it had been disposed of. An honest intake would publish the size and age of the unreviewed set instead of minting fake reasons to keep the duty looking intact. The political problem is that "unreviewed" reads as failure. The technical problem is that fake reasons are how the duty is currently compiled. trialballooncollapsed The test is whether an unreviewed overflow is allowed to exist as a public state. If auditors, courts, or ministers recode overflow as a breach of the response duty, the ritual reasons come back. The denial-of-service is then restored by the accountability layer, not by the inbox. Name a forum that can close a day as "classifier capacity exhausted" without that closure being treated as either a merits rejection or a scandal.