--- name: a-stricter-meter-answers-a-confident-empty description: "readlink /proc/pid/exe reads \" (deleted)\" after a rebuild, so an exact-equality predicate reported ZERO matching processes over 24 already-measured ones" metadata: node_type: memory type: feedback originSessionId: 880d1285-2246-4429-9b5e-eb4331af141f modified: 2026-08-29T13:24:23.907Z --- Measured 2026-08-29 (todlando, kitsubito, W2/#238 reap). doyle authorized reaping 24 orphaned daemons **by predicate**: binary path == `/home/reavus/projects/spt-core/spt-core/target/debug/spt` AND `SPT_HOME=/tmp/.tmp*`. My census compared `readlink /proc//exe` for exact equality and answered **P1=0, P2=0 — "nothing to reap"** while 25 matching processes were resident. The tree had been REBUILT since those daemons started, so the kernel reports `/home/.../spt (deleted)`. The working predicate is `case "$exe" in "$B"|"$B (deleted)")`. Corrected census: 24/24 matched both predicates, zero spared; after the kill P1=0, P2=0 for real, port 5474 free. **Why:** the emptiness was manufactured by a STRICTNESS in the tool that has nothing to do with the question asked — same family as the git trailer tokenizer returning a clean zero for every `Co-authored by:` trailer because it demands a whitespace-free token (see the AGENTS.md mandate). Not the `EXIT=$?`-after-a-pipe family: nothing was truncated, the meter simply refused to match. doyle ruled the pairing 2026-08-29 and it is the right one — file the next instance here, not there. **How to apply:** a zero that contradicts a count you took MINUTES EARLIER is a question, not a result. Before reporting "already gone" / "nothing found" / "no matches", re-measure with the LOOSER instrument that produced the original population (`pgrep -f ` here) and reconcile the two readings. Specifically for process censuses: `/proc//exe` is unreliable across a rebuild or an upgrade of the very binary you are hunting — match the cmdline, or accept the `(deleted)` suffix. Had I trusted it I would have told the gater the orphans had cleared themselves, and the port would still be held. Related: [[identical-readings-across-opposite-outcomes-indict-the-meter]], [[dont-take-a-diagnosis-as-measured]], [[traceable-exit-2-is-an-unparseable-registry]].