Back to Archive
RESEARCHResearch

Informational Entropy Is Not Thermal Entropy

Why the distinction matters for the foundations story and how it sharpens the claim boundary around Digital Circuitality.

2026-03-12T00:00:00.000Z
Editorial cover for Informational Entropy Is Not Thermal Entropy

A Joke That Became a Crisis

When Claude Shannon was deciding what to call his new measure of uncertainty, John von Neumann gave him a piece of advice: "Call it entropy. Nobody understands entropy, so in a debate you will always have the advantage."

It was a brilliant joke. And it created seventy years of confusion. The naming collision between Shannon's information entropy and Boltzmann-Clausius thermodynamic entropy has produced a genuine scientific crisis — one that reaches into computer science, physics, and the very foundations of how we think about computation.

The Confusion

For decades, computer science has operated on a deeply held assumption: that information entropy (Shannon) and thermal entropy (Boltzmann/Clausius) are intimately related. The supposed bridge between them is Landauer's principle — the claim that erasing one bit of information must dissipate at least kT ln(2) joules of energy as heat, where k is Boltzmann's constant and T is the temperature of the environment.

Since Rolf Landauer proposed this in 1961, it has been treated as physical law. Entire research programs — reversible computing, quantum thermodynamics of information, Maxwell's demon resolutions — were built on this assumption. Textbooks teach it. Papers cite it. Conferences take it for granted. Careers depend on it.

But what if the two entropies are not the same quantity at all? What if the entire bridge is an illusion?

The Refutation: Kish and Ferry (2018)

In 2018, Laszlo B. Kish and David K. Ferry published a rigorous analysis that proved — with mathematical precision — that information entropy and thermal entropy are fundamentally different quantities. "Apples and oranges" that cannot be equated. Here is what they found:

1. Thermal entropy is objective. It is a property of the physical system itself. It does not depend on who is measuring it or what instrument is used. A gas at temperature T in volume V has a definite thermodynamic entropy regardless of the observer. It is a fact about the universe.

2. Information entropy is subjective. It depends on the measurement instrument, the observer's knowledge, and the chosen encoding. The same physical system can have completely different information entropies depending on how you measure it and what you already know. It is a fact about the observer.

3. They can be separated in space and time. The information about a system and the system's thermodynamic state can exist in completely different locations at completely different times. This single fact makes any general equivalence mathematically outside the declared model.

4. Information entropy can violate the Third Law of Thermodynamics. At absolute zero, thermodynamic entropy reaches a minimum. Information entropy has no such constraint — it can take any value regardless of temperature. They do not even obey the same laws.

Reference: L.B. Kish and D.K. Ferry, "Information entropy and thermal entropy: apples and oranges," J. Comput. Electron. 17, 43-50 (2018).

Zero-Energy Erasure

But it gets even more devastating. Even before the 2018 paper, Kish and collaborators had already struck at the heart of Landauer's principle. In 2016, they demonstrated something remarkable: information erasure can occur with zero or even negative energy dissipation through thermalization in double-potential-well memories.

The mechanism is elegant: a memory element with two potential wells (representing 0 and 1) can be erased by allowing the system to thermalize — to reach thermal equilibrium with its environment. This process does not require the minimum kT ln(2) energy dissipation that Landauer predicted. In certain configurations, it can even release energy. Let me say that again: erasing a bit can give you energy back.

This means Landauer's erasure bound is not an approximation that future technology might approach. It is fundamentally wrong as a universal physical law. The emperor has no clothes.

Reference: L.B. Kish, C.G. Granqvist, S.P. Khatri, and F. Peper, "Zero and negative energy dissipation at information-theoretic erasure," J. Comput. Electron. 15, 335-339 (2016).

The Key Insight for Software

Now here is where this physics debate becomes directly relevant to what we build. Kish's 2016 paper contains a remarkable result (Equations 11-12): in a deterministic computer with error-free memory, the information entropy is always zero.

