---
name: silence-on-the-healthy-path-is-not-evidence-of-a-stall
description: "A repeated log line whose repeat is SUPPRESSED by success cannot date a stall; one line plus silence is the shape of health, not of a wedge."
metadata: 
  node_type: memory
  type: feedback
  originSessionId: d02b1658-b94a-4d51-b1e2-d4f28251bdfe
  modified: 2026-08-18T07:15:11.056Z
---

Before inferring a stall from "the line printed once and never again", check whether the emit site
repeats on the HEALTHY path. If success suppresses the repeat, silence is what working looks like
and the observation dates nothing.

Measured 2026-08-18, releases#188 (run 32108557362 against job 95597031932). A whole RCA — three
eliminated candidates, a named surviving mechanism, two approved build lanes — rested on: *one
`PUMP_DIAL_SUBMIT` in 900s means no round ever closed, because a closed round would submit again.*
The instrumented re-run emits **exactly one `PUMP_DIAL_SUBMIT`** and closed **709 rounds** under it.
The dial connected at `mono_ms=27`, the conn was cached in `conns`, and a peer holding a live conn
is never re-dialed. The second line was missing because the first one WORKED.

The whole visible token set matched the original job — 1 submit, 1 `SELF_ADDR_REBIND`, 2
`PUMP_IPC_READER: spawned`, no `PUMP_PEER_FAIL`, no reader exit, ~920s, same failing rung. So the
evidence never separated wedged from healthy; it was equally the signature of both, and the RCA read
one of the two into it.

**Why:** a re-emitting line gets used as a clock. Once you are treating it as a clock, its absence
reads as time-not-passing rather than as state-changed — and the retry path that would re-emit it is
exactly the path that success removes. The trap tightens when the surrounding facts are all
ABSENCES too ([[absence-needs-sibling-probe]]): several silent observations agreeing feels like
convergence when they may share one cause.

**How to apply:** for any "printed once, then nothing" claim, open the emit site and ask what
suppresses the second print. If a success path does, the claim is dead on the spot — say so before
proposing a mechanism. Then instrument the SILENT arm: the loud sibling being absent proves nothing
when its counterpart emits nothing at all (`PRESENCE_CONNECTED` was silent while only
`PRESENCE_DIAL_FAILED` logged, so "no `PUMP_PEER_FAIL`" could not distinguish "connected fine" from
"no outcome arrived"). Pre-register the readings before the log exists.

Related: [[start-event-is-not-proof-nothing-ran]] (its mirror — a start line is not proof of
absence, this is silence misread as absence of progress), [[one-sample-is-not-a-negative]],
[[log-token-names-its-population-not-the-subsystem]], [[intermittent-green-is-zero-information]],
[[ruling-rests-on-a-premise]].