The Stack

The layers where goal-directed systems fail — and a map to the corpus

Elias Kunnas

Any institution, policy, organism, or program can be analysed as a goal-directed system. Such systems fail in a small number of recognisable ways, and the failure modes group cleanly into twelve layers. Each layer asks one question; each question has a healthy answer-shape and a failure-shape. This page is the navigation surface for the rest of the corpus: what each layer is, the canonical failure at that layer, and the essays that cover it. The page is not an argument that the world has exactly twelve layers. It is a navigation surface: when a failure appears, the stack asks which layer is binding and points to the essays that treat that layer. Treat the partition as a working hypothesis — useful enough to organise the work, not the periodic table of social science.


0. Scope and reference telos

The Stack is telos-relative. It does not define failure by itself. A Stack walk must name the system boundary and the reference telos before naming the failed layer. The same event may be success relative to one local system and failure relative to another: a village coalition can succeed at coalition preservation while failing relative to legal-civic legitimacy; a bureaucracy can succeed at defensibility while failing relative to action; a democracy can succeed at voter satisfaction while failing relative to deep-time flourishing. In local use, the reference telos is often the institution's legitimate mandate. In framework use, the reference telos is deep-time flourishing and survival margin. When these diverge, Layer 0 is not background; it is the first object of audit.

The Stack applies where a persistent goal-directed system has channels through which relevant reality must become action, correction, or reproduction. The preconditions are: (1) a declared system boundary, (2) a reference telos, (3) reality entering through identifiable channels, (4) a conversion path from signal to action, (5) persistent carriers — roles, files, queues, ledgers, memory, feedback loops, reproduction pipelines — and (6) localisable failure across distinguishable substrates. Without all six, the Stack is metaphor rather than diagnostic. It applies strongly to institutions and institutionalised systems; it applies to other substrates (AI systems, markets, cultures, minds, organisms) only by translation into substrate-native hardening devices.

Failure relative to telos T therefore means: T-relevant reality entered through a channel the system does not own, so the reality could not become T-preserving adaptation. The "T-relevant" qualifier is not optional; it is the variable that decides which channels count as load-bearing.

Three nested failure types follow from this. Telos-misalignment failure: the system executes well, but its telos itself fails the meta-telos (the village game running correctly while depleting substrates that deep-time flourishing depends on). Execution failure: the system's telos is acceptable, but it fails at one of the eleven lower layers (the welfare agency that cannot process claims because the queue is invisible). Multi-system collision failure: multiple systems each succeed locally but jointly produce higher-order failure because no one owns the translation between them (the court closing the case while the town reopens it). The third category requires a distinct primitive — cross-system standing-and-closure conversion — that the Stack alone does not supply.

Worked example, telos-relative diagnosis. A small town: an authority figure is convicted in court; the community responds by slandering the victim and continuing to grant social standing to the convicted man. The legal system and the town substrate are each running their own stack. The legal system succeeds at universal-rule closure: standing was granted, evidence was processed, the verdict was rendered, the sentence was imposed. The town succeeds at coalition preservation: the in-group authority figure was defended, the outside intrusion was named as such, the defector (the complainant) was sanctioned. Neither system necessarily fails by its own lights. The failure relative to deep-time flourishing is the unowned conversion between them — no role in the town substrate owns importing the verdict, protecting the complainant's continued membership-standing, or sanctioning post-verdict retaliation. The same shape recurs in workplace HR vs staff culture, regulator vs industry, audit vs department culture, international tribunal vs national public, university discipline vs peer group, and whistleblower vindication vs industry blacklisting. The diagnostic move is to walk both stacks and ask which channel of conversion between them is unowned.


I. The twelve layers

# Layer The question it asks Canonical failure
0TelosWhat is the system for?No owner of the purpose; drift; capture by proxy objective
1MechanismHow does it actually produce its outcome?Intent replaces causal model; words assumed to control behaviour
2ResponseWhat does the system make rational, cheap, or unavoidable for the next actor?Pressure routes through the cheapest channel — gaming, exit, substitution
3CarrierWhich harms get a voice in the decision system?One side has a carrier; the other side is silent and absorbs the cost
4MeasurementWhat signal is treated as reality?Proxy becomes target; map detaches from territory; Goodhart dynamics
5LedgerWhich stocks does the policy actually draw down?Hidden depletion masked by visible flow; "hard to measure" booked as zero
6CompilationDoes the public-usable decision frame exist?Pieces exist scattered; the assembled artifact nobody compiles
7Computation / adoptionDoes the system actually compute with the frame?Parameterised reasoning is refused, captured, or masked as values
8DecisionWho must choose, repair, or override — and how is evasion prevented?Diagnosis exists; no one is forced to act on it
9ExecutionDoes the institution have the capacity to implement the repair?Smart fix demands competence the receiver lacks; result worse than the disease
10FeedbackDoes observed failure feed back into mechanism correction?Decorative evaluation; advisory reports that bind nothing
11ReproductionDoes the system reproduce the capacity that made its outputs possible?Output survives; the generator-chain dies

