Coherence Energy Labs

The banner is computed, not drawn - the solution of our field equation in exact integer arithmetic, rendered by a program in this repository. CI re-derives it on every push; one byte of drift fails the build. Its receipt is committed beside it and printed on the artifact itself.

Provable software and applied systems, built on coherence energy: one measurable way to know how well any system holds together, and to make it hold together better.

Website  ·  Live demos  ·  Contact

Physics, life, mind, and technology get studied in separate rooms. They share a load-bearing property: parts working together as one. We call that property coherence, and we treat it as an engineering quantity - something you can measure, compute, and build against.

Coherence energy is the cost of holding a system's order together against noise:

E_coh = k_B·T · D_KL( ρ_system ‖ ρ_disorder )

Coherence itself is a field, governed by one screened equation we solve everywhere:

(D·L + κ²I) τ = s

The same equation schedules instructions in our compiler, forecasts natural hazards, plans spacecraft trajectories, and drives attention in our AI systems. It also drew the banner at the top of this page. One discipline, bare metal to cosmology.

A claim is only as strong as the artifact behind it.

Modern software asks for trust. Ours is engineered so that trust is never required. Every result travels a chain of custody in which each link is checkable by a stranger:

 source          certified          deterministic         receipt            stranger           a claim
 one program ──► compile      ──►  execution       ──►  program + input ──► verification  ──►  you can
                 proven equal      0 ULP across          + cryptographic    zero lines of       cite
                 over ALL inputs   CPU·GPU·WASM·browser  hash               our code needed

• Every result ships as program + input + receipt. Anyone can re-execute it and get the same bytes.
• Every guarantee has a gate that can say no. Our CI gates are mutation-tested - we deliberately inject the bugs they claim to catch and prove they go red. A gate that cannot fail is not a gate.
• Every failure is published, not buried. We keep a falsification library of our own dead claims, dated and preserved. Negative results are load-bearing.
• Everything fails closed. When evidence is missing, the answer is "no" - in our compilers, our proofs, and our AI.

Our live demos hand you the verifier:

• The Gauntlet - honest and forged computation proofs, checked entirely in your browser. The forgeries fail on your hardware, by your arithmetic - not our word.
• Re-executable figures - every published chart is a program, its input, and its receipt. Your browser re-derives the result and confirms it, offline, from a local file, with no server to trust. A figure you can't fake is a figure you can cite.
• CPU == GPU, live - the same computation on two different substrates, agreeing to the last bit, in front of you.

No accounts. No telemetry. No network required. The proof either verifies on your machine or it doesn't.

Two energy ledgers sit in this repository - 4,096 integer transfers across 64 accounts each, generated by the same program. In one of them, a single entry was altered by one unit - one part in billions of total flow. No chart will show it. No statistic will find it fast. The books find it instantly, because conservation is a sum, not a vibe:

git clone https://github.com/coherence-energy-labs/.github && cd .github
python tools/conservation_challenge.py --audit assets/ledger-a.json   # one says BOOKS CLOSE, drift = 0
python tools/conservation_challenge.py --audit assets/ledger-b.json   # the other names the broken accounts

The forged ledger doesn't just fail - the audit names the exact accounts where conservation breaks, drift ±1, at both ends of the altered transfer. This is the discipline our applied systems run on: exact-integer books that close to zero, or say precisely why they don't. This page practices what it preaches. The banner is a re-executable figure with its receipt committed, guarded by a public gate that re-derives it from source on every push and on a weekly schedule. Clone this repo and run python tools/render_banner.py --check - you'll re-create the org's face, byte for byte, on your own machine.

Artifacts before adjectives. Nothing is called done, fast, or safe without a machine-checkable artifact behind the word. First failure is fuel. A red gate is never reverted around - it is root-caused and the system comes back stronger. Falsify your own work first. Every major claim ships with the experiments that tried to kill it. Preserve coherence. We build systems that do not hide how they work - that can be inspected, that can prove what happened, and that hold together instead of falling apart.