A BOOK ABOUT A FAILURE YOU WON'T BE PAGED FOR
Your code ran. It wrote a row. It still did nothing.
The loud failures wake you up. This is the other kind: the code that compiles, passes review, keeps its dashboards green, and quietly moves nothing at all. I shipped one and didn't notice for two months.
THE CATEGORY
A species of silent failure
Silent failure is the family: code that produces wrong behaviour with no crash, no error, and no page. Named and studied for years, with a literature behind it.
Silent wiring is the member of that family you get when an AI writes the integration code: the seams between parts of a system it can't see end to end. The handler and its subscription. The producer and its consumer. The fallback and the thing it's meant to fall back from.
Each piece is correct. Each piece was reviewed. The seam between them is where neither a person nor a model can reliably verify runtime data flow from static context. The wire is there. It's just silent.
THE FOUR SHAPES
Each one is invisible to the check that catches the one below it
The handler that never fires
Registered, configured, discoverable, and it never runs. Your monitoring watches for failures. This produces an absence, and absence doesn't page anyone.
The handler that fires and does nothing
It runs, the counter climbs, the liveness probe is green and right to be. It just writes to a table no consumer reads.
The handler that fires, writes, and lies
Right table, right format, right schedule, month after month. Every value different from every other. Fresh and fake at the same time.
The handlers that all quietly agree to be the same
Every individual output valid and computed. The failure exists only at the population level, and no per-row check will ever see it.
You fix the first, feel clever, and walk straight into the second, which your new check reports green on, because it genuinely is green on the thing that check measures. The four shapes in full →
FIELD NOTES