Stop and think about what this means. A deterministic program that takes input X and always produces output Y has zero informational uncertainty. No randomness. No ambiguity. No missing information. The Shannon entropy of its output, given its input, is exactly zero. That is not a metaphor. That is a mathematical fact.

This is precisely what Phi C = 1 means in Digital Circuitality. A formally verified, deterministic system — one where every input maps to exactly one output through a verified transformation — has zero informational uncertainty. When the Circuitality Coefficient reaches unity, the system's information entropy reaches zero. These two conditions are mathematically equivalent. And that equivalence is the foundation of everything we build.

What This Changes for Digital Circuitality

Our framework originally referenced Landauer's principle as part of its thermodynamic analogy. Thanks to Prof. Kish's direct guidance, we corrected this. And here is the thing that surprised us: the correction made the framework stronger, not weaker.

The framework is now purely information-theoretic. Our verification metrics no longer rely on any contested relationship between information and physical energy. They measure one thing: informational uncertainty. Pure Shannon entropy. No thermodynamic claims. No physics debates. Just math.

Phi C = 1 means zero informational uncertainty. When the Circuitality Coefficient reaches unity, the system has zero information entropy. Not zero physical energy. Not zero heat dissipation. Zero uncertainty about what the system will do. This is a statement about knowledge and determinism — the purest kind of engineering guarantee.

No dependency on contested physics. By removing the Landauer connection, Digital Circuitality no longer depends on any disputed physical claim. The framework stands on pure information theory — Shannon (1948), established and uncontroversial for nearly 80 years — plus formal verification, which is pure mathematics.

A theory that depends on fewer assumptions is more robust than one that depends on more. We removed an assumption, and the whole structure got stronger. That is how you know the correction was right.

Brillouin's Negentropy

The correct historical inspiration is Leon Brillouin (1953), who proposed that information is negentropy — the negative of entropy. Gaining information about a system reduces your uncertainty, which is analogous to reducing entropy. It is a beautiful idea, and it motivated much of Digital Circuitality's early development.

But we are honest about the limitations. Even Brillouin's negentropy principle is not a general law. Kish and Ferry (2018) show that the relationship between information and thermodynamic entropy is more nuanced than a simple negation. There are cases where gaining information does not correspond to any thermodynamic change, and cases where thermodynamic changes carry no informational content.

So Digital Circuitality takes the safest possible path: pure Shannon information theory, with physical analogies used as metaphor and intuition, never as foundation. We say that a verified system "behaves like" a low-entropy physical system because it is deterministic and predictable. We do not claim that verification literally reduces thermodynamic entropy or saves physical energy. We are very precise about this distinction.

The metaphor is powerful. The physics would be wrong. We chose the math.

Seventy Years of Confusion, Resolved

Von Neumann's joke has had a long run. For seventy years, the conflation of information entropy and thermal entropy has muddied the waters in physics, computer science, and everything in between. Researchers built careers on the assumption that erasing a bit costs energy, that Maxwell's demon is defeated by Landauer's principle, that computation has irreducible thermodynamic limits. Entire fields were built on a naming collision.

Kish and Ferry resolved this confusion with mathematical rigor. The two entropies are different quantities with different properties, different domains, and different physical meanings. They share a name and a functional form — and absolutely nothing else.

Digital Circuitality builds on this resolution. By grounding our framework in pure information theory — where it belongs — we inherit the mathematical certainty of Shannon's work without the baggage of contested thermodynamic claims. The result is a framework that is cleaner, more honest, and built to last.

Sometimes the strongest move in science is admitting what you got wrong and building something better on the correction. That is exactly what we did.

Published by the BRIK64 team. For more on Digital Circuitality, see What Is Digital Circuitality?, EVA Algebra Deep Dive, and Precision as Domain.

More reading

Continue the archive

Full archive
Technical BRIK64 diagram showing an AI coding prompt transformed into a reviewable blueprint, human review checkpoint, and target outputs.
AI safetyUncategorized

Reviewable AI Coding Pipelines: From Prompt to Blueprint

