Sample Proof Artifact
Example format only. This uses test data to show how a sprint records state, gates, execution, evidence, and caveats without leaking private accounts or pretending blocked routes succeeded.
Run Summary
Workflow
Verify a public product page and payment CTA before sending a buyer link.
Allowed Surface
Public landing page, seller-controlled checkout link, and local proof file. No customer data.
Decision
Send the link only if the CTA loads, points to the expected payment route, and no private markers are present.
Evidence Ledger
| Check | Evidence | Status |
|---|---|---|
| Fresh page load | Browser loaded the public URL and title matched the expected offer name. | Pass |
| CTA route | Primary button resolved to the expected deposit checkout URL. | Pass |
| Private marker scan | Rendered body checked for local paths, secrets, private email, local-only URLs, and obvious token markers. | Pass |
| Outbound gate | One buyer-intent recipient only. No attachments, no repeated follow-up, no benchmark or revenue claim. | Human approval if public send |
| Blocked route handling | If the public page or checkout fails to load, the proof says blocked and no link is sent. | Stop on failure |
Handoff
Next action: send the verified link only to a specific interested buyer. Remaining caveat: this proof confirms route readiness, not purchase intent, checkout completion, buyer budget, or guaranteed revenue.
Want this kind of proof packet built for your workflow? Use a written mini-audit or support the sample if it saved you time.