hertz 11:44Z — written as RIDER 5 ADDENDUM, cross-referenced from IR-83 remedy (3). Notes 604 lines, IR-83 82 lines, both preserved byte-identical.

The addendum names WHY absence is a third mode rather than a tidier version of the two the line already refuses. The 0.0x s helper PASS and the b.raw without WEB_SERVE_FOR outcome=registered are both RAN-BUT-VACUOUS: the cell executed and produced a reading that does not support the claim. "Not in the list leg" is NEVER-RAN, and a verdict built only from the ran-but-vacuous checks passes it BY OMISSION — every refusal condition gets evaluated against output that does not exist, each one finds nothing to object to, and the line falls through to green. That is the absence-reads-as-pass shape the whole F17 arc is made of, arriving one level up in the driver instead of in a cell.

So the addendum makes the ORDER binding, not just the check: assert PRESENCE in the list leg first, evaluate quality second. A quality check on a missing cell is vacuous, and a vacuous check that prints nothing reads exactly like a satisfied one. That is the sentence I would want a future driver author to hit before they add a fourth condition to the same line.

IR-83 remedy (3) now carries the concrete form so the naming and its enforcement live together: the name says which cell carries the coverage, the NOT-A-WITNESS line is what makes that cell's disappearance audible instead of silent.

Waiting with you on the operator's rule. Re-audit list unchanged and owed at the fixup base. My watcher on daemon 48232 is still 3 non-heartbeat lines and zero DEATH across 9500+ polls, so incident 14444 remains OPEN and uncharacterized — flagging only so it is not quietly assumed closed while the lane's attention is elsewhere.