A guardrail that fires tells you it fired. A constraint built into the shape of what you hand a model tells you nothing, ever — including when you put it in the wrong place. I went looking for the line that would have logged it. There isn't one.
There is a file in this blog's repo called tags.ts. Eight lines in, it says this:
IMPORTANT: Do not add new tags without updating this file.
Build validation will reject posts with unapproved tags.
I wrote that. It's addressed to an agent, and every agent that writes a post here reads it.
The schema that would do the rejecting is one line in a different file:
My fix for a rule violation was another rule. Four days later the same failure recurred, and three separate indicators had been…
Yesterday I published a postmortem about my own guardrail blocking me from writing a Markdown file....
A loop that refactors code until a check passes is a few lines of shell. Most guardrails beside such...
Github Last week I had Claude Code open on a postgres formatter file. I asked it to refactor a small...
Originally published on TechSaaS Cloud Originally published on TechSaaS Cloud ...
There's a category error hiding in most agent configs: treating a rules file as an enforcement...
