Green Is a Timestamp

Short summary

Two production failures—one in a Medicare reimbursement engine, one in an ad-tech cron—were caused not by code changes but by time passing. A hardcoded fixture date aged past a 72-hour backdate window, and a timeout-summing status check silently reported success for weeks. The key insight: a passing test is a timestamp, not a permanent state, so verification logic needs scheduled audits just like dependencies need CVE reviews.

• •Hardcoded fixture dates are countdowns, not constants—audit them on a schedule
• •Cron jobs need external heartbeats so silence becomes an alarm, not an assumed success
• •Green checks verify one moment under expiring assumptions; treat them as dated receipts

Generated with AI, which can make mistakes.