Receipts, explained.
Short, procurement‑friendly explainers for how MVG evidence works: DSSE pointers, fail‑closed semantics, and offline verification.
DSSE in 60 seconds
What a DSSE pointer is, why it is review‑friendly, and how to open it without surprises.
PASS / FAIL / HOLD
Why HOLD is the safest default for uncertainty, and how it prevents silent policy drift.
Offline verification
How a reviewer can replay verification locally under pinned versions — no uploads, no network.
Where to start
If you only open one link, start with the ticket‑pack DSSE pointer. It connects the pack, proofs, and expected outputs.
Receipts — quick answers
These answers are written for human review and stable snippets. Search feature eligibility varies; treat rich results as optional, not an expectation.
What is a DSSE pointer?
DSSE (Dead Simple Signing Envelope) is a signed envelope format. MVG uses DSSE statements to publish audit-friendly evidence pointers: what to attach to a ticket, what to verify, and what outputs to expect.
What do PASS, FAIL, and HOLD mean?
PASS means the evidence and policy checks verify. FAIL means a check deterministically fails. HOLD means evidence is missing, unverifiable, or policy is uncertain; by design, HOLD is fail-closed and requires human review or corrected artifacts.
What does offline-verifiable mean?
Offline-verifiable means a reviewer can replay verification locally without network calls or uploads, under pinned versions. This reduces supply-chain risk and makes audits reproducible.