"Add a cancellation flow that keeps the customer's data for 30 days." The founder's own words, preserved as the anchor for everything below.
Representative Receipt
What a Proof Receipt records.
The example below is a synthetic receipt from the demonstrated Founder-to-Proof journey. It uses synthetic data and generic model labels. Proof Receipts are a demonstrated capability, not yet running on production accounts.
Who approved, and the exact versioned action they approved. Approval binds to that version. A revised plan needs a new approval.
The expert functions consulted, under generic labels. Positions and dissent are retained in the protected record.
The recommendation that won, and why: evidence, risks, tradeoffs, and confidence at decision time.
Every produced artifact is listed with a content hash, so you can verify later that what shipped is what was recorded.
The tests and checks that ran, and their results. Not a summary sentence. The actual outcomes.
The security and quality evaluation of the finished work. In the demonstrated journey, a blocked verdict means the work does not ship.
What the job actually cost to produce, recorded on the receipt rather than estimated after the fact.
The final state of the job: completed, blocked, or held, with the reason attached.
What the work does not cover. Honest receipts record the edges, not just the wins.
Synthetic example
All field values shown or described on this page come from synthetic demonstration data. No customer data appears here.
Evidence, not a completion message.
See how the receipt fits the full journey from direction to proof.