Developer's orphan-record detector caught his own missing entries the very next day

A developer built a tool to detect published web pages missing from his tracking ledger, only for it to flag three of his own articles the following morning. The orphaned records existed because his workflow logs a prose note first and fills in the structured table row later, meaning the machine-readable data often never gets written. He manually added the missing rows in four minutes, but acknowledged this was a patch rather than a fix to the underlying habit. The root issue, he explained, is that prose notes get human attention while scripts cannot flag the absence of a row that was never created. His takeaway is that any record serving both humans and automated systems will drift toward whichever reader actually complains when something is missing.