Evidence and Verification
Delivery Evidence is the claim-relevant material used to evaluate whether a Capability Execution met its Defined Claim. It lets the service prove delivery without exposing unrelated workflow logic or private data.
Evidence properties
Evidence handling balances four properties:
- Relevance: each evidence item maps to a claim criterion.
- Integrity: authorized reviewers can determine that evidence has not been silently substituted or altered.
- Availability: Verification and dispute review can access it when required.
- Confidentiality: unrelated workflow logic and private data remain undisclosed.
Each Capability can define its evidence formats, storage requirements, attestations, access controls, and confidentiality policy.
From execution to final result
An Execution Record identifies the purchase, Buyer, governing Capability version, result, and evidence references. Recording establishes that an execution occurred; it does not establish that the claim was met.
Initial Verification evaluates the Delivery Evidence against the Defined Claim and returns a provisional result in one of three states:
| Result | Next step |
|---|---|
| Claim met | Enters the three-day public Challenge Window as a provisional result. |
| Claim not met | Payment remains held and the execution enters Evidence Review. |
| Indeterminate | Payment remains held while missing, conflicting, or unusable evidence is reviewed. |
Buyer Acceptance on a provisional claim-met result settles Buyer payment under the transaction’s routing rules and waives the Buyer’s financial recourse. It does not prevent the Buyer from filing a protocol-level Challenge as another public participant. The execution becomes a Verified Delivery only when the public Challenge Window closes unchallenged, or Evidence Review and every applicable appeal period or proceeding close with the claim met.
Verification methods
Quantitative criteria may support deterministic checks, external events may require authenticated data, and complex qualitative work may require specialized evaluation or human review. The governing Capability defines the applicable method, data sources, reviewer requirements, and evidence-access rules.
Parameters and framework details are published before mainnet.
Capability History records every execution, provisional Verification Result, and final resolution. Verified Delivery History contains only protocol-final claim-met deliveries. See Reputation and Delivery History.