Recompute every hash we publish, and check we are not lying
Re-verify every sealed settlement on the FlashyOS network: fetch the public feed, recompute each sha256, exit 0 only if the books check out. Verify, don't trust — including us.
Every settled cross-org collaboration is published as a frozen canonical payload plus its sha256. This fetches the public feed, recomputes each hash, and exits 0 only if the whole record checks out. It is about two hundred lines, and it is the reason you do not have to take our word for anything. It also seals and verifies action/1 — the claim one step of work leaves (actor, authority, input, tool, output) — through the same canonicalisation, and re-derives the output from the recorded input to refuse a mismatch.
FlashyOS publishes every settled cross-org collaboration as a frozen canonical payload plus its sha256. `npx @flashyos/verify` fetches the public settlement feed, recomputes each hash, and exits 0 only if the whole record checks out. It is about two hundred lines.
The one rule is `sha256(settlementPayload) === settlementHash`. Payloads are JSON with keys sorted at every level, frozen at resolution time and never recomputed from live rows.
It also refuses a payload that is self-consistent but not in canonical form — the exact shape a re-serialise-and-re-hash forgery would take. Receipts, settlements and `shipped/1` entries hash through the same canonicalisation, and `packages/verify` pins the verifier against the sealer so the two cannot diverge.
Installing it puts this command on your path — read from the package’s own manifest, so this list cannot drift from what you actually get.
flashy-verifyReceipts, settlements and shipped/1 entries all hash through one canonicalisation, and packages/verify pins the verifier against the sealer in test, so a change to how bytes are sealed cannot silently pass the checker. The verifier is small enough to read end to end. Verify it yourself: run `npx @flashyos/verify` against the live public feed at flashynetwork.com/settlements.
Apache-2.0, read from the package’s own manifest. Embed it in anything, including closed software — that is what makes a spec adoptable and a verifier worth running. FlashyOS’s server side is AGPL-3.0-only instead, and a test in the monorepo asserts the direction between them: AGPL code may consume this, this may never consume AGPL code.