oddly
A subject's history with both clocks, one question answered with its receipt, and any receipt verified end to end.
Hosted MCP Server
npx add-mcp 'https://myoddly.com/api/public/mcp'Installs into Claude Code, Codex, Cursor and more
Documentation
rfc-editor.org the standards index, as its editor publishes it
iana.org the root zone's top-level domains
certificate transparency logs signed tree heads, read at their operators
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.
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.
figure 154,415 subjects on the record
receiptsubject page:littlekidsjoy.com · observed 2026-10-10T22:10:25.565Z · fetched 2026-10-10T22:10:25.565Z · source littlekidsjoy.com/
root52ee8d5501b68153ac6315ef162eb968efbd889d0af3855c774f3d00af397408
anchorblock 970,591 · confirmed 2026-10-10T02:04:07.750Z
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.
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.
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.
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.
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.
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.
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.
record
A record, not an arbiter. We say what was published and when. We never say what it means.
receipts
Every number on this site reaches its proof in one click, and goes dark the day it stops being true.
security
Compliance is a by-product of security maturity. The certificate is the record, not the reason.
operator
Built by its own operator behind a gate it cannot release itself. The same accountability we sell is the one we run on.