Silent stubs and dead code: why 'which parts are real' must have a clear answer

A software engineer working on a private deployment platform discovered that a system had been confidently answering queries for weeks without throwing a single exception or failing any test. The root cause was a pattern of silent fakes: a database column never written to, a complete access-review model with zero application references, and drivers that returned null without any documented intent. The investigation revealed that different infrastructure providers cannot honestly answer the same question the same way, making a blanket fix impossible. Instead, the engineer pinned deliberate nulls in tests with explicit comments, converting unexplained absences into documented decisions. The broader takeaway is that fake or stub components are valid for incremental shipping, but the system must make it enumerable and obvious which parts are real versus placeholder at any given time.