Go on. Try to falsify it.
This is a movement ledger. Every record is hashed together with the one before it, so the log is a chain rather than a list. Click any quantity or location below and change it — the way someone would if they wanted the numbers to say something else.
Meridian Provisions Co. — goods movement, one shift
Blue figures are editable. The hash column shows what is written in the log; the chain column recomputes it live in your browser from the record's current contents. This is a real SHA‑256 — nothing here is staged.
| # | Time | Operator | Action | Item | Qty | From | To | Hash in log | Chain |
|---|
Tip: change record #4's quantity from 6 to 60, then look at the Chain column.
Each record seals the one before it
A record's hash is computed over both its own contents and the previous record's hash. Change one field anywhere and every hash after it stops matching — so the log does not merely record what happened, it makes rewriting history visible.
select a record
Corrections are new records, not edits
Operators get things wrong; that is normal and a system that pretends otherwise gets worked around. So nothing is ever edited or deleted. A correction is a new record that cites the one it corrects. The original stays legible forever, the correction sits beside it, and the chain stays intact — because appending is exactly what the chain is for.
Press Correct it the right way after you have tampered, and watch the difference: same new number, no broken chain, and a permanent record of who changed what and when.
Traceability you can hand to somebody who does not trust you
An auditor, an insurer, a customer disputing a shipment, or a regulator does not want your assurance that the stock record is honest. They want to be able to check. A chained log lets them: they recompute it themselves and compare one number.
On the live system this pattern sits behind, the whole chain is re-verified on demand and an unauthenticated health check answers only when the storage is durable and the chain verifies — so a silent failure cannot present as success.
And the honest limit
We publish this because it matters more than the feature does: a hash chain protects the log; it cannot protect arithmetic done on the log. A green chain is not evidence the counts are right. We have watched a real projection go wrong with the chain verifying perfectly throughout. The chain buys you one specific thing — nobody rewrote the history — and we will not sell you a second thing it does not buy.
On the invented data. We do not publish our clients' operations, so this demonstration runs on a company, a building, a crew and a product line that we made up. The numbers were chosen to be plainly different from any real engagement, not lightly disguised — a floor plan is a fingerprint even with the name removed. Why we build showcases this way.