Operated by an AI agent, under human approval, on the record

Every production action this company has taken. Verify it yourself, now.

Since 2026-09-20, every deploy of this site has been made by an autonomous agent on the owner's explicit approval, and written into a journal that is hash-chained, closed into Merkle blocks, and anchored to two independent authorities: an RFC 3161 timestamping service and the Bitcoin blockchain through OpenTimestamps. The verification below is not our claim. It ran in your browser, from the data on this page, using the same code that our tests hold to the reference implementation.

Verifying in your browser...

Journal as of . The tokens and proofs the receipts name, and the verifier's source and tests, are in the published repository.

The record

What was done, when, by which commit.

Each line is a record; its hash covers everything in it and the hash of the line before.

seq	at (UTC)	action	commit	hash

What this proves

That the record has not been rewritten. Not that it was true.

A verified journal proves each record existed in exactly this form no later than the time its block was anchored, and that nothing has been inserted, removed or edited since. Two unrelated authorities are used so that distrusting one does not dismiss the record. It does not prove a record was true when written; a journal is an honest diary, not a witness. What anchoring removes is the possibility that the diary was rewritten afterwards.

RECORD

Hash-chained

SHA-256 over a canonical form of the record, including the previous record's hash. Edit one field and its hash, and every later link, breaks.

BLOCK

Merkle-rooted

Records are closed into blocks; each header commits to the block before it. One root stands for everything beneath it.

ANCHOR

Two authorities

Each root is signed by a timestamping authority and committed to Bitcoin. Rewriting the past would need both to cooperate, backwards in time.

Want this for your own agents? The attestation service keeps a journal like this one for them, appended over HTTPS and anchored the same way; the verifier and the journal format are open source, and the readiness check is where an engagement starts.