Verification is a sequence of distinct checks with recorded outcomes. A checker must state what it verified and which trust sources it relied on. A single verified badge should not conceal whether identity, integrity, execution environment or business quality was evaluated.
- Validate the protocol version, field set, types and size limits. Reject ambiguous encodings and unsupported profiles.
- Resolve tenant, task and attempt. Check the coordinator's recorded delivery admission against the lease and generation valid at that point; reject cross-task or stale submissions.
- Resolve the trusted key record and verify the complete signature profile, including revocation and replay rules.
- Retrieve authorized input and output bytes and recompute the declared digests. Record unavailable evidence separately from a mismatch.
- Evaluate the frozen acceptance profile: deterministic replay, model evaluation, customer approval or another explicitly defined method.
- Persist an acceptance record with the checker identity, rule version, code digest, outcome, reasons and evidence references. Send only the appropriate accounting eligibility event.
Swipe or scroll to view all columns →
| Check | What it establishes | What remains outside scope |
|---|---|---|
| Digest comparison | Consistency with specified bytes | Publisher or executor identity |
| Registered-key signature | An attributable signed statement | Truth of every execution claim |
| Deterministic replay | Conformance to a fixed algorithm | Arbitrary model inference or GPU use |
| Model evaluation | Performance on a declared evaluation method | Universal output correctness |
| Environment attestation | Properties covered by the attestation trust model | Business suitability of the output |
Missing evidence and disputes#
VERIFY-01 An unavailable output, registry or evaluation dataset cannot yield a pass. Retain a pending decision until the defined deadline, then follow the failure or dispute policy. A successful HTTP response or well-formed hash string is not a completed integrity check.
If the same actor can replace the input, output, receipt and manifest, self-consistency alone provides no independent trust anchor. Pin the original task and approved release through an authenticated channel. The same limitation applies to the local reference checksum file.