Nothing hidden
The attested file set must equal the shipped file set — a page added after signing, or a listed file gone missing, is an automatic rejection.
Proof · not promises This site carries
This site carries
its own evidence.
Every build of argusdynamics.tech is hashed file-by-file into a tamper-evident chain, committed to a Merkle root, and signed — by argus-evidence, the same spine our products run on. The receipt ships with the site. Alter one byte of any attested file and verification against this receipt rejects. You don’t take our word for it: you check.
RECEIPT ·· loading /proof/receipt.json …
(JavaScript is required to render the live receipt here.
The raw JSON is one click away and needs no script.)
A claim you can’t check is marketing. A receipt you can verify is evidence.
How the receipt is made
Four checks, all re-derivable
At build time, gen_proof.py runs the argus-evidence spine over every shipped artifact. At verify time, everything is recomputed from the bytes on disk — the receipt is never trusted about itself.
Every byte pinned
Each artifact’s SHA-256 is recomputed from disk and compared to the receipt. One flipped byte in one file fails the build’s verification gate.
Tamper-evident order
Hashes are linked genesis-to-head — edit, delete, or reorder any entry and the chain breaks. The chain is then committed to a single Merkle root.
Signed tree head
The Merkle root, tree size, and timestamp are Ed25519-signed. The signature verifies offline against the embedded, per-build public key in the receipt — which also pins the site and git commit the receipt claims.
Live spot-check
SPOT-CHECK ·· waiting for receipt …
Verify it yourself — don’t take our word.
The quickest check needs nothing but a terminal: hash any page and compare it to the receipt.
curl -s https://argusdynamics.tech/ | sha256sum
curl -s https://argusdynamics.tech/proof/receipt.json
Your browser also runs a live spot-check on this visit (panel at left): it fetches the homepage, hashes the actual bytes with WebCrypto SHA-256, and compares against the receipt entry — a real check, in your hands, on your machine.
What this proves — and what it doesn’t. The receipt proves the served site matches the attested build, byte for byte, and that a live run of the argus-evidence spine produced and verified it. It does not authenticate the domain: receipt and pages come from the same origin, so a compromised or cloned origin could re-sign its own copy. The signing key is ephemeral per build — an integrity seal, not a long-term publisher identity. A pinned release key, distributed out-of-band, is a separate key ceremony, and we will say so plainly when it ships. Evidence over theater, always.
The same spine, for your systems
Want your evidence to hold up like this?
Signed inference receipts, tamper-evident audit logs, verifiable pipelines — the machinery attesting this page is the product. If your work needs evidence that survives scrutiny, talk to us.
Start a conversation → // signed receipts // tamper-evident logs // verify offline