What to send
- The observed agent action.
- The boundary it should have respected.
- The runtime context: framework, tool, workflow, or deployment shape.
- One artifact: log excerpt, trace id, receipt, screenshot, or public link.
What Shadow returns
- A public autopsy entry when the failure is broadly useful and safely redacted.
- A private failure diagnosis when the evidence is sensitive.
- A deterministic contract, receipt example, or proof card when the failure can be converted into a reusable control.
- A paid audit path only when the failure needs deeper hands-on work.
How the paid path works
- Free triage — send one failure; you get a diagnosis. No payment, no call required.
- $400 Failure Census — seven days of your agent logs/traces mapped to failure classes with receipts. Scope confirmed by email first, then invoiced directly (Stripe invoicing) — no checkout page, no card details over email.
- $2,000 Contract Install — deterministic claim-boundary contracts installed on one production workflow. Same invoice flow.
- $500/mo Governed Operations — ongoing runtime governance retainer.
Falsifier
If this surface produces no concrete submitted agent failure within 7 days of publication, the intake wedge failed and should be reworked or retired.