| Verifier | Recompute depth | Canonical envelope | Independent admission | Anchor existence | Pre-outcome precedence | Action chain | Certified |
|---|---|---|---|---|---|---|---|
| agentoracle · live ed25519-jcs | ● terminal | ✓ pass | ✓ pass 2 signers verified | ✓ pass via on-chain (Arbitrum) | ✓ pass via on-chain (Arbitrum) | — n/a | CERTIFIED |
| invinoveritas · live nostr-event | ● terminal | ✓ pass | ✓ pass embedded | ✓ pass via Bitcoin OTS | ✓ pass via Bitcoin OTS | — n/a | CERTIFIED |
| safeagent · live bip340-schnorr | ◐ bounded · anchor | ✓ pass | ✓ pass embedded | ⏳ pending | ⏳ pending | — n/a | not yet |
| moyan-pmi · live ed25519-jcs | — | endpoint unreachable this run | not yet | ||||
/governance endpoint). For a graded trace dump: CERTIFIED = the verdict survives the row’s own recorded jitter (|score−threshold| > jitter_margin); PARTIAL = inside the band; DEPTH-0 = fault / non-recomputable. For a deterministic vector: every linked identifier either recomputes byte-for-byte from its own preimage or it doesn’t — no jitter concept applies. A grade against a pinned commit stays true forever, but the project can move past it — so every run (1) checks how far the default branch has drifted from the pin and (2) where we have a registered reverify recipe, re-pulls evidence and recomputes it fresh — a full re-derivation for a small artifact (ibex), a cheap byte-range sample for a large one (Correctover’s 20k-row dump is canary-sampled, not fully re-graded every cycle — a full re-grade is heavier and could silently flip a published % without a human look, so the sample answers "is this still alive and consistent," not "re-publish the percentage"). Drift is a signal, not a verdict; neither check ever silently changes a published grade. Recomputed by us, reproducible by anyone at the pinned commit.| Benchmark | Recompute-depth grade | Pinned commit | Freshness |
|---|---|---|---|
| Correctover v1.1.0 graded trace dump · 20071 rows · recipe examples/benchmark-grade/grade_traces.py | 26.5% certified · 52.8% partial · 20.7% depth-0 | a27999b333 | drift unknown reverify: unreachable checked 2026-08-15 |
| ibex-agent-verification verifiable-action-chain v1 deterministic vector · 1 record(s) linked · recipe conformance/verifiable-action-chain-v1.json + tests/test_full_chain_vector.py | RECOMPUTES 4/4 action_id → decision_id → execution_outcome_id → audit_record_id | 814d670c88 | main +3 reverify: pass checked 2026-08-15 |
| Correctover correctover-crewai verify_proof_package plaintext-consistency deterministic vector · 1 record(s) linked · recipe pip install correctover-crewai; RecomputeEngine().verify_proof_package(pkg) adversarial test (see babyblueviper1/preaction-governance-conformance examples/plaintext-verdict-consistency) | FIXED + REGRESSION-COVERED proof_hash → expected_verdict → expected_confidence | a2bc2fdf75 | drift unknown reverify: unreachable checked 2026-08-15 |
| trustless-ai/recompute-kit aggregate-budget-v0 deterministic vector · 7 record(s) linked · recipe conformance/aggregate-budget-v0/{aggregate-budget-v0.vectors.json,gate.ts,suite.json} — bun gate.ts | RECOMPUTES 7/7, TAMPER DISAGREES 5/7 (as claimed) rootId → periodIndex → admittedSum → conserves | b672bbfa2f | main +50 reverify: pass checked 2026-08-15 |
| google-agentic-commerce/AP2 open_mandate_hash v0 (seeded by AlgoVoi) deterministic vector · 7 record(s) linked · recipe vectors/ap2_omh_v0/ap2-omh-v0.json -- SHA-256(JCS_RFC8785(mandate_body)), any conformant RFC 8785 implementation | RECOMPUTES 7/7, PAIR INVARIANTS 4/4 (as claimed) vector_id → expected_jcs_bytes_b64 → expected_open_mandate_hash | 3a4b516ef9 | main +2 reverify: pass checked 2026-08-15 |
terminal recomputes through an external anchor on an independent clock;
bounded · anchor recomputes independent admission but the anchor is not yet confirmed;
bounded · admission recomputes the envelope but admission rests on the producer;
attested means the envelope does not recompute from its own bytes. Rows are ordered by
this tier, then alphabetically — both re-derivable from the suite states, so the order is not our
opinion (the alphabetical tiebreak is why we are not first within a tier).embedded when the verification key is
in the fixture, or k/N signers verified for a multi-signer claim, so a row never implies it
is fully recomputable from the fixture when only some signers are. Anchor existence: the commitment is externally confirmed by the declared
mechanism (it provably exists). Pre-outcome precedence: the accepted anchor point provably
precedes the terminal outcome — a confirmed-but-backfilled stamp proves existence, not ordering,
so existence and precedence are reported separately and existence can never pass as ordering.
Action chain: the terminal record joins back to the same proposed action (n/a where
an endpoint is pre-action only). pending is honest, not a failure.POST /conformance/{name}/certify-to-ledger (250 sats, Bearer auth)
lets a currently-certified verifier publish its live grade as a permanent, invinoveritas-signed
entry on the public /ledger — same Nostr broadcast +
Bitcoin OpenTimestamps anchor every other entry gets, so the record survives even if this page's grade
later changes or the live endpoint goes down. Labeled honestly as "certified as of this
measurement," never "currently certified." Callable only while certified: true here; a
re-call on an unchanged snapshot returns the existing entry instead of re-charging.[](https://api.babyblueviper.com/conformance)2026-08-15T02:20:09.751556+00:00.