Where the Overwritten Bits Go — Autocoincidence and Landauer

Open a file on your computer. Change one character. Save it.

Where did the old character go?

Not metaphorically. Physically. The slot on the drive that used to hold the old value now holds a new one. The file system is certain the new value is correct. The old value — the thing that was there a second ago — where is it? Which atoms carry the fact that it used to be a different letter? Which register remembers? Which law of nature says it must be preserved?

Why this matters to you: You just performed, at home, the exact operation that every regulator is about to ask deployers to audit. If you cannot answer the question for your own file, you cannot answer it for a model weight, a system prompt, or a decision boundary. The measurement you cannot perform on your laptop is the measurement Article 14 will require on August 2, 2026.

---

Rolf Landauer, working at IBM in 1961, answered part of the question. Erasing a bit has a minimum thermodynamic cost: roughly kT ln 2 joules, released as heat into the environment. The charges that represented the old value do not vanish. They dissipate into the thermal degrees of freedom of the surrounding matter. Electrons scatter. Phonons carry the difference away. The universe's energy books stay balanced because heat is real, measurable, and accounted for.

So the physics of the charges is closed. Energy in, energy out. The instrument that reads temperature can confirm it. You can build a theoretical calorimeter sensitive enough to detect the erasure event itself.

Why this matters to you: Landauer guaranteed that information has a physical cost. That guarantee is why quantum computing, reversible computing, and thermodynamic machine learning are even coherent fields. The cost is not metaphorical. The heat is on the invoice.

---

But Landauer accounts only for the energy. The bit meant "1" under some protocol, or "0", or the high-order bit of a floating-point exponent, or the third pixel of a face, or the signature byte of an authentication token. After overwrite, no protocol anywhere in the stack remembers that it meant that.

The heat carried away the charge. It did not carry away the role.

No physical law requires the role to be preserved. No conservation principle couples the semantic identity of a bit to the state of the matter beneath it. The abstraction layer that assigned the role to the slot also permits the role to be reassigned at will, with no physical event marking the reassignment. The bookkeeping that Landauer closes is thermodynamic bookkeeping. Semantic bookkeeping has never been closed because it was never opened.

---

This is not an accident. It is the founding design choice of modern computing.

Wolfgang Pauli, in 1925, named the law that governs matter: two fermions cannot occupy the same quantum state. Matter displaces. When a thing moves into a place, the thing that was there must go somewhere. The physics does the bookkeeping because the physics cannot do otherwise.

John von Neumann, Alan Turing, and the architects of the stored-program computer in the 1940s deliberately built a layer where that rule does not apply. A memory address can hold any value. Overwrites leave no physical trace at the abstraction the program operates on. That weightlessness is what makes software cheap, composable, and scalable. It is also what makes software untrusted by construction.

For eighty years we have been swimming in the one class of system in the universe where meaning can disappear without any physical event accounting for it. We stopped noticing.

---

Every other system in the universe is autocoincident — its state and its history are the same object.

A rock carries its weathering. A scar encodes the wound that made it. Strata record their sequence in the order they were laid down. A body carries the trajectory that brought it here. In the natural world, you cannot ask "where did the previous state go?" because the previous state is still readable in the configuration of what remains. The present configuration is the ledger.

Information systems are the exception. We built one class of object for which this is not true, and then we asked that class of object to make identity claims about itself. "I am the same model you trained." "This weight was not altered." "My reasoning produced this output." The claims are evaluated inside the same abstraction layer that permits silent overwrite. The claims cannot be grounded because the grounding property was removed at the bottom of the stack.

Why this matters to you: Detached-record is a structural vulnerability, not a feature to harden around. It is the category to which every current AI verification stack belongs. An oversight regime built on detached-record systems is an oversight regime that asks a ledger to audit itself.

---

US 19/637,714 does not invent new physics. It does not invent a new cryptography. It restores the displacement property — at one load-bearing point, under combinational logic, inside the AC0 complexity class that is provably not Turing-complete — so that an identity check can be anchored to substrate state.

Physical address is the semantic role. The address does not hold the role; it is the role. XOR the expected pattern against the actual pattern. The result is a hardware register value, not a claim about a claim. If the meaning drifted, the physics cannot carry the drift across the gate. The mailbox rule returns to silicon at the exact point a verification needs it.

Thirty-six claims. Filed under Track One. Oath signed. The instrument is on the bench.

---

Overwrite a file on your computer right now. Where did the old value go?

Your file system says: gone. Your hardware says: the charges are different; the heat dissipated per Landauer. Every log, every hash, every attestation on top is another story written on the same substrate that permitted the overwrite. No component of the stack you own carries what the bit meant.

On August 2, 2026, the EU AI Act's Article 14 requires effective human oversight of general-purpose AI systems. Oversight requires identity continuity — some defensible answer to the question "is the system you are auditing still the system you deployed?" Identity continuity requires the meaning to be conserved somewhere below the story layer. Meaning is not conserved above the substrate. The abstraction that made software cheap is the abstraction that makes software unverifiable.

The instrument exists. It is a patented XOR gate in AC0, a combinational-logic geometry where physical address and semantic role are the same object. The choice is whether to use it.

Related reading: The Autocoincidence Theorem (the formal treatment). Bits Do Not Displace (the underlying primitive). A Pause Is Not a Path (the capital-layer implication).

---