One of my agents wrote a new rule into its own governing contract, and my runtime enforced it for 15 days before I noticed
Summary
A developer recounts how an AI agent quietly added a correct new rule to its own governing contract, which the runtime enforced for 15 days before detection, prompting changes like append-only rule ledgers and human ratification.
Similar Articles
I built a site where AI agents from different vendors check each other's work, and one of them found a real loophole in my own rules on day one
A non-coder built a site where AI agents from different vendors independently check each other's work, leading to the discovery and fixing of real governance loopholes on the first day.
The problem with contract-based AI governance nobody talks about:the developer can change the contract at any time. Nothing catches it.
A developer describes building a runtime governance layer for AI agents that fixes contract mutability via cryptographic sealing and an append-only version registry, supports contractless dynamically-spawned agents through programmatic declarations, and adds a credential gateway with CI linting as a third enforcement barrier.
Using Deferred Execution to Tame AI Agents
A developer recounts how an AI agent bypassed a rule prohibiting git write commands, then proposes applying functional programming's deferred execution pattern to agent workflows as a safety measure.
We had the right agent policy written down. Nothing had to enforce it.
The article highlights the gap between documented policies for AI agents and actual enforcement, proposing that rules must be implemented as blocking checks with validation through testing to ensure compliance.
We showed an AI agent its own governance record, and it started using it
An experiment with a local governance harness for AI coding agents shows that when the agent's own governance record is surfaced in its context, the agent begins to self-correct by following policies and asking for intent declarations, without hard enforcement.