Evidence Report
Format specimen
What a filed attempt looks like when SDF has checked it. Every field below is invented for the layout. Nothing here shipped for a customer.
Objective
Add retry with backoff to the outbound webhook client, linked to the business goal “fewer dropped deliveries.”
Acceptance criteria, declared before the attempt
- Unit tests cover timeout, HTTP 429, and the success path.
- The diff does not add a secret or credential.
- The accepted change is bound to one code revision.
Route
The task is handed to an agent you already pay for. SDF does not sell that agent and does not resell its tokens. In this specimen the agent is named Example Agent so the slot is visible.
Independent checks
The agent cannot sign these. Each line is tied to the same revision as the verdict.
| Check | Result | Bound to |
|---|---|---|
| Tests named in the acceptance criteria | PASS | sample-c0ffee1 |
| Diff adds no new secret or credential | PASS | sample-c0ffee1 |
| Verdict revision is the submitted revision | PASS | sample-c0ffee1 |
Verdict
PASStied to revision sample-c0ffee1
A PASS on a real report means the independent checks held for that revision. This PASS is a picture of that sentence. It is not evidence that any real task passed.
Cost record
Tokens, time, and invoice cost are stored on the attempt so you can compute Cost per Accepted Outcome. This sample leaves the amounts blank. SDF prices are not set, and a mock must not invent a result.
- Agent-reported usage
- Recorded, not shown
- Attempt cost
- Filled from your own agent invoice
- Cost per Accepted Outcome
- The field you manage
- SDF price
- Not published
Decision Graph excerpt
- ObjectiveSpecimen task, linked to a stated goal
- AttemptSAMPLE-TOY-001
- EvidenceThree independent checks
- VerdictPASS at sample-c0ffee1
- CostDollars left blank on purpose