Writing
Demo · Immutable ledger

Immutable Ledger — a book that never forgets

Hard problem
A spreadsheet forgets the instant you overwrite a cell — hence the trail of saved copies (v1, v2, final-FINAL) standing in for an audit trail — and “what did the books say last quarter?” has no reliable answer.
Approach
Make the book append-only. Every commit adds to the log, a correction appends beside the mistake it fixes, and any past state is derived on demand by querying the book as of a moment in knowledge-time — never restored from a copy.

The trick isn’t saving copies; it’s that history is a query: the books store what changed, and any past state is recovered by asking for it as of a moment in time. Below, the same journal in two books — one built that way, one not.

Two ways to keep a book

Same journal lines, same chart. One book remembers every state it ever held; the other forgets the moment you edit it. Play with both.

Immutable book
Each commit appends to an immutable log — nothing is overwritten. To fix a mistake you append an adjusting line; the original entry and its correction both stay on the record, and every past state stays queryable, plotted as its own series.
DateTypeAmount
No versions yet — commit one to plot it.

Honest cost: the log only grows by what changed (0 entries), never by full copies. At scale you materialise the current state for speed and answer the past with as-of queries — but you never lose it.

Mutable book
Only one book exists. Every edit overwrites in place — the chart shows just the present, and the evidence the books ever said something else is gone.
DateTypeAmount
Net: $1,700
— Current
$0 … $1,700
2026-01-312026-03-31
Time-travel: as of knowledge-time…nothing to travel to

The slider is inert: there is no history. 0 edits → 0 past states unrecoverable.

The trap: it looks tidy — one clean line, no clutter. That tidiness is the data loss.

The axes are the same on both: X = entry date, Y = cumulative net (revenue − expense). The only difference is what happens to the past when you change your mind.

What immutability buys you

Everything below falls out of the same property: state is derived from an append-only log of events.

Full audit trail

Every version is preserved, so you can answer “what did the books say on day N?” without a backup.

Corrections, not erasures

Fixing a mistake appends an adjusting entry. The original error — and its fix — both stay on the record.

Time-travel queries

Reconstruct any historical state on demand; reporting periods become a filter, not a snapshot you had to remember to take.

The idea in full, without the toy — Declarative accounting, explained; and where this property lets AI sit next to the books — the harness.