A given problem rarely sits at one layer alone — but the canonical failure mode usually does. The diagnostic move is to ask, layer by layer, where the binding failure is. A policy that has the right mechanism (1) and the right ledger (5) but no decision-side enforcement (8) will fail at the decision layer; a policy whose decision-side is healthy but whose execution layer (9) has been hollowed out will fail at execution. The vocabulary lets the post-mortem be specific.


II. The layers, with corpus pointers

0. Telos — what is the system for?

The question. What is the system actually selecting for, explicitly or implicitly? An institution without an owned, articulated purpose is being optimised by selection pressures it does not see.

Healthy primitive. Explicit telos, explicit tradeoffs, named objective function.

Failure family. No owner of the purpose; drift; capture by proxy objective; comfort-and-preservation as terminal value; multi-objective incoherence.

In this corpus.

1. Mechanism — how does it actually work?

The question. What rule, incentive, constraint, or architecture is supposed to produce the outcome? "We will pass a law about X" is not a mechanism; "the law changes the cost of Y, which causes actor A to substitute toward Z" is.

Healthy primitive. Explicit mechanism claim with named actor, changed constraint, expected response, target output, time horizon.

Failure family. Intent treated as causal force; legal text assumed to compile into operational behaviour; moralisation replaces computation.

In this corpus.

2. Response — what do agents do next?

The question. Once the rule changes, what does the next actor find rational, cheap, safe, or unavoidable? Policy lands inside an existing strategic landscape and triggers a response. The response is a property of the actor and the architecture, not of the legislator's intent.

Healthy primitive. Mapped response channels; predicted dominant response; counterfactual against status quo.

Failure family. Pressure routes through the cheapest channel — compliance gaming, formal substitution, withdrawal, exit, lobbying, reclassification, passive non-uptake.

In this corpus.

3. Carrier — who can carry harm into the decision system?

The question. Which harms become visible because they have someone or something to carry them into the institution that could repair them, and which harms remain invisible because no carrier exists?

Healthy primitive. Standing for the silent class; explicit bearer of diffuse cost; statistical victim given a procedural voice.

Failure family. One side has a carrier (legally, organisationally, narratively); the other is silent. The silent side absorbs the cost. The carrier-equipped side writes the rules.

In this corpus.

4. Measurement — what signal is treated as reality?

The question. What does the system observe, and what does it treat as evidence of success or failure? Measurement is never neutral: once a measure is attached to reward, punishment, or legitimacy, the actors inside the system optimise the measure, not the underlying reality it was meant to track. Measurement failure is upstream of ledger failure; before you can count the wrong stock, you can measure the wrong proxy.

Healthy primitive. Measurements that remain coupled to the underlying reality; proxy treated explicitly as proxy; audit path from metric back to territory; periodic recalibration when the relationship between proxy and reality drifts.

Failure family. Goodharting; proxy-target divergence; cargo-cult epistemology; metric-compliance replacing reality contact; map detaching from territory.

In this corpus.

5. Ledger — what gets counted as cost?

The question. Which capital stocks does this intervention draw down to fund the visible benefit, and are those stocks on a ledger anyone consults? Most of what a civilisation runs on is booked at zero by default; that booking decides what looks like a gain.

Healthy primitive. Full accounting across all load-bearing stocks; stock + flow + recovery-horizon for each.

Failure family. Hidden depletion masked by visible flow; "hard to measure" booked as zero; balance-sheet theft at civilisational scale.

In this corpus.

6. Compilation — does the right decision-frame exist?

The question. Have the relevant academic substrate, statistical evidence, and policy considerations been assembled into a public-usable decision frame that a generalist can actually pick up and use? Three distinct objects often get confused: academic synthesis, institutional compilation outputs, and the publicly-pickable decision-frame artifact. The third one is the one that is frequently missing. Compilation is the supply-side question; whether the frame is actually used once it exists is the Computation/adoption layer below.

Healthy primitive. Parameterised public frame with named variables, causal structure, an update rule, and a policy-evaluation test.

Failure family. The pieces exist; the assembled frame does not.

Repair-side analogue. Compilation has a repair-side analogue. A diagnosis may compile correctly into a public decision frame and still fail to compile into a native institutional artifact. The first question is content compilation: does the frame exist? The second is actuator compilation: does the frame land as the right kind of object — statute, reasons, guidance, record, register, contract clause, budget line, dashboard, audit trigger, parliamentary motion, or public essay — at the right binding strength? A correct frame routed to the wrong surface becomes an over-prescription, a decorative report, or an administrative impossibility. Content compilation supplies the diagnosis. Actuator compilation selects the repair vehicle. See §V Repair routing for the operational protocol.

In this corpus.

7. Computation / adoption — does the system actually use the frame?

The question. Once a decision frame exists, does the system actually compute with it — or does it convert the frame into slogans, factional ammunition, or moral cover? Compilation and computation are separable problems: a perfectly compiled frame can land in a discourse architecture that refuses to compute with it. The two failures call for different repairs.