AI-generated code workflows become more reviewable when teams separate the prompt, generated code, structural blueprint, human review, and target compilation.

Open article
BRIK64 editorial image showing AI-generated software becoming inspectable, certified, and compiled across targets.
AI-generated softwareUncategorized

Making AI-Generated Software Reviewable

AI-generated software can move quickly, but it still needs structure, traceability, and review boundaries. BRIK64 helps teams preserve the blueprint behind generated code.

Open article
Editorial cover for AI Governance Workflows Need Reviewable Technical Evidence
AI SAFETYAI Safety

AI Governance Workflows Need Reviewable Technical Evidence

How bounded software evidence can help teams carry AI governance reviews into compliance workflows without implying full legal coverage.

Open article
Editorial cover for Compiler Evidence: Targets, Proof Files, and Test Scope
ENGINEERINGEngineering

Compiler Evidence: Targets, Proof Files, and Test Scope

A summary of the public numbers that can be stated responsibly and the limits of what those numbers prove.

Open article
Editorial cover for Safety-Critical Software Needs a Readable Assurance Path
PRODUCTProduct

Safety-Critical Software Needs a Readable Assurance Path

How bounded software evidence can support engineering review in high-consequence domains without replacing the broader safety program.

Open article
Editorial cover for Bounded Contract Logic Before Deployment
PRODUCTProduct

Bounded Contract Logic Before Deployment

Why smart contract workflows benefit from explicit state boundaries, value constraints, and reviewable rule sets before deployment.

Open article
Editorial cover for What the Proof Material Means for Users
VISIONFoundations

What the Proof Material Means for Users

A practical note on the proof files behind the compiler and what remains invisible to a normal authoring workflow.

Open article
Editorial cover for Why a New Format Instead of Another General-Purpose Language
VISIONFoundations

Why a New Format Instead of Another General-Purpose Language

Why BRIK64 introduces PCD as a bounded computational format rather than extending a conventional language with another annotation layer.

Open article
Editorial cover for Adversarial Testing Against the Compiler Chain
ENGINEERINGEngineering

Adversarial Testing Against the Compiler Chain

How the team tries to break the compiler and what those tests can and cannot prove about the formal system.

Open article
Editorial cover for Translation Validation Across Two Targets
RESEARCHResearch

Translation Validation Across Two Targets

A look at cross-target output comparison, what it can support, and what still depends on the bounded intermediate form.

Open article
Editorial cover for Why Tests Passing Is Not the Same as Closure
VERIFICATIONEngineering

Why Tests Passing Is Not the Same as Closure

A look at sampled testing versus bounded verification, with examples of logic that passed tests but still required stronger structural checks.

Open article
Editorial cover for One Blueprint Across Multiple Targets
PRODUCTProduct

One Blueprint Across Multiple Targets

How the transpilation chain uses PCD as a bounded intermediate form, what 10 source languages and 14 targets mean in practice, and where the equivalence claim stops.

Open article
Editorial cover for What AI Intuition Still Cannot Verify
AI SAFETYAI Safety

What AI Intuition Still Cannot Verify

Why intuition without an external proof path remains a risk, and where BRIK64 fits in that boundary.

Open article
Editorial cover for API and MCP Access Around the Registry
PLATFORMProduct

API and MCP Access Around the Registry

How discover-and-execute workflows expose registry and platform operations to humans and agents without enlarging the proof claim.

Open article
Editorial cover for Blueprints Before Refactors
REVOLUTIONProduct

Blueprints Before Refactors

How extracting bounded computation from an existing codebase can make rewrites and target changes easier to review.

Open article
Editorial cover for A Bounded JavaScript-to-Rust Workflow
TUTORIALGetting Started

A Bounded JavaScript-to-Rust Workflow

Lift the logic, review the bounded blueprint, then emit a target language while keeping the claim attached to the intermediate circuit.

Open article
Editorial cover for Lifting Existing Code into a Reviewable Blueprint
TOOLINGProduct

