docs / proof
Prompt to paid order.
This is the public proof that matters right now. A generated store can go live, take a payment through Stripe Checkout, produce receipt evidence, and record merchant webhook delivery.
Shipped flow
1. Prompt creates a generated store.
2. Owner completes publish and Stripe onboarding.
3. Buyer adds to cart and reaches checkout.
4. Stripe Checkout completes and records a paid order.
5. Receipt page and evidence JSON render the order proof.
6. Outbound merchant webhook delivery is recorded and verifiable.
What this proves
The product is beyond fake-door status.
A generated store can become a live transacting store.
Paid orders, receipt evidence, and merchant webhook proof all live in one runtime.
The seller-side runtime works with real Stripe checkout and real order records.
What this does not prove yet
SDK publication or CLI packaging.
Provider provisioning or store creation through Stripe Projects.
ACS catalog registration or broader agent-channel distribution.
x402 or other machine-payment rails in production.
Operator path
The canonical operator procedure lives in docs/V1_0_PUBLIC_PROOF_RUNBOOK.md.
The proof chain is straightforward: prompt, generated store, publish/onboarding, storefront cart, Stripe Checkout, paid order, receipt evidence, and merchant webhook delivery.
Public proof surfaces include /live for the feed and /orders/{id}/evidence for structured evidence on a known order.