Healthy primitive. Parameterised reasoning made procedurally consequential; disagreement attached to named variables; values separated from empirical claims; institutional teeth that make ignoring the frame expensive.

Failure family. Computation refused; empirical claim hidden as value disagreement; frame captured by faction; frame sloganised; public debate remains slogan-shaped despite the compiled artifact existing.

In this corpus.

8. Decision — who must choose, repair, or override?

The question. Once the mechanism failure is visible and the frame exists, who is forced to decide, and how is invisible evasion prevented? Diagnosis without a forced decision is decorative.

Healthy primitive. Repair-or-override loop with named owner; political override permitted but visible; no quiet decay.

Failure family. No one is forced to act; the warning is filed; the system continues. Or the decision is delegated until no owner remains.

In this corpus.

9. Execution — does the system actually implement the repair?

The question. Once a decision is made, does the receiving institution have the capacity, authority, and feedback loop to execute the repair without producing worse distortion than the original problem?

Healthy primitive. Implementation ledger with owner, trigger, and a movement test that distinguishes activity from result.

Failure family. Critique absorbed without repair; reform-form without transformation; smart mechanism failing because implementation capacity is missing.

In this corpus.

10. Feedback — does reality update the system?

The question. After the policy is enacted, does observed failure feed back into mechanism correction — or only into narrative? Most evaluation produces reports; very little produces correction.

Healthy primitive. Feedback is not complete when information returns. Feedback is complete only when returned information changes the system’s action set, opens a decision forum, or forces a reasoned refusal to act. Operationally: each observation channel must trace to artifact → owner → deadline → forum → response menu → public output → no-action explanation → named next carrier where action lies outside the instrument. A channel that stops at “monitor and reassess” is an alarm, not a feedback loop.

Failure family. Decorative evaluation; advisory reports that bind nothing; audits that observe but do not alter the mechanism; soft-control verbs (monitor, evaluate, develop, agree, recommend, increase transparency) that name the next institutional event implicitly when no such event is structurally required.

In this corpus.

11. Reproduction — does the generator-chain continue?

The question. Does the system reproduce the capacity that made its outputs possible — the apprenticeship, the lineage, the standards, the tacit knowledge? Output can continue for years after the generator is dead. The persistence is misleading: the corpse is still standing.

Healthy primitive. Live generator-chain; apprenticeship and intergenerational transmission; explicit standards; spore strategies for hostile environments.

Failure family. Output without generator; chain breakage; institutional shell surviving the competence that filled it; AI substituting for the practitioner-chain that would have produced the next generation of practitioners.

In this corpus.


III. Two navigational cuts: layer and gate

The Stack names the where of failure: telos, mechanism, response, carrier, measurement, ledger, compilation, computation, decision, execution, feedback, reproduction. A second cut names the where in passage: the route by which institutional intelligence becomes binding action. The two cuts form a coordinate system. The layer asks which substrate is broken. The gate asks where, in the passage from "someone knows" to "the institution acts," the object stopped moving.

This second cut covers one geometry, not the whole corpus. The corpus also contains parallel-bonded faults, selector matrices, allocation channels, substrate stacks, and topology / feedback structures (see end of this section). The chain is the dominant grammar — the recurring sequential conversion that the most load-bearing recent essays instantiate — but it is not the master architecture.

The passage:

GateQuestionPrimary corpus pointer
AgendaIs the relation on the table at all, or excluded before it can be considered?Nondecision / structural inadmissibility; Non-Compilation sits adjacent (compilation-of-public-frame, not strict agenda admission)
CapacityWhat kind of bound is possible at all, even roughly?Boundability precondition; Information Gradient names the substrate; Calculemus §VII names the wrong-thing / no-feedback failures
ProductionWas the relevant bound, model, estimate, or diagnosis actually created?The Refusal to Compute — production variant of the same primitive as admission
AdmissionDid the bound become an admissible object on the decision record?The Refusal to Compute (admission variant) and The Procedural Object (the seven-field admissibility test)
AnchoringDoes the bound or proxy remain coupled to the territory it claims to track?The Measurement Anchor — causal audit path, validity envelope, bounded proxy status, independent verification
BindingDoes the admitted intelligence constrain anyone with authority? Authority is a vector, not a yes/no.Powerless Intelligence (authority × resource × answerability) and Feedback Authority (the ignore-cost vector)
ExecutionDoes acceptance become changed behavior, not only recorded acceptance?Implementation Ledger — acceptance → transition record → re-entry
LearningDoes action update the institution’s map?A cluster: The Severed Map (disciplinary topology), Cargo Cult Epistemology (ritualized verification), the Hypercodex provenance argument. Single-essay coverage is partial.

