Silent pipeline flaw: passing checks whose results never reached the system that needed them

A software team discovered that an automated check was running and passing correctly for weeks, yet its results never appeared in the acceptance report because the check was missing from the device routing list that writes to the permanent record. Neither the check nor the acceptance step flagged an error — the gap simply produced an 'absent' status, which the system treated as 'not yet applicable' rather than a failure. A second issue caused intermittent digest mismatches in a map component, traced to the append-only record being incorrectly pinned as an input, meaning every new log entry invalidated the map's freshness. Both defects were invisible from within their respective components and produced no red alerts, only ambiguous or silent outputs. The key lesson drawn is that verifying a component works is insufficient — what must be tested is whether its results are actually reachable by the systems that depend on them.