---
title: "The Halting Problem of Law"
subtitle: "Why nobody knows what the laws are—and why the system prefers it that way"
author: Elias Kunnas
description: "Tax law: 90-99% formalizable. Administrative regulations: 60-70%. Sentencing: 80% with a discretionary floor. Constitutional: <10%. Empirical data on what portion of law can be computed."
canonical: https://kunnas.com/articles/halting-problem-of-law
url: https://kunnas.com/articles/halting-problem-of-law.md
date_published: 2026-01-18
date_modified: 2026-02-19
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. — [From Telos to Policy](https://kunnas.com/articles/from-telos-to-policy.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>

---

# The Halting Problem of Law

*Why nobody knows what the laws are—and why the system prefers it that way*

Elias Kunnas

## Thesis {#thesis}

Determining what a law currently says after decades of amendments is not a solved clerical task — it is computationally indeterminate, because amendments are semantic instructions requiring human interpretation, not mechanical edits, and that ambiguity structurally favors whoever can afford more lawyers. Formalizability varies sharply by domain, from 90-99% for tax and benefits law down to under 10% for constitutional law, so the fix is not one universal deterministic text but domain-specific: automate what can be automated, and make the remaining discretion visible and logged.

---

## I. The Constitutional Hallucination {#i-the-constitutional-hallucination}

A citizen wants to know what the law says about their situation. They go to [Finlex](https://www.finlex.fi/), Finland's official legal database. At the bottom of every consolidated statute, they find this disclaimer:

> "Oikeusministeriö ei vastaa virheistä." (The Ministry of Justice does not guarantee accuracy.)

The *official government database* doesn't know what the law says. And it explicitly refuses to be held accountable for errors.

This isn't a Finnish peculiarity. [EUR-Lex](https://eur-lex.europa.eu/EN/legal-content/glossary/consolidation.html), the European Union's legal database, states that consolidated texts have "no legal effect"—only the original amending acts published in the Official Journal are authoritative. To know EU law definitively, you must read the base act plus every subsequent amendment PDF and mentally apply the changes yourself.

The working assumption is that consolidation—combining a base law with its amendments to produce current text—is a clerical chore. Something computers should handle easily. The reality is that it's computationally impossible to do reliably.

## II. Syntactic vs. Semantic: The Architectural Flaw {#ii-syntactic-vs-semantic-the-architectural-flaw}

In software, version control works because changes are **syntactic operations**:

- "Replace line 47 with X"
- "Delete lines 10-15"
- "Insert Y after line 20"

Any computer can apply these. Same input produces same output. Deterministic.

Legal amendments are **semantic operations**:

- "Replace 'child' with 'person' everywhere except in §4(2)"
- "The provisions of the 1985 law §12, as they were on 1.1.2010, shall apply"
- "Add exception for cases where the general principle of administrative law applies"

These require *interpretation*. What does "everywhere" cover—references in other laws? Implicit references? Cross-references that reference this section? What was the 1985 law's state on a specific date, and how was *that* derived? What are "general principles of administrative law"—they're not enumerated anywhere, they evolve through case law, and different jurists disagree.

The problem isn't append-only architecture (that works fine in databases). The problem is that amendments are semantic instructions rather than syntactic diffs. Semantic operations require human judgment. Human judgment produces inconsistent results.

## III. The Compile-Time Problem {#iii-the-compile-time-problem}

In software development:

- The compiler forces ambiguity resolution *before* execution
- If code is ambiguous, it doesn't compile
- Errors are caught before deployment

In law:

- The "compiler" is the Judge
- The Judge only runs *during* a lawsuit (runtime)
- And only on the specific provisions that caused the "crash"

The vast majority of legal code is never compiled. It exists in a quantum superposition of "maybe valid, maybe not" until someone gets sued. A [2025 French study](https://arxiv.org/abs/2501.16794) attempted to automate consolidation using GPT-4 and achieved only 63% accuracy on complex bills—the remaining 37% included "hallucinations" where the model invented plausible but incorrect legal phrasing.

If state-of-the-art AI can't reliably consolidate legislation, the problem isn't inadequate tooling. The problem is that the input data is architecturally incompatible with deterministic processing.

## IV. Error Accumulation {#iv-error-accumulation}

Model consolidation as a state machine:

```

S₀ = Initial Law
δ = Transition Function (Amendment)
S₁ = δ(S₀, A₁)
S₂ = δ(S₁, A₂)
...
Sₙ = δ(δ(δ(S₀, A₁), A₂), A₃)...
```

If δ is ambiguous (semantic operation), uncertainty compounds through the chain. Finnish tax law has undergone 50+ amendments over decades. Each δ introduces interpretation variance. By amendment 50, the "current state" is unknowable without an oracle (a court ruling).

**The test:** Give the same base law and amendments to five law firms. Ask each to produce a consolidated text. Will you get five bit-for-bit identical files?

Almost certainly not. The "current state of the law" is not a deterministic value—it's a probability distribution across possible interpretations.

## V. The Intent Trap {#v-the-intent-trap}

In software:

```

// This function calculates tax (intent)
return x * 0.25; // (reality)
```

Intent is a comment. Code is reality. If the comment says "calculates tax" but the code returns a random number, the code wins.

In law, intent (*esityöt*/preparatory documents) is treated as part of the source code. "What did the legislators mean?" requires consulting committee reports, parliamentary debates, and expert opinions.

The bug: you cannot mechanically merge intent. You can only merge text. By treating intent as resolvable, the system guarantees non-determinism. Even if you could query the original legislators:

- They may disagree with each other
- They may be dead
- Their "intent" may have been a political compromise with no coherent meaning

## VI. The Oracle Is Also Broken {#vi-the-oracle-is-also-broken}

The Supreme Court is supposed to be the final oracle—the authority that resolves ambiguity definitively. But oracles produce split decisions. 5-4 rulings are common. The nine "most qualified" legal minds in the country cannot agree on what the law means.

If they can't agree, what does "correct answer" even mean?

Worse: the law is temporally unstable. *Roe v. Wade* (1973) stood for 49 years as "settled law" before *Dobbs* (2022) reversed it. *Plessy v. Ferguson* (1896) lasted 58 years before *Brown v. Board* (1954). Same constitutional text, different answers.

```

Law(case, t) = f(court_composition_at_t)
Law(case, t+50) ≠ Law(case, t)
```

One justice dying literally changes what the law "is." This isn't discovery of truth—it's creation by majority vote among a politically-selected group, revocable by future majority votes.

Prediction models achieve [70%+ accuracy](https://scholarship.law.duke.edu/cgi/viewcontent.cgi?article=1630&context=lcp) forecasting Supreme Court rulings based solely on political variables. If an algorithm can predict rulings without reading the legal arguments, the written opinions are post-hoc rationalization, not causal reasoning.

The system is:

1.  **Non-deterministic:** Multiple valid outputs exist at time T
2.  **Temporally unstable:** Output at T can be invalidated at T+n
3.  **Non-monotonic:** Past "settled" answers can be declared wrong

Stare decisis is a norm, not a guarantee. The law is whatever five people agree it is today, until five different people disagree tomorrow.

## VII. The Economic Cost of Pretending {#vii-the-economic-cost-of-pretending}

The [Confederation of Finnish Industries](https://ek.fi/en/current-affairs/) estimates regulatory compliance costs Finnish businesses 5-7 billion euros annually. A significant portion isn't the cost of following clear rules—it's the cost of figuring out what the rules say.

This "interpretation tax" includes:

- Legal fees for navigating ambiguity
- Delayed decisions while awaiting clarification
- Abandoned projects in uncertain regulatory zones
- Risk premiums for operating where law is unclear

The [Standard Cost Model](https://www.oecd.org/en/publications/2025/04/oecd-regulatory-policy-outlook-2025_a754bf4c.html) used by the OECD breaks administrative burden into "familiarization costs" (understanding obligations) and "substantive costs" (fulfilling them). If law isn't consolidated reliably, familiarization costs explode. Reading base_act.pdf + amendment_A.pdf + amendment_B.pdf + amendment_C.pdf takes far longer than reading consolidated_law.pdf.

Because EUR-Lex and Finlex explicitly disclaim accuracy, businesses operate in a liability grey zone. Follow the government's consolidated text, get fined because it contained an error, and your defense ("I relied on the official database") fails because the database warned it wasn't authoritative.

This forces "double verification"—checking official gazettes against consolidated texts—or purchasing expensive private legal databases. The state produces raw material (acts) but refuses to guarantee the finished product (consolidated law), creating a market for legal certainty that shouldn't need to exist.

## VIII. The "Flexibility Is Good" Defense {#viii-the-flexibility-is-good-defense}

Lawyers will object: "We need discretion! Rigid rules can't handle edge cases! Flexibility serves justice!"

The counter: Discretion belongs in **application** (judicial), not **consolidation** (clerical).

These are different operations:

- **Consolidation:** What does the law say? (Should be deterministic)
- **Application:** How does this law apply to this case? (Can involve judgment)

We need to know WHAT the text is before deciding HOW to apply it. Currently we argue about both simultaneously. This is like debating what the source code says and what it should do at the same time.

In functional programming, you isolate pure functions from IO—side effects are contained in explicit monads, not scattered throughout. Good legal architecture does the same: **isolate the discretionary**. Mark exactly where human judgment enters. Keep everything else deterministic.

Formalizability varies by domain, not provision type. Empirical data:

- **Tax & Benefits: 90-99% formalizable.** OpenFisca encodes 3,963 legislative elements of France's socio-fiscal system. U.S. Tax Court: 99.2% of cases settle without trial—the outcome is predictable enough that parties don't fight. [Catala](https://www.inria.fr/en/catala-software-dgfip-cnaf) runs in production at French tax authority.
- **Administrative regulations: 60-70%.** [Information-theoretic analysis](https://www.frontiersin.org/journals/physics/articles/10.3389/fphy.2021.671882/full) shows regulations have high compression factors (code-like structure). But [Chevron data](https://wclr.commonwealthlaw.widener.edu/wp-content/uploads/2025/01/chevron-on-the-eve-of-loper-bright-nicholas-r.-bednar.pdf): in contested cases, only 32.8% of statutes were "clear"—66.4% required interpretation.
- **Sentencing: 64-80%, with a floor.** U.S. Sentencing Guidelines adherence: 80.6% (1991) → 63.9% (2001) → ~42% (2024, advisory era). Even mandatory guidelines hit a ["20% discretionary floor"](https://www.ussc.gov/sites/default/files/pdf/news/congressional-testimony-and-reports/departures/200310-rtc-downward-departures/ch3fnl.pdf)—judges found reasons to depart.
- **Constitutional/Civil: \<10%.** High vocabulary entropy, low compression. "Due process" and "reasonable care" are semantic, not syntactic. These function like literature, not code.

The Chevron 66.4% "ambiguous" rate measures *contested* cases—the hard edge. The Tax Court 99.2% settlement rate measures the *base*—where the law is clear enough that parties don't litigate. Both are true: most tax law is deterministic, but the edges of administrative law are genuinely ambiguous.

By making consolidation non-deterministic, we've imported judgment into what should be a mechanical operation. The flexibility lawyers value in application has leaked into the infrastructure layer, corrupting the foundation.

## IX. Power Is the Substrate {#ix-power-is-the-substrate}

Legal non-determinism isn't an accident. It's a power architecture.

**Ambiguity favors the powerful:**

- Those with resources can argue for favorable interpretations
- Expensive lawyers find "creative readings"
- The poor get default (unfavorable) interpretations
- Same text, different outcomes based on who's arguing

If law is an NP-hard search problem, "justice" becomes a function of computational power. In legal context, compute equals billable hours. A litigant with unlimited resources can pay a team to exhaustively search the decision tree for winning arguments, obscure precedents, or procedural loopholes.

This creates regressive distribution of legal error. The poor are subject to "rough justice"—heuristics, plea bargains, summary judgments—because they can't afford the compute required to verify their rights. The rich purchase "precision justice"—exhaustive procedural verification and exploration of every interpretive branch.

**Deterministic law would constrain power:**

- Formal specifications leave no room for "interpretation"
- Version control prevents rewriting history
- The powerful couldn't purchase favorable readings
- Law would actually bind equally

**This explains why the obvious fix hasn't happened.** It's not ignorance or technical difficulty. Ambiguity is load-bearing for the current power structure. Legal interpretation is a power-hiding mechanism. "We're just finding the correct meaning" obscures "we're deciding who wins."

Making law deterministic would be power-revealing. It would show who benefits from current rules. It would constrain discretion. It would make law actually bind the powerful. It would reduce the value of expensive lawyers.

The resistance to formal legal infrastructure isn't conservative inertia. It's that the Head (power) will resist any Skeleton-strengthening move (constitutional constraint).

## X. The Full Law-Power Chain {#x-the-full-law-power-chain}

Non-determinism enters at every stage:

1.  **Creation:** Legislature writes semantic amendments. Ambiguity may be intentional (defer hard choices) or accidental (rushed drafting). Either way, interpretation is delegated downstream.
2.  **Publication:** Official databases disclaim accuracy. Citizens can't know what the law says. The state refuses to guarantee its own rules.
3.  **Interpretation:** Courts resolve ambiguity—but produce split decisions, reverse precedents, and vary by composition. The "oracle" is probabilistic.
4.  **Application:** Who can afford to explore the decision tree? Rich litigants purchase precision justice; the poor get rough justice. Same text, different outcomes based on compute budget.
5.  **Oversight:** Who holds courts accountable? Judicial independence protects against political interference but also shields patterns of discretion from scrutiny. (See: [Theatrical Accountability](theatrical-accountability.md).)
6.  **Amendment:** Can the system correct itself? Constitutional lock-in and veto players prevent adaptation.

This essay focuses on stages 2-3 (publication and interpretation). But even perfect consolidation wouldn't solve stages 4-6. And there's a deeper problem: [the statute is not the runtime](laws-are-the-wrong-abstraction.md). Legal text changes authority, expectations, incentives, remedies, and available actions; it does not by itself supply interpretation, capacity, enforcement, feedback, or correction. Treating promulgation as delivery leaves the causal composition unspecified.

Solving the Halting Problem of Law is necessary but not sufficient. You need to know what the law says (this essay's focus). But you also need mechanisms that make the law *effective*—skin in the game, automatic triggers, exit rights. A right without a mechanism is a wish.

## XI. The Estonian Half-Solution {#xi-the-estonian-half-solution}

Estonia has made progress. Since 2010, the electronic [Riigi Teataja](https://www.riigiteataja.ee/en/) has been the only official publication, and consolidated texts are legally binding.

But Estonia still has consolidation. Amendments are still semantic instructions that must be interpreted and applied to produce consolidated text. The state just takes responsibility for the result instead of disclaiming it.

This is better than nothing—it shifts liability from citizen to state, which creates an incentive for accuracy. But it doesn't solve the underlying problem. The consolidation step still exists. Interpretation still happens. Errors are still possible. Estonia has moved the risk, not eliminated it.

The real solution is more radical: **eliminate consolidation entirely**.

Instead of: Base Law → Semantic Amendment → Interpretation → Consolidated Text

Do: Database State → Direct Edit → New Database State

No interpretation step. No consolidation. The law IS the database. Amendments are commits, not instructions. Parliament votes on the diff, not a description of the diff. The "consolidated text" is just the current state of the repository—always authoritative, always current, no interpretation required.

Estonia proves the problem is political, not technical. But Estonia is step zero (accept liability for consolidation). The full solution is step one (no consolidation needed).

## XII. Architecture That Forces Honesty {#xii-architecture-that-forces-honesty}

The system currently pretends courts "discover" eternal truths. How do you architect a system where this pretense becomes impossible?

**Principle:** Don't ask them to stop pretending. Make pretending architecturally infeasible.

**1. Immutable version control.** Every change cryptographically timestamped and signed. You can't claim "the law always meant X" when git log shows otherwise. History becomes undeniable fact, not narrative.

**2. Court composition tagging.** Every decision tagged with judges and vote split. "Decided by \[names\], vote \[5-4\]." Automatically visible: this isn't "the law"—it's what these five people decided. When composition changes, flag all rulings at reversal risk.

**3. Mandatory probability disclosure.** Before ruling, prediction market odds recorded. After ruling, accuracy tracked. System shows: "This court's rulings match market predictions 73% of the time." Undeniable proof the system is probabilistic.

**4. Interpretation cloud.** For ambiguous sections, show ALL valid interpretations. "This clause has 3 valid readings. Courts have chosen \[A\] 60%, \[B\] 30%, \[C\] 10%." You can't pretend one truth when the UI shows three options with percentages.

**5. Precedent stability flags.** Algorithm detects: "This ruling was 5-4. Two majority justices replaced. Reversal probability: 67%." You can't call it "settled law" when labeled "UNSTABLE - HIGH REVERSAL RISK."

**6. Sunset clauses on precedent.** Rulings expire in 20 years unless explicitly renewed. Forces acknowledgment: "We're choosing to keep this" not "This is eternal truth." Each generation must actively affirm, not passively inherit.

**7. Formal specifications where possible.** For calculation laws (taxes, benefits): the specification IS the law. No room for interpretation—the code runs or it doesn't. Projects like [Catala](https://www.inria.fr/en/catala-software-dgfip-cnaf) have formalized parts of French tax code and US benefits law, revealing bugs and inconsistencies that human drafters missed.

The meta-principle: architecture forces honesty. The probabilistic, power-contingent, temporally-unstable nature of law becomes visible through the interface itself. You cannot maintain the pretense when the system shows you the probability cloud.

## XIII. The Solution {#xiii-the-solution}

Recall the empirical partition from Section VIII:

- **Tax & Benefits (90-99%)** — Catala/OpenFisca territory. Fully formalizable.
- **Administrative regulations (60-70%)** — High compression, but contested edges remain ambiguous.
- **Sentencing (64-80%)** — Algorithmic with a "20% discretionary floor."
- **Constitutional/Civil (\<10%)** — High entropy. Literature, not code.

Each domain needs different treatment:

**Tax & Benefits:** Fully deterministic. Law lives in a version-controlled database. Amendments are direct edits, not semantic instructions. No consolidation step—the repository state IS the law. Parliament votes on diffs. The [Catala approach](https://arxiv.org/abs/2103.03198): specification IS the law, natural language is derived. This is proven technology—France runs it in production.

**Administrative regulations:** Formalize the 60-70% that has code-like structure. For the contested edges, bound discretion explicitly: not "reasonable" but "factors A, B, C with weights." Log every application. Make patterns visible.

**Sentencing:** Accept the 20% discretionary floor—judges will depart when the algorithm produces injustice. But require explicit justification. Tag every departure with reasoning. Enable statistical analysis: which judges depart, for whom, how often?

**Constitutional/Civil:** Accept that "cruel and unusual" must evolve. But make interpretation visible. Track how meaning drifts over time. Enable statistical analysis of who gets which interpretation. The discretion remains—the hiding doesn't.

**The meta-principle:** Isolate the impure. Like Haskell separates IO from pure functions, good legal architecture separates the discretionary from the deterministic. Mark exactly where human judgment enters. Keep everything else mechanical.

Estonia is step zero: accept liability for consolidation. The full solution is step one: eliminate consolidation entirely for the 90%+ formalizable domains (tax, benefits). Then bound and log the rest.

## Synthesis {#synthesis}

**The halting problem of law is solvable—for most of it.** Tax and benefits: 90-99% formalizable, proven in production. Administrative regulations: 60-70%. Even sentencing can reach 80% with bounded discretion. Only constitutional and civil law remain genuinely open-textured. Eliminate consolidation where possible. Bound and log discretion everywhere else. The goal isn't eliminating all judgment—it's isolating judgment to where it belongs and making its exercise visible.

The transition to computational jurisprudence is inevitable. The question is whether that code will be a black box of control for the powerful, or an open-source platform for democratic accountability.

---

**Related reading:**

- [The Law in Force Should Be Knowable](https://lawvm.org/the-law-in-force-should-be-knowable/) · [Why Law Is Law-Shaped](https://lawvm.org/why-law-is-law-shaped/) — two short LawVM essays on the civic case and structural design behind reproducible legal text.
- [Laws Are the Wrong Abstraction](laws-are-the-wrong-abstraction.md) — Even perfect consolidation leaves the runtime unspecified. Governance needs law plus delivery architecture.
- [Theatrical Accountability](theatrical-accountability.md) — Stage 5 of the law-power chain: the five-layer stack of elite immunity
- [The Vibes Constitution](vibes-constitution.md) — How Finland built a mood board instead of a legal system
- [Ethics Is an Engineering Problem](ethics-is-an-engineering-problem.md) — Why implementation reliability depends on architecture

## Sources and Notes

**Legal Consolidation & State of the Art:**

- [EUR-Lex Consolidation Disclaimer](https://eur-lex.europa.eu/EN/legal-content/glossary/consolidation.html) — "Consolidated text is meant purely as a documentation tool and has no legal effect."
- [Finnish Legal Database (Finlex)](https://www.finlex.fi/fi/laki/ajantasa/) — Ministry of Justice does not guarantee accuracy of consolidated texts.
- [Estonian Riigi Teataja](https://www.riigiteataja.ee/en/) — Since 2010, consolidated texts are legally binding. A half-solution: moves liability to the state, but still requires consolidation.
- [French AI Consolidation Study (2025)](https://arxiv.org/abs/2501.16794) — GPT-4 achieved ~63% accuracy on complex legislative consolidation. arXiv:2501.16794.

**Computational Law:**

- [Catala Programming Language](https://www.inria.fr/en/catala-software-dgfip-cnaf) — INRIA. Domain-specific language for formalizing tax and benefits law. [Academic paper (arXiv:2103.03198)](https://arxiv.org/abs/2103.03198). 1.5:1 code-to-law expansion ratio.
- [OpenFisca](https://openfisca.readthedocs.io/) — 3,963 coded legislative elements of France's socio-fiscal system. Powers Mes Aides and LexImpact.
- [OECD, "Cracking the Code: Rulemaking for Humans and Machines"](https://read.oecd.org/10.1787/3afe6ba5-en?format=pdf)

**Empirical Legal Analysis:**

- [Bednar, "Chevron on the Eve of Loper Bright"](https://wclr.commonwealthlaw.widener.edu/wp-content/uploads/2025/01/chevron-on-the-eve-of-loper-bright-nicholas-r.-bednar.pdf) — 32.8% of contested statutes clear (Step 1), 66.4% ambiguous (Step 2).
- [USSC Downward Departures Report](https://www.ussc.gov/sites/default/files/pdf/news/congressional-testimony-and-reports/departures/200310-rtc-downward-departures/ch3fnl.pdf) — Sentencing guideline adherence: 80.6% (1991) → 63.9% (2001).
- [Friedrich, "Complexity and Entropy in Legal Language"](https://www.frontiersin.org/journals/physics/articles/10.3389/fphy.2021.671882/full) — *Frontiers in Physics*, 2021. Regulations: high compression (code-like). Constitutions: high entropy (literature-like).
- [Katz, Bommarito & Blackman, "A general approach for predicting the behavior of the Supreme Court"](https://scholarship.law.duke.edu/cgi/viewcontent.cgi?article=1630&context=lcp) — 70%+ accuracy from political variables alone.
- [Confederation of Finnish Industries (EK)](https://ek.fi/en/current-affairs/) — €5–7 billion annual regulatory compliance costs in Finland.

---

***Update (April 2026):** Since this essay was written, [LawVM](https://lawvm.org) has answered the consolidation question empirically. For the text-state layer, \>99% of Finnish statutory text is mechanically reproducible from the amendment chain. The remaining divergences are dominated by errors in the official editorial surface, not limits of the compilation method — meaning that with deterministic compilation as the native pipeline, the theoretical ceiling approaches 100% for well-drafted legislation with clean source data.*

*This essay provides the theoretical foundation for [LawVM](https://lawvm.org) and for [Lainsäädäntöinfrastruktuuri](https://parempisuomi.kunnas.com/lainsaadantoinfrastruktuuri), a proposal for version-controlled legislation with formal specifications. The underlying physics: [The Question Nobody Asks](the-question-nobody-asks.md) → [The Four Axiomatic Dilemmas](the-four-axiomatic-dilemmas.md).*