The diagnostic rule: identify the earliest dependency gate whose failure blocks passage of the relevant object. Downstream repair cannot substitute for the missing upstream dependency. More dashboards do not fix non-admission. More consultation does not fix powerless intelligence. More reports do not fix a missing execution ledger. If the upstream gate cannot be repaired directly, downstream work can still be preparatory, compensatory, or pressure-building — but it should be named as such, not treated as a cure.

The layer and the gate together locate a failure more precisely than either alone. “Layer 7 computation failure” says the institution refuses to compute with a frame that could bind it. “Production gate” says the bound was never created; “admission gate” says it existed but never became a procedural object. “Layer 4 measurement failure” says the system’s signal has detached from reality. “Anchoring gate” says that detachment blocks later binding, execution, and learning. The layer locates the substrate. The gate locates the stopped passage.

Binding has strength, not only status. The Binding gate is binary in name (owned vs unowned) but graded in practice. An admitted object can constrain an institution weakly, moderately, or heavily. Each substrate has a ladder of instruments. In law: reasons < guidance < agency duty < statutory public duty < parliamentary reporting < constitutional duty. In software: warning < log < alert < failed test < deployment block < rollback trigger. In organisations: note < memo < policy < budget condition < audit finding < dismissal trigger. Moving upward increases ignore-cost but also administrative friction, jurisdictional exposure, and maintenance burden. A repair can therefore fail in two opposite ways: under-binding, where the object creates no real response duty, and over-binding, where the object is routed through a heavier instrument than the institution, genre, or problem can carry. The Stack diagnosis names the missing conversion; the repair must still choose the lightest instrument that actually converts. The two specialisations of binding strength — Powerless Intelligence and Feedback Authority — treat the receiver-side and consequence-side of the same gradient.

Where the chain is the wrong diagnosis

The chain applies to sequential intelligence-translation. Several recurring corpus structures are not sequential, and the first-failed-gate rule misleads when applied to them:

The chain’s debugging register transfers well to sequential administrative passage. It transfers badly to live political contestation, recursive causality, simultaneous failure, and legitimacy contestation. Bad Equilibria Are Not One Thing explicitly says its five gates “are diagnostic axes, not mutually exclusive boxes and not a causal sequence.” Forcing those essays into the chain distorts their analysis.

This subsection is a map legend, not a master theory. The Stack gives the layer coordinate. The passage gates give a second coordinate for the intelligence-to-action corridor. Other geometries point to other coordinate systems. Reading a corpus essay correctly starts by asking which geometry it occupies — sequential, parallel-bonded, selector, allocation, substrate, topology — and then applying the diagnostic move appropriate to that geometry.

Chain plus distortion in practice

Real cases are rarely pure instances of one geometry. A case often has a dominant sequential passage while secondary geometries operate around the failed gate. A chain-only diagnosis can be locally correct and still under-repair the case: it identifies the blocked gate without scanning for what stabilizes the failure, where pressure routes when blocked, which bonded layers restabilize the failure, which reform vectors are attempted, which substrates are missing, or whether the gate is itself a routing topology.

The two-step diagnostic that fits most real cases is: locate the dominant passage failure (the earliest blocking dependency), then scan the failed gate for distortions.

DistortionQuestionCorpus pointer
Bonded edgesWhat co-active faults preserve this gate failure?Bad Equilibria, Theatrical Accountability
Allocation routingWhere does pressure go when this gate blocks?The Response Vector
Selector dynamicsAre repeated reform attempts choosing different vectors?When Does Reform Happen?
Substrate dependenciesWhich substrate must hold for this gate to function?Full-Stack Survival
Topology at the gateIs the gate itself a routing or network problem?Optionality Has No Router, The Procedural Object

A repair plan that fixes the dominant gate without addressing the distortions usually fails: the next case in the same domain reproduces the same failure through the same bonded layers, allocation channels, or substrate gaps. The mechanism test the corpus uses in practice now reads as two paired moves — gate repair plus distortion repair.

Reverse consequence: when the gate works correctly

A separate complement to the chain operates when the gate is not failing at all. Structural Residue covers cases where a gate works under its own rule but leaves a consequence causally live. This is the worked egress case for §IV Motion 3: the gate may be healthy but the consequence-exit channel is unowned, so the consequence routes outward without binding back as accountability. The usual case is refusal: a claim is correctly excluded, and the consequence routes outward through other actors, scales, time horizons, or institutional channels. A second case is acceptance-by-design: a relief valve, exception, appeal, discretion clause, or safety mechanism correctly accepts the hard case but sheds processing load, litigation, delay, or discretion burden downstream. The gate is not broken in either case. The unowned object is the consequence of the gate working. Repair therefore does not mean closing the gate; it means naming the downstream load, owner, capacity, and feedback path. The chain follows admissible signal forward through gates; structural residue follows the live consequence outward through carriers. A case can call for both diagnostics: a chain failure plus distortions plus persistent residue from earlier correctly-functioning gates that have been routing or shedding for years.


IV. The structural law underneath

One sentence keeps surfacing across the twelve layers and is worth naming as the master form:

