When a Safety Reviewer Rejected Everything and Still Passed Its Test

This is a submission for DEV's Summer Bug Smash: Smash Stories powered by Sentry.

ARGUS is a data-catalog governance swarm. Specialist agents find missing descriptions, untagged sensitive columns, broken lineage assumptions, and other metadata defects. An Arbiter reviews each proposed repair before anything can be written.

That last reviewer is supposed to be the safety boundary. It must reject unsupported claims without blocking repairs that the evidence actually supports.

One live sweep exposed a failure that looked exactly like diligence.

The Arbiter rejected 86 of 112 proposals. Among the rejected repairs were classifications such as:

When a Safety Reviewer Rejected Everything and Still Passed Its Test

Related reading

The HTTP 429 That Turned Seven Minutes Into Zero Work

Gotcha: chasing a bug that was never in my code

"Trust this file over the exit status": the note our test suite left itself —…

Tracing and Resolving a Critical Security Bug in Smart Contract Analysis

Nine green tests and a parser that never worked once

My Summer of Sleuthing: 373 Merged PRs and the Bugs That Taught Me Everything