Verify this build

Re-hashes a sample of the assets served to your browser and verifies the release manifest's Ed25519 signature against a hard-pinned Aarmos key. Runs entirely on-device. Does not block execution — this is a truthful verdict, nothing more.

Checking…

Release gates

Blackout profiles. CI runs the governance path with Aarmatix hosts, and then all network egress, black-holed. Policy evaluation, signing, and local verification must complete unchanged; a release that needs the network to govern does not ship.
Clean-room portability. The open verifier core must resolve and verify a receipt with no network and no application code present.
Build-provenance sidecar. Receipts may be accompanied by a detached <receipt>.provenance.json recording build identity only. It is optional: remove it and the receipt still verifies. See provenance.

CLI equivalent: aarmos verify release https://aarmos.io

The pinned public key ships inside the app bundle. A fork can serve a valid manifest for their own build, but cannot produce one that verifies against the Aarmos key.