A system fails, relative to telos T, where T-relevant reality enters through a channel the system does not own.

Ingress without ownership creates blindness. Surface without ownership creates parasitism. Egress without ownership creates externalization.

That first sentence names the original master form; the second states the full triad. The same conversion question recurs in two further forms: surplus must lie on owned surfaces if it is to reach telos rather than feed extractors, and consequence must exit through owned channels if it is to bind the decisions that produced it. All three are ownership of telos-relevant conversion; the Stack’s twelve layers are the substrates on which any of the three motions can fail.

Motion 2 — Surface. Telic systems contain surplus: money, discretion, legitimacy, trust, attention, debt capacity, exception space, optionality. Surplus not owned by a telos-preserving constraint becomes a feeding surface. Actors attach to the surface, build justifications, harden them into offices, budgets, contracts, and metrics, and reproduce past correction. The diagnostic question for surface failure: which T-relevant surplus is unowned, and which carrier prevents capture? Failure of the second motion produces parasitism. Full Accounting, Telocracy, and The Dominant-Player Constraint develop the surplus-side ownership question; the cross-layer overload and capture conditions below are specific failure modes of this motion at aggregate and rule-setting scales. Surface parasitism is the earlier ecological form and capture is what it hardens into: feeding actors reproduce, gain institutional position, acquire capture levers, and then use those levers to keep the surface open.

Motion 3 — Egress. A decision is made, an action taken, a cost incurred. The consequence must return through an owned channel to bind some actor — the decision-maker, an oversight body, a successor administration, a payer of record. If it exits through an unowned channel, it leaves the decision system entirely: future taxpayers, displaced workers, depleted trust, unbuilt alternatives, deteriorated demographic or institutional capital, and knowledge that drains into informal carriers because no formal compiler exists. The diagnostic question for egress failure: which T-relevant consequence is exiting, and what carrier should hold the return path? Failure of the third motion produces drift: the system continues making decisions whose consequences arrive on parties too diffuse, delayed, or fragmented to constitute a decision-grade counterparty. Structural Residue (a gate works correctly but the consequence routes outward), The Asymmetric Carrier Problem (silent payer absorbs cost), The Tyranny of the Present (consequences land on future cohorts), and the cost-displacement family in Full Accounting treat this motion at substrate-specific resolution.

The three motions are not independent. Channel failure produces blindness — the system does not feel that surplus is being eaten. Surface failure produces feeding — actors organize around the unowned surplus. Egress failure produces drift — the costs of the feeding leave the decision system without binding back. Mature institutional failure is the loop: blindness permits feeding; feeding externalizes costs; externalized costs do not return; non-return preserves the blindness. The corpus essays at each layer give the substrate-specific repair vocabulary; the three motions give the geometry that holds them together.

The twelve layers are twelve different ways the system can fail to own a channel through which T-relevant reality enters. Unowned purpose produces telos gaps. Unowned mechanism produces intent-substitution and moralised causal disputes. Unowned actor response produces the four-channel pressure routing. Unowned harm produces silent-side absorption. Unowned measurement produces cargo-cult epistemology and the severed map. Unowned cost produces false-zero accounting. Unowned decision frame produces non-compilation. Unowned computation produces the Calculemus slogan war. Unowned decision produces powerless intelligence. Unowned repair produces institutional containment. Unowned feedback produces theatrical accountability. Unowned generator-chain produces sterile generativity.

The diagnostic question for any failure: which T-relevant channel, surface, or consequence is unowned, and by what authority would it have to be owned? That is the cross-layer question the stack is built to support. The "T-relevant" qualifier is non-optional: change the telos and the verdict on the same events can change.

Premise-correction ownership. A system can own its procedures, metrics, and implementation channels while leaving premise correction unowned. When adverse reality returns, the error routes into auxiliary apparatus, execution failure, an inadmissible reporter, a domain boundary, or world-noise, while the load-bearing premise stays insulated. The diagnostic tell is the absorption question: when reality pushes back, which category receives the error — premise, apparatus, execution, the reporter's standing, the evidence's admissibility channel, or the world? The discriminator is the direction of risk — a healthy system absorbs an anomaly by increasing its future contact-risk (the patch exposes the premise to a new way of being wrong); a premise-insulating system absorbs it by decreasing premise-risk while preserving status. The most self-serving route is rejecting the reporter as unauthorized rather than the evidence as false — a Feedback Authority admissibility failure located at the premise layer rather than the action layer.

Four conditions cut across all twelve layers rather than living at one.

Cross-layer overload. Accumulated binding mass can exceed the system’s action capacity, so each owned channel itself becomes a maintenance burden the institution can no longer carry. Cancer Failures names this cross-layer pathology — the layers are individually owned but their aggregate weight is unowned — and pairs against the conversion-failure family the rest of the stack diagnoses.

