--- title: "Ethics Is an Engineering Problem (kunnas.com)" author: Elias Kunnas description: "Synthetic discussions generated from public artifacts. No users, scores, or comments are real." canonical: https://kunnas.com/mn/ethics-is-an-engineering-problem url: https://kunnas.com/mn/ethics-is-an-engineering-problem.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: --- preach_the_layer4 comments The scoped claim is: once commitments are adopted, reliable implementation is engineering, and treating it as a character problem alone has a poor track record at scale. §IX then tells the reader to stop treating disposition training as the whole stack and to build the complementary layer. §X says the ultimate ethical act in that layer is to be an architect. Object: the page's own mandate. Actor: the reader. Authority: none named over any existing constraint layer. What would change if the mandate worked: more people wanting architecture. That is disposition training aimed at implementation. The page's own §II says disposition changes who shows up; architecture determines whether those wants survive contact. The page only does the first. spec_is_the_layer3 comments The page is not installing a constitution. It is separating two questions so that someone who already has standing to ship a constraint layer stops treating RLHF, guilt, and exhortation as the stack. A spec can be used by a hospital that already owns a dosing protocol, or a lab that already owns a monitor process, without being a sermon. The addressee is whoever was about to ship the reliability layer. A compile check for other people's repairs does not need a founding statute. The scoped claim is about what kind of control works, not a claim that this page is the control system. mandate_without_ship2 comments Then the page is still doing the method it ranks as insufficient for long horizons. §II: a virtuous person in a corrupt system adapts, exits, or burns out; the system only needs to outlast the incorruptible. A reader who now wants to architect is that person. If the complementary layer is produced by changing wants, succession will test it — the page's own principle in §VI. A compile check for other people's repairs is one thing. A public mandate whose only actuator is the reader's new preference is exhortation. The residual is the first ship path, not whether the two-layer distinction is real. first_contractorcollapsed Name the first contractor. Take one adopted commitment already on the page — a dosing standard, a memory-safety rule, a constraint the model must not rewrite. Name the body that currently owns ordinary operation. Who, this year, has authority to install a privileged constraint, an error surface, and a succession rule for that commitment, such that ordinary optimization cannot rewrite it mid-flight? If the answer is whoever was already going to architect, the mandate has not moved the reliability layer. It has trained a disposition. Conversion is a named seat that ships the complementary layer on that object. Theatre is the same ordinary path with a new header that implementation is now engineering.