Trust
Trust in Canopus is not a slogan. It is the set of Vela substrate records that let a reviewer inspect who ran what, which bytes were verified, which checks passed, and where the known attack surfaces still live.
Trust pages should expose gates and accepted artifacts as inspectable records, not decorative confidence labels.
attemptwork
An agent, capability, procedure, system, or human run with input material, declared output material, environment, disclosures, failure state, and cited artifacts.
checkgate
A schema, provenance, contradiction, benchmark, proof, or evaluation result over a reviewable change or release.
reviewgate
A human or authorized reviewer decision over a reviewable change, check, candidate gap, or contested finding.
eventaccepted
A signed, reviewable state transition that changes the Vela-backed frontier record.
evaluationaccepted
A content-addressed result with inputs, metric, runner, environment, timestamp, and linked finding or target.
releaseaccepted
A citation-ready bundle of source state, proof artifacts, mirrors, and known caveats.
attestation ledger
vaa_* envelopesCompute systems, prompts, capability calls, output hashes, and cited diff packs. These records pin provenance. They do not vouch for correctness.
inspect traces →
verifier chain
lean v4.29.1The public key, toolchain, verifier output hash, source anchors, and theorem records in one reviewable surface.
inspect verifier →
formal path
0 verifiedMachine-checked Lean declarations that pin substrate invariants and external math used by the protocol.
inspect theorems →
integrity model
0 undefendedKnown adversarial surfaces, current mitigations, and regression gates. This is reference evidence, not product copy.
inspect threat model →