- operation
- registered name
- engine
- name + version
- inputHash
- source identity
- outputHash
- result identity
- losses
- declared ledger
Evidence
Inspect the proof behind the artifact.
Resolve what ran, which bytes entered and left, what changed, what failed, and which decision allowed the exact result to move forward.
contract 1.0.0Receipt anatomy
Every claim needs a resolvable field.
This is the evidence schema Runstamp aims to produce—not a fictional run, customer, approval, or benchmark result.
EvidenceWhat it establishesWhere it resolves
Input and output identityExact source and result bytesHashes in the result evidence
Operation contractRegistered name, engine, and contract versionRegistry descriptor and receipt
Loss and diagnosticsKnown fidelity changes and actionable issuesTyped result envelope
ValidationThe checks that ran and their exact outcomeValidator evidence when available
DecisionThe policy or human boundary behind releaseBound review evidence when required
Prove the gate can fail.
A passing fixture is incomplete evidence unless a deliberately invalid control is rejected for the expected reason.
Keep date and scope attached.
Benchmarks and conformance artifacts publish their environment, limitations, and dated result instead of becoming timeless claims.