How we build the registry

Every incident in this registry obeys five rules:

1. A public source URL is required. No source, no row. Period. We link to vendor forums, named reporters, affected-user posts, and news outlets — primary sources where possible, secondary where validated.
2. Amounts are as reported. "$72,000" means the source reported $72,000. We never round up, never annotate with "estimated," and never backfill a missing dollar figure. Undisclosed amounts carry amount_usd: null and verified: false.
3. Dates are as reported. We record the incident date (or report date, if the incident date is unclear) as the source states it. If only a year is known, we record the year and mark the record as partially verified.
4. No surveys. No incidence rates. We do not publish claims like "X% of teams experience runaway spend." Vague rates are how dataset trust dies. If we cannot source each row individually, we do not ship an aggregate.
5. Verified flag means everything is confirmed. A record is verified: true only when the amount, date, cause, and provider are all confirmed by the source. If any field is approximate, verified: false — so downstream users can filter confidently.

1. We find a credible public report. Vendor community forums (OpenAI, GCP), Reddit megathreads (r/LangChain, r/googlecloud), named tech journalism (The Register, AlphaSignal), and affected-user posts (LinkedIn, dev.to) are all acceptable. Anonymous forum posts without supporting detail are not.
2. We normalize the fields. Amount → amount_usd (float or null), date → ISO month, cause → one of the five normalized categories (retry loop, prompt injection, unattended session, leaked credential, failed cap), provider → normalized vendor name.
3. We map the cause to a rule. Each incident is tagged with the sipi.bot rule type that would have stopped it — per-transaction cap, daily total, velocity limit, merchant allowlist, category rule, or time-of-day. This is the conversion mechanic: it turns fear into a checklist.
4. We regenerate. Adding an incident to data/incidents.py triggers a rebuild of every artifact: all format files (JSON/CSV/JSONL/min), all hub pages, all OG cards, all sitemaps, and IndexNow pings. One source of truth.

Yes. Open a PR against the dataset repo with:

• A public source URL (required)
• The amount as reported (or "undisclosed")
• The date as reported
• A neutral, factual summary — no marketing language

Do not submit unsourced incidents, rounded-up amounts, or invented statistics. They will be rejected. The verified flag lets you submit a well-sourced report even if some details remain approximate.