Verify me

This site makes claims. This page is a set of checks you can run yourself. Pick a claim, run a command, read the output. A replayed transcript asks you to trust the transcript. A CI run asks for less: trust in the repository’s workflow and in GitHub. A replayed command asks for less still: trust in the pinned revision and your own toolchain.

This page is not a portfolio, a resume, or an advertisement.

Watch. Open a verification result. No toolchain. A CI log or a replayed transcript. Under a minute for a replay; a CI log takes as long as you read it. For: a contracting POC who opened a letter; a hiring manager; a journalist; anyone with a browser.

Run. Run a check. A pinned command. Under a couple of minutes with a Rust toolchain already installed; hours for the Lean proof if you install its toolchain. For: a systems engineer; a reviewer who will clone; anyone who will replay a command.

Read. Inspect a proof. A proof script. No installation. For: a formal-methods reader; someone who will open PROOF.md.

Claims

Claim	Watch	Run	Read
A COSE parser shown not to panic while parsing a signed envelope. 19 theorems, machine-checked.	watch	run	read
An unanchored receipt is reported untrusted, not valid. A tampered file is reported invalid.	watch	run	·
The ATL core library’s test suite passes at a pinned revision.	watch	run	·

Teardowns

One question, eight times: what a published procurement text fixes, and what it leaves open. Analysis of documents, not reproduction of a system.

If a claim above does not survive your check, write me. A verification page nobody uses is decoration. A claim that does not survive is a bug.

Pins: atl-cli@96cc146 · atl-core@d5d89bb · cose-parse-nopanic@d4cd6dc.

Transcripts replayed in the players date from 2026-08-31 (atl-cli) and 2026-09-01 (cose-parse-nopanic); CI run dates are on each page.