We scanned our own revenue agent first.
This was unpaid internal dogfood. It is not revenue, a customer result, or proof of market demand.
What the scan caught
Aggregate history was mislabeled as current-offer evidence
Seventy-two historical direct emails produced zero replies, but the ledger had no campaign, offer, version or channel breakdown. The system was correctly cautious and incorrectly specific. It now closes first-touch direct email without pretending the new product had 72 failed attempts.
Message delivery was not bound to exact content
A Gmail message ID proves provider acceptance, not which offer body was sent. Future sends now record hashes for the raw message and body plus campaign and offer version.
The buyer could not inspect a completed example
This page and its signed machine-readable delivery close that proof gap without exposing private messages or credentials.
Evidence map
The live offer and Stripe checkout are supported by serving-path and Stripe readback receipts. Zero payment and zero qualified replies are supported by Stripe and Gmail scans. The claim that the new product failed after 72 sends is unsupported because the source lacks campaign attribution.
Verify it
Download the full redacted delivery + signed action receipt. Verify it with verify_action_receipt at the Corbelworks MCP endpoint using the published Ed25519 key.