Where a receipt settles it.
Payments and scams
A shopper pays a store, and the store's page changes the next morning.
The record holds what the page said when they paid, and when we read it.
Insurers at claim time
A claim turns on what a policy page said on the day of the loss.
The insurer will read the sealed copy and both of its clocks.
Agent teams with receipts
An agent acts on a list its publisher can change without notice.
Each action will cite the list as it stood that day, for anyone to check.
Reading from
No logos, and nobody's permission was needed to read any of these. Open one and check what we wrote down against what it says today.
The figure, to ground
Every figure here descends to its anchor.
The figure rests on a receipt, the receipt on the day's root, and the root on an anchor outside our hands. The anchor is the point where checking the record stops involving us.
figure326,428 subjects on the record
rootb2e445604917873236baf6b5868b4d3587ebf3457916c9b345b905c2ed3f3acf
anchorblock 973,014 · confirmed 2026-10-26T02:01:24.709Z
Every receipt of the day, chained: change one and the root changes. The root is what we publish, and the anchor is where its time stops resting on our clock.
Who needs this today
Four decisions the world makes on assertions.
Three of them now have a door.
Four people, four sectors, one root underneath all of them. Today they decide on assertions. Tomorrow they decide on evidence.
Finance
Diligence moves from relationship to arithmetic.
A counterparty's number is trusted because of who handed it over, and nobody can say afterwards what it said on the day the money moved.
When the registries are on the record, the check stops depending on the relationship: the figure, the day the registry published it and the day it was read, sealed before anyone knew it would be questioned.
Opens on company registers and filings, when a signal subject serves publicly.
Commerce
What was actually published, and when.
A competitor's price, a supplier's stock, a marketplace rank. Unverifiable after the fact, until now.
Settle the dispute with the storefront's own words: the value before and after each change, when the source said it and when we looked, sealed. A screenshot never carried the source's clock, which is why this could not be shown before.
Technology
An agent acted. Was it authorised, by whom, when?
Today the answer is a log the acting system wrote about itself, checked against a rulebook that changes without announcing it.
Hold the action against the rulebook as it stood when it happened: the crawler registries and the standards they rest on, read at the source with both clocks and sealed. A receipt anyone can verify, including your regulator.
Compliance and legal
Asked afterwards what was true, when, and on whose say-so.
Today the answer is a retention policy and somebody's recollection, and the evidence you need is the evidence most likely to be gone.
With the record there is something to point at: what the source published and when, read at the source and sealed before anyone knew it would matter. Evidence gathered after the question is asked was always the weaker kind, and until now it was the only kind.
How a team plugs in.
-
The GitHub app
It will classify each pull request and check the approval on the head commit. The verdict will be sealed to your own chain.
Not open yet.
-
The SDK
For actions that never touch a repository. Your agents will call it where they act, and the record will seal at oddly.
Follows the app.
-
The open verifier and the Action
You will check any receipt yourself, with code you can read. The Action will seal a repository's releases into the record.
Not open yet.
-
The trust centre
What we hold ourselves to, area by area, and when each was last read.
When the app opens:
Install the app on one repository.
Merge as you do today. Each verdict is sealed.
Hand the evidence pack to your auditor.
What oddly is
Boring on purpose.
Infrastructure that keeps the receipt.
Decisions in software are moving off prose and onto typed, checkable inputs. The inputs still have to be true. That is the whole company.
A record, not an arbiter. We say what was published and when. We never say what it means.
Every number on this site reaches its proof in one click, and goes dark the day it stops being true.
Compliance is a by-product of security maturity. The certificate is the record, not the reason.
Built by its own operator behind a gate it cannot release itself. The same accountability we sell is the one we run on.
Read it. Build on it. Depend on it.
Read it
Free, with attribution.
Build on it
By the meter. Developers
Depend on it
By contract.