COSMO Execution-Case Verifier

A public, offline, single-file verifier for COSMO execution-case evidence bundles.

In plain words: this is a small program you can download and run on your own computer. You give it a folder of evidence files from a COSMO run, and it answers ACCEPT or REJECT: do the records in that folder agree with each other and with the rules that were signed beforehand? It needs no internet connection.

What it does not do: it is written by COSMO, not by a third party, and it checks that the records are consistent. It cannot tell whether the outside world matches them. Evidence folders are listed under /evidence/; the proofs are explained on the proof overview.

Run

node cosmo-verify.mjs <bundle-dir>     # verify a bundle
node cosmo-verify.mjs --show-trust     # print the embedded trust profile
node cosmo-verify.mjs --version        # version, trust hash, source sha3

Node ≥ 18. No npm packages, no network, no environment reads. Exit codes: 0 ACCEPT, 1 REJECT (the last result names the criterion K/S/T/P/M/V/J/E/D/O), 2 ERROR.

What ACCEPT means

The bundle satisfies all ten criteria under exactly the published COSMO trust profile below. This is a separate offline verification of internal consistency — not an independent third-party attestation. There is no trust override in the normal mode.

The evidence bundles under /evidence/ can be checked with this file. Point the verifier at a bundle directory; a flat published bundle is staged into the case layout deterministically, without changing any bytes.

Verify this file before trusting it

openssl dgst -sha3-256 cosmo-verify.mjs
# must equal distributable.sha3 in PROVENANCE.json (and --version source_sha3)

PROVENANCE.json also pins the build inputs and vendored package versions, so the file can be rebuilt from source and reproduced byte-for-byte.

Second verifier: SupraFX maker case bundles

Maker windows on SupraFX (evidence folders named suprafx-maker-*) use a different bundle layout, schema cosmo.killer-demo.maker-case-bundle.v1. They are checked by a separate single-file program, cosmo-verify-maker.mjs, with its own PROVENANCE-maker.json. It runs the same 14 checks (MB1-MB14) as the repository verifier: 48 checks on a bundle with a fill, 29 on a declined case, 52 on a Robinhood-demo fill bundle with both on-chain settlement legs (MB13) and 58 with a customer mandate (MB14). cosmo-verify.mjs above is unchanged by this addition.

node cosmo-verify-maker.mjs <case-dir>     # verify one maker case bundle (cases/<id>/ under the evidence folder)
node cosmo-verify-maker.mjs --show-trust   # embedded pins (policy, gates, proposer, authorizer, registers)
node cosmo-verify-maker.mjs --version      # version, trust hash, source sha3
openssl dgst -sha3-256 cosmo-verify-maker.mjs   # must equal distributable.sha3 in PROVENANCE-maker.json