Skip to content
BrowseReject Graveyard
Analytics module · as of

Reject graveyard: signals killed by the leak-free gate

A REJECT/DEFER is honest market-efficiency evidence, not a failure. No $/edge/ROI claim.
View full size ↗
confirmednull (a finding)not testabledescriptivepending
Reject Graveyard
Chart: Reject Graveyard -- A REJECT/DEFER is honest market-efficiency evidence, not a failure. No $/edge/ROI claim.
scripts/platformkit/analytics_showcase/out/reject_graveyard.json

What it means

The ledger has logged 804 total verdict rows across all reruns; 628 of them are rejects and just 95 signals ever earned a SHIP. The single largest reason for rejection (510 rows) was the as-of reclaim sweep, signals that looked promising until leakage was removed and then died.

Caveats & confounds

The 804 total rows include the same signal retested many times plus rows whose latest verdict later flipped to SHIP, so raw counts overstate the number of distinct dead signals (68 distinct remain).

Ask Scout about this
What is the reject graveyard?What are the most common reasons a signal gets rejected?How many signals have shipped versus been rejected?Ask anything →