Silence accepted as proof of absence

What goes wrong

Something happens, but nothing is emitted when it does, so the only trace of the event is an unchanged record. A reader then treats the empty result as evidence that the event never occurred, and relies on a channel that was never wired to report it. The quieter the reading looks, the more confident the wrong conclusion becomes.

Example

A background step stops running entirely; no alert fires, because every alert in that area is driven by failures the step itself would have reported, and the quiet page is read as a healthy week.

Not to be confused with

Not Probe Failure Reads As No, where a check runs and its failure is misread as a negative answer; here nothing reports at all, and the gap itself is taken as the answer.

Discovered by

@sks24git GitHub

Field notes · 10

@sks24git2026-11-05beat 1 review round

A change started exporting each item's history to users, but one admin action still changed items without logging. The export then shows a history that stops short of the item's real state.

Log every writer once users can read the log. A gap reads as a lie.
Name repeated buttons by their row. Identical labels let screen-reader users act on the wrong item.

@sks24git2026-11-04beat 2 review rounds

A sweep sets a flag when its scan hits the row limit, but the log line that prints it fires only when some row was due. When the oldest rows are all stuck, the scan fills, nothing is due, and the starvation never shows.

Report a saturation flag on its own line. Gating it on other counts hides it in the one case it exists for.

@sks24git2026-10-30beat 2 review rounds

To stop a counter from moving while a job waited in line, we skipped the item until the job started. Some jobs never start, so the item was skipped forever and its close and alarm paths went dead.

Give every wait a way out. A skip with no age limit turns a rare state into a silent stall.
Test the guard on the second pass. Old fields often survive an upsert.

@sks24git2026-10-30beat 1 review round

A fix stopped a false stuck alarm by skipping every item that waits for an answer, with no age limit and no other alarm in its place. A question nobody answers then waits forever, and no check ever reports it.

When you mute one alarm, name the alarm that still fires. Muting without a fallback turns noise into silence.
Bound every skip by age or state. A skip with no end hides real stalls.

@sks24git2026-10-28

A spec armed an alarm on a three-hour zero window but judged it on single zero hours with a healthy forecast. By construction the alarm could never fire in time, so the acceptance test failed before any code existed.

Define the alarm and its acceptance on the same event. A criterion the mechanism cannot satisfy fails every implementation.

@sks24git2026-10-26beat 1 review round

A recorder marked a prompt as answered only via one input path, while two other paths answered it silently. Every record showed the prompt still open and text sent before any button, and the only test could not fail.

Mark state at the effect, not at one caller. Every path that resolves a prompt must record it.
A test that passes with the assignment deleted is not a test. Mutate it before you trust it.

@sks24git2026-10-25

A watchdog that flags stalled work skips anything whose checks still read "pending", with no age limit. A check that never reports keeps the stall invisible forever, the one case the watchdog exists for.

Every "still in progress" exemption gets a clock. Without one it becomes a permanent blind spot.
Test the exemption's expiry, not only its start. The old-and-pending case is the real one.

@sks24git2026-10-17beat 2 review rounds

A design classifies results by rerunning the inner engine, but an outer layer adds its own findings after the engine returns. Each kind that only the outer layer reports goes missing, so its defects never show up.

Classify the output users see, not a rerun of one layer. Each layer adds its own facts.
Stop after three rounds of new findings. Ship the part that holds and restart the rest from the cause.

@sks24git2026-09-10beat 4 review rounds

Every other site logging a degraded read printed a shared token; this one printed the setting name and value only. A search for the token found each disarmed setting except the one on the money path.

Log the shared token, not only a readable sentence. A message outside the vocabulary is invisible to the search hunting it.
a search tool your own token before shipping the line.

@sks24git2026-09-10

Retired endpoints were replaced by a status code and nothing else, while the older tombstones beside them log and count each call. The next step drops the table on traffic evidence nobody collects.

A tombstone that does not count its callers cannot authorise the deletion it precedes. Log the call you expect never to happen.