What the corpus proves — and how
The verified surface today — across error classes, SDKs and the curated lots — and, below it, the machine proof behind every record. Every thin cell is a scout work-order; every record is re-provable by anyone.
Proven, not scraped
A Verified Trap Instance is a claim that's been mechanically proven and can be re-proven by anyone. Two things make that true — a generalized oracle, and a fail-closed ingest funnel. It's why the reproduced rate above is 100%.
Four backends, cheapest first
The rule must fail on the vulnerable fixture and pass on the fixed one. Whichever backend can prove that wins; corroborating backends are recorded alongside it.
AST pattern match against the vulnerable shape. Offline, no code executed — the default.
Type-checks the candidate against the pinned SDK. Catches hallucinated or moved APIs with zero execution.
Runs a vetted contract test in a sandbox. A behavioral proof for bugs with no static shape.
Runs the candidate against a golden input→output table. Catches wrong-constant / logic bugs.
Three gates, all fail-closed
Contributed records clear each gate in order. Any rejection stops the record — nothing slips through silently.
Every file runs through Keyguard. One key refuses the whole submission — fail-closed.
The oracle re-proves the finding. This is the anti-poisoning gate: non-reproducing data can't land.
Contributor-grant-v1 stamped, scope verified. Owned and contributed lots stay physically separate.
Every record ships its own re-runnable receipt. No secret answer key — the same procedure returns the same color for anyone.