Locally verified means your machine ran the checks. Mantyl Verified means Mantyl’s own infrastructure independently re-executed them and staked a signature on the result. This page explains exactly what happens, because a trust mark you cannot inspect is just a badge. The feature is in beta and free while Mantyl is in alpha; paid credits arrive later.
The command refuses a dirty working tree, because an accreditation binds a commit and an uncommitted tree is not a commit. It shows you the file count and size before anything uploads, and only git-tracked files are ever bundled: local state, ignored files and secret env files never make the list.
The verification worker downloads your bundle into an ephemeral working copy, first proving the bundle digest matches what the CLI uploaded. It then recomputes the passport’s file manifest against the extracted source, which proves the uploaded code is byte-for-byte the code the passport describes. The recorded verification plan re-executes in an isolated Docker sandbox with network cut after dependency install, exactly as your own machine runs it. Only when every check reproduces as passed does the worker sign. The working copy is destroyed after every run, pass or fail, and the uploaded bundle is deleted the moment the job completes.
The accreditation is an Ed25519 signature over a canonical record containing the passport digest, the evidence digest, the commit, the policy identifier and version, the verifier version and the verification time. Change any of those and the signature fails. Move the accreditation to a different passport and it fails with that exact reason. The hosted passport page re-verifies the signature every time it renders, so a mark that stops verifying simply disappears rather than lingering.
The signing public key is published at /api/signing-key. Any Ed25519 implementation can verify an accreditation offline: the signed bytes are the canonical JSON of the record, and the key never changes without notice in the changelog. The private key exists only on the verification worker, never in the CLI, never in the web app.
An accreditation proves the recorded checks passed on independent infrastructure against exactly the claimed source at exactly the claimed commit. It does not prove the software is secure, correct or fit for purpose, and the passport itself says so. Evidence, not certification, at every layer.