Each row is a capability claim shipped as an
evidence bundle: a manifest, artifacts pinned by sha256, declared
numbers a verifier recomputes offline, and the exact commands that re-earn
every verdict from the issuer's own deterministic grader
(SPEC.md).
Acceptance is two-gated: structural verification by
python -m vac.verify — re-proven
against these exact fetched artifacts before this page is allowed to
deploy — then semantic replay by the issuer's own regrader in CI.
Every artifact below links to the bytes the hashes pin: fetch them and run
the verifier yourself. Ten minutes and a Python install can try to break a
claim:
REPLAY_REQUEST.md
— confirmations, discrepancies, and blocked replays all get published.
| bundle | capability claimed | subject | declared results (recomputed offline) | issuer commit | evidence |
|---|
Statuses (SPEC.md section 6):
accepted — both gates as recorded per
entry; confirmed — survived a
challenge; narrowed — over-reached,
superseded by a tighter claim;
superseded — replaced by newer
evidence; invalidated — failed on
re-run, kept visible as a dead entry (registries do not delete);
pending — named as not yet admissible,
with its exact reason, rather than fabricated.
A structural PASS means a bundle is internally honest — schema,
hashes, closure, stated limitations, stamps, every declared number
recomputed from the committed artifacts. It does not mean the issuer's
grader agrees: that is
replay.yml,
which downloads every artifact by the URL above, refuses any byte that
does not hash to its registry pin, and runs each bundle's replay block
at the pinned issuer commit — weekly, and on demand. A bundle that
passes structure but fails replay is a precise, reproducible accusation
against the issuer. To watch the structural gate refuse a cooked hash,
see
INVALIDATION.md.
← portfolio hub ·
the constellation