Lifting Existing Code into a Reviewable Blueprint

What the Lifter preserves, where liftability evidence exists in the repo, and how bounded blueprints help before migration.

Open article
Editorial cover for COBOL Migration Through Bounded Lift-and-Review
MIGRATIONProduct

COBOL Migration Through Bounded Lift-and-Review

Why legacy modernization benefits from lifting review-critical logic into a bounded blueprint before transpilation or replacement.

Open article
Editorial cover for Why AI-Generated Code Needs Blueprints and External Checks
PRODUCTAI Safety

Why AI-Generated Code Needs Blueprints and External Checks

Generated code and generated tests can fail together. This note explains why BRIK64 keeps verification outside the model loop.

Open article
Editorial cover for Which Parts of a Codebase Are Ready for Stronger Review?
PRODUCTProduct

Which Parts of a Codebase Are Ready for Stronger Review?

Use lifting and bounded analysis to identify review-critical functions before migration or certification work.

Open article
Editorial cover for Laszlo B. Kish and the Information-Theory Thread
RESEARCHResearch

Laszlo B. Kish and the Information-Theory Thread

A research profile on the ideas that influenced the information-theoretic framing behind Digital Circuitality.

Open article
Editorial cover for From Preferences to Enforced Action Boundaries
AI SAFETYAI Safety

From Preferences to Enforced Action Boundaries

Why robotics and agent systems need explicit action gates, bounded state, and reviewable fallback paths.

Open article
Editorial cover for First PCD Circuit: A Minimal Walkthrough
TUTORIALGetting Started

First PCD Circuit: A Minimal Walkthrough

Install the CLI, write a small circuit, and inspect the bounded output path. A practical introduction to the format and the compile step.

Open article
Editorial cover for EVA Algebra: Sequence, Parallel, Conditional
DEEP DIVETheory

EVA Algebra: Sequence, Parallel, Conditional

How three composition operators carry sequencing, fan-out, and branching through the circuit model, and what that means for compiler readability and closure.

Open article
Editorial cover for Working with the SDKs Without Leaving the Bounded Model
SDKSGetting Started

Working with the SDKs Without Leaving the Bounded Model

How the Rust, JavaScript, and Python SDKs expose BRIK64 patterns while keeping the formal core distinct from host-language code.

Open article
Editorial cover for Why Software Verification Still Looks Different from Hardware
RESEARCHResearch

Why Software Verification Still Looks Different from Hardware

A comparison between sampled software testing and the compositional review posture hardware teams expect.

Open article
Editorial cover for 128 Operations and the Boundary Between Core and Bridges
ENGINEERINGEngineering

128 Operations and the Boundary Between Core and Bridges

A tour of the reviewed core, the contract-bounded extensions, and what that split means for technical scope.

Open article
Editorial cover for PCD for AI Agents: A Small Format with an External Proof Loop
AI AGENTSAI

PCD for AI Agents: A Small Format with an External Proof Loop

How a finite grammar helps agents author bounded logic while the compiler and policy checks stay outside the model.

Open article
Editorial cover for Precision as a Declared Domain
ENGINEERINGEngineering

Precision as a Declared Domain

Why bounded numeric domains matter for floating behavior, decimal handling, and reviewable arithmetic.

Open article
Editorial cover for BPU: Policy Enforcement as a Hardware Roadmap
HARDWAREHardware

BPU: Policy Enforcement as a Hardware Roadmap

Why software-only guardrails share execution context with the model they constrain, and how the BPU roadmap moves policy enforcement toward FPGA and silicon.

Open article
Editorial cover for Policy Circuits for AI Safety Workflows
AI SAFETYAI Safety

Policy Circuits for AI Safety Workflows

How external policy circuits can gate generated code and agent actions without claiming to solve general alignment.

Open article
Editorial cover for What Digital Circuitality Tries to Formalize
VISIONFoundations

What Digital Circuitality Tries to Formalize

A bounded programming model built from reviewed operations, explicit composition, and closure checks.

Open article