Developer discovers AI enforcement hook measured freshness, not content, invalidating prior results

A software developer published a write-up about a pre-tool hook designed to deny work when a decision ledger had gone too long without an entry, crediting it with stopping non-compliance four times. A reader pointed out a fundamental flaw: the hook checks a freshness predicate — how recently the ledger was written — rather than a content predicate, which would verify whether an actual ruling was recorded. This mirrors an earlier bug the author had described, where a safety gate counted running cargo processes instead of asking whether any protected process was active. When the developer ran controlled tests to validate the critique, the harness failed twice due to bugs in output capture and an undeclared tool configuration, both of which initially disguised themselves as gate failures. Ultimately, the tests confirmed the reader's diagnosis: the four prior denials lacked a denominator, since an empty but timely ledger entry would have passed the gate just as easily as a properly recorded ruling.