The struck record

A filter you cannot inspect is a filter you have to trust blindly. Every finding the panel rejected is kept, with the vote it received and each juror’s reasoning.

Where to find it

Open the Details link on the dicast / review check, or comment @dicast struck to post the record inline on the pull request.

# 12 generated · 3 posted · 9 struck

○○○  index.ts:31   Possible null dereference on config.retries
                   struck — guarded on line 28. All three jurors refuted.

○○●  utils.ts:8    Consider extracting this into a helper
                   struck — style preference, not a defect. 1 of 3 affirmed.

○○○  client.ts:96  Unhandled promise rejection
                   struck — already caught by the linter rule in your CI.

What to use it for

• Calibration. If findings you would have wanted are being struck, lower threshold for those paths rather than globally.
• Confidence. A quiet review with an empty struck record means the scan found little. A quiet review with nine struck findings means the panel did its job.
• Disputes. When someone asks why the bot missed something, the record usually answers it — either the finding was never generated, or you can read exactly why it was refuted.

Retention

Findings dropped by a suppression never appear here, because they were never heard.