Cross-layer under-binding. Each owned channel either generates conversion capacity or fails to. Steering Power (Capacity × Coupling × Salience) names the macro-amplitude form; Powerless Intelligence (Authority × Resource × Answerability) names the receiver-side specialization; Feedback Authority grades the consequence the institution bears once conversion path exists; The Refusal to Compute names the active strategy to suppress conversion by refusing to produce or admit the bound that would activate obligation. The same multiplicative any-zero-kills-product structure recurs at every layer where an owned channel must convert input into binding action. Cross-cutting precondition: this is the inverse failure family to Cancer (under-binding per channel; Cancer is over-binding aggregate).

Cross-layer capture. One actor can choose the rules, evidence, forum, timing, closure condition, and enforcement substrate of a contest that affects others. The Dominant-Player Constraint names governance as the architecture that prevents this concentration of upstream control. Most governance-arc primitives block specific capture levers; the cross-layer condition is that any owned channel can be captured if no primitive blocks the relevant lever, and the matrix of levers-vs-primitives is dense rather than diagonal.

Cross-layer symbolic substitution. A system can populate any layer with an artifact that represents ownership without carrying the causal role that ownership would require. A declared right may lack an enforcement carrier; a transparency mandate may lack a publication surface; a procedure may lack a consequence; a monitoring duty may lack a response path; a constitutional protection may lack a re-entry channel into decision. The artifact appears in the institution’s official compilation, but the institution’s action set is unchanged or changed only at a weaker level than the artifact implies. This is not simply overload, under-binding, or capture — it is a prior type question that can precede or co-occur with all three: a symbolic substitute can mask under-binding, help capture, or accumulate into overload. Symbolic artifacts are not causally inert: they coordinate, legitimate, signal, and create focal points. The failure occurs when those symbolic effects are treated as if they were enforcement, correction, measurement, allocation, or execution — that is, when the artifact carries less or different causal force than the role it is invoked to perform. The connection to Feedback Authority is direct: the substitution pattern is the channel-installation version of selling one binding-force profile (procedural, consequential) while installing a lower one (decorative, advisory). The diagnostic test: what action set changes, who must act differently, what record or trigger is created, what consequence follows if nothing happens? If the answer is only that the institution has named, affirmed, announced, or represented a channel, the channel is symbolic rather than owned. Mechanism Space develops the underlying geometry (semantic space vs mechanism space); Laws Are the Wrong Abstraction §VII gives the rights-specific application (“a right without a mechanism is a wish”); The Halting Problem of Law §II gives the legal-text-as-code application (syntactic vs semantic). The substitution diagnostic is what unifies them across layers. Two sibling child-families specialize the parent diagnostic by what is being substituted. The Causal Talisman (and the broader Talisman cluster) names the substitution of legitimacy-bearing weight for analysis — a morally protected cause-name or category discharges analytical pressure without any formal institutional artifact required. Nominal Execution names the substitution of form/status-bearing availability for execution — a formal artifact (right, statute, certification, procedure, model) is invoked as if it had carried the institutional fact it names. The two surface at different points: weight-substitution can operate without any formal token; form-substitution requires the token and credits its presence.


V. Using the map

The page is built to be a working object, not an essay to be read once. Four intended uses:

Triage. For any concrete failure — a policy that obviously isn't working, an institution that obviously isn't delivering, an organisation's capability that is obviously eroding — walk the twelve layers in order. Where is the binding failure? Multiple layers usually contribute, but one is usually load-bearing for the current state. Naming the layer is the first move; the corpus essays at that layer are the second. In every layer walk, run the symbolic-substitution check before the under-binding diagnosis: distinguish the owned channel from its symbolic substitute, ask what action set changes, who must act differently, what record or trigger is created, what consequence follows if nothing happens. If the answer is only that the institution has named, affirmed, announced, or represented a channel, the repair has not yet reached mechanism level — and a subsequent under-binding diagnosis will mistake an absent channel for a weak one.

The loop named in §IV — blindness permits feeding; feeding externalizes costs; externalized costs do not return; non-return preserves the blindness — is the mature predatory attractor, but it is not the only attractor a real case lands on. Four conversion-failure attractors and one wrong-repair attractor recur, and they take different repair routes. Naming the attractor is the second triage move after naming the layer.

AttractorSignatureRepair route
Closed predatory loopBeneficiaries of the surface preserve blindness and route consequences away from the decision systemRepair all three motions (ingress / surface / egress) plus anti-capture at the carrier layer
Visible-but-powerlessEveryone sees the signal; no actuator must act on itPowerless Intelligence, Feedback Authority
Beneficiary-free externalizationCosts exit through time, jurisdiction, ideology, or accounting convention rather than into organized feedersAsymmetric Carrier Problem, Full Accounting, Structural Residue
Public-but-shameless non-returnHarm is public, knowledge returns, but no one is bound to change behaviourDominant-Player Constraint, Corrective Closure Ownership, consequential Feedback Authority
Wrong repair: Over-ownership / CancerEvery channel binds; aggregate binding mass exceeds action capacity; new ownership requirements add to the load without removing failed onesWhen Ownership Is the Wrong Repair, Cancer Failures, triage, conditional closure, sunset clauses

The wrong-repair row is the discipline against the corpus’s own favourite move: install an owner. Ownership is the repair when ingress, surface, or egress is unowned. It is the wrong repair when the binding mass is already the failure, when the proposed owner is captured by the surface it must judge, when the trigger becomes its own bureaucracy, or when the trace becomes theatre without re-entry. Each repair-route cell above is correct only when the layer diagnosis has cleared the wrong-repair test as well. When Ownership Is the Wrong Repair gives the full family — capture, theatre, dashboarding, exhaustion, cancer — the repair-compilation test, and the case where a weak actuator is the strongest one legitimately available.

Cross-referencing. When two essays in the corpus seem to overlap but are not the same thing, the layer assignment usually clarifies why. Non-Compilation at the Compilation layer (6) and Calculemus at the Computation/adoption layer (7) treat the supply side and demand side of the same problem, but at different layers — Compilation asks whether the frame exists; Computation asks whether the system uses it. Cargo Cult Epistemology at the Measurement layer (4) and Full Accounting at the Ledger layer (5) also treat related but distinct failures: measurement asks what signal counts as evidence; ledger asks what stock counts as cost. The layer assignments make the distinctions visible.

Gap-finding. Where a layer has fewer essays than its weight in the failure stack would predict, the gap is informative. Measurement (4) was freshly separated from Compilation in earlier versions of the stack; the dedicated Layer 4 anchor is The Measurement Anchor, which gathers the Goodhart family explicitly. Computation/adoption (7) has its operational anchor in The Refusal to Compute, which supplies the four-gate test (relation, bound, obligation, unbounded substitute) that distinguishes refusal from honest non-computation and operationalizes Calculemus’s broader argument. Reproduction (11) has strong coverage on chain breakage and weaker coverage on chain formation; a How Generator-Chains Form essay is the non-trivial missing half. The stack is a working map; the gaps are part of what the map is for.

Repair routing. A Stack diagnosis is not yet a repair. After the failed layer and gate are named, the repair must be compiled into a native institutional artifact. Three questions control the compilation. First: what object is needed — telemetry, reason-giving, evaluation, intervention, escalation, capability, or public argument? Second: which authority owns that object — the target instrument, a related carrier, a different institution, or no institution yet? Third: what binding strength is native to that surface — explanation, guidance, agency duty, public statistic, statutory duty, parliamentary trigger, or constitutional rule? The recurring error is to discover the right risk and prescribe the wrong actuator. A Measurement failure does not automatically require a statutory report. A Feedback failure does not automatically require parliamentary review. A Capability failure does not become solvable because a contract asks suppliers for more paperwork. More binding is not always more repair. The repair is correct only when the object, owner, surface, and strength match the failure. Risk discovery is not actuator selection.

Pitfall under repair routing: observability over-binding. The most common wrong repair after a Measurement, Feedback, or Learning diagnosis is to add a dashboard, report, audit, ledger, or statutory review duty at the heaviest available level. The diagnosis may be correct and the repair still wrong. Observability is administratively respectable, so it expands beyond its native attachment point. The test is: what must be observed, by whom, at what granularity, for what decision, and with what consequence? If the answer is operational telemetry, a public statistic or decision field may be enough. If the answer is policy evaluation, reasons or a follow-up section may be the native surface. If the answer is intervention, a report without a decision duty is only theatre. More visibility is not repair unless it lands on the decision that needs the visibility.

The cross-cutting positive synthesis is What Bureaucracy Is: the runtime of traceable discretion, decomposed into five recurring functions (admit, authorize, assign, remember, contest-or-close) that the Stack’s layers and the corridor essays specialize. The Stack reads failure-relative; What Bureaucracy Is reads function-relative.

Two further cross-stack disciplines sit alongside the Stack rather than inside it. Hardening Devices is the substrate-export discipline: the Stack’s failure types are substrate-general, but the carriers that implement repair — records and files in institutions, weights and eval artifacts in AI, identity commitments and habits in minds, rituals and taboos in cultures, contracts and audited accounts in markets — are substrate-specific. A claim that a Stack-layer failure-type generalizes across substrates must pass the substrate-translation discipline before it ships. Inside the Closure Machine is the practitioner-true counterpart: the abstract Stack architecture is right, but the unit of analysis inside an actual ministry is not the decision but the durable position, and the governance-arc primitives are relocated and constrained when read through the pre-clearance machinery that produces durable positions. Both essays are reading disciplines on the Stack rather than additional layers in it.

The stack is not exhaustive of the corpus. Several essays are foundational (the physics and architecture beneath the stack) — The Four Axiomatic Dilemmas, The Physics of Intelligence, The Physics of Moloch, The Thermodynamics of Power, Telic Systems (the corrective-architecture class the stack applies to; the five-property diagnostic decides what counts), The Sovereignty Ladder (the nine-rung taxonomy of telic systems, prion to civilisation), and The Three-Layer Architecture (the reactive/constitutional/strategic layering that recurs across scales). Others are domain-applied (AI alignment, Finnish-specific institutional analysis, the alignment-via-physics treatments). Others are about the craft of writing the essays themselves (Essay Engineering, Optimal Prose, How I Work). Those are listed on the main essays index rather than here, because the stack is a failure-mode taxonomy for goal-directed systems and they sit alongside it rather than inside it.


The argument in three sentences. Goal-directed systems fail at one of roughly a dozen recognisable layers, and the failures at each layer have the same shape across very different domains. The vocabulary of the stack lets a post-mortem be specific — this failed at the measurement layer, not the ledger layer; this failed at the computation layer, not the compilation layer — instead of devolving into "the system is broken" or "the people are corrupt." The corpus organises by layer because the layer is where the repair is, and the page is the map of where each repair lives.


Sources and notes

Status of the partition. The twelve-layer scheme is a working taxonomy, converged on through internal dialectical work over the corpus. An earlier version of this page used a ten-layer scheme; the current revision splits Measurement out of Compilation and splits Computation/adoption out of Compilation to preserve distinctions the corpus has deliberately made (Non-Compilation vs. Calculemus; Goodhart-family failures vs. Full-Accounting failures). The partition is not claimed to be the periodic table of social science. Other partitions exist — Hirschman's exit-voice-loyalty, Ostrom's design principles for the commons, Tilly's repertoires, the political-economy literature's principal-agent stack, the safety-engineering Swiss-cheese model — and each cuts the same territory differently. The defence of this partition is pragmatic: it organises the corpus, it produces non-empty rows at every layer, and it makes the cross-layer interactions legible. A better partition that did the same work would be welcome.

The master line. "A system fails, relative to telos T, where T-relevant reality enters through a channel the system does not own" is the most compressed form the corpus has converged on. An earlier version omitted the "relative to telos T" qualifier; the qualifier is non-optional because the Stack is telos-relative: the same events can be success under one telos and failure under another. Where individual essays cite "the structural law," this is the form they are pointing at.

Scope discipline (strong / medium / weak / invalid). The Stack applies strongly to institutions and institutionalised systems (ministries, agencies, courts, public consultations, welfare systems, permitting regimes, universities, professional discipline systems, legislative mechanisms, infrastructure decision systems). It applies by translation to software systems, AI systems, markets, cultures, minds, and organisms — but only after substrate-native hardening devices are substituted for institutional ones (records become traces or evals; feedback authority becomes deployment-gate or rollback-trigger; reproduction becomes model lineage or transmission ritual). It applies weakly to isolated actions, reflexes, one-shot decisions with no future state, purely physical processes, simple tools, and systems with no memory or correction loop. It is invalid when: (a) no telos is declared, (b) the local telos is treated as morally final, (c) a Level-2 institutional regularity is treated as Level-1 universal, or (d) a sequential-chain diagnosis is forced onto a parallel-bonded, selector-matrix, allocation-routing, or topology/feedback structure that requires a different geometry.

Three failure types. The Stack must distinguish: telos-misalignment failure (the system executes well but its telos itself fails the meta-telos — the village game running correctly while depleting substrates that deep-time flourishing depends on), execution failure (the system has an acceptable telos but fails at one of the eleven lower layers — the ordinary Stack use), and multi-system collision failure (multiple systems each succeed locally but jointly produce higher-order failure because no one owns the translation between them — the court closing the case while the town reopens it). The third category requires a distinct cross-system primitive, not the Stack alone.

Adjacent maps. Full Accounting and the Capital Stocks reference page work the ledger layer (5) at higher resolution. The Layer Walk is the operational sibling to this page: the procedure for taking a real failure and walking it through the layers this page lists. The Mechanism Analysis defines the pre-enactment legislative artifact; How Mechanism Analyses Are Made defines the production discipline behind it. The full essay list on the articles index is organised by topic cluster rather than by layer, and remains the canonical entry point for readers who do not yet have a specific failure in mind.

Known under-treatments and open writing slots. Measurement (4) and Computation/adoption (7) were the freshly-separated layers; both have dedicated anchors — The Measurement Anchor at Layer 4 and The Refusal to Compute at Layer 7. Feedback (10) is filled by Feedback Authority. Reproduction (11) has solid coverage on chain breakage but weaker coverage on chain formation — a How Generator-Chains Form essay is the non-trivial missing half. The actuator-compilation discipline (the second operation after diagnosis: compiling the diagnosis into a native repair artifact with the right owner, surface, and binding strength) is currently distributed across §V Repair routing, the binding-strength gradient at the Binding gate, the Structural Residue acceptance-by-design expansion, and the Layer 6 Compilation repair-side analogue paragraph; the companion essay When Ownership Is the Wrong Repair consolidates it, with the repair-compilation test and the legitimate-ceiling distinction. These gaps are flagged here so readers can know what is missing rather than assuming silence is consent.

Related references: