Systems that can say no · The AI agent security roadmap
Build AI agents you can trust, contain, and audit.
AI agents now read email, browse the web, call APIs, write code, and move money. Most ship with the security model of a demo. This is the path from "it works on my laptop" to "we can prove what it did, why, and that it could not have done worse."
Why "Fencing Token"?
In distributed systems, a fencing token is a number that increases every time a lock is granted. Storage rejects any write carrying an older token, so a process whose authority has gone stale can never act on it. That is the principle here: authority is checked where the action happens, by a system that can say no. AI agents are the first series; the idea applies to any system that acts. (Not a cryptocurrency.)
- 60+verified resources
- 9roadmap stages
- —incidents mapped
- Weeklylast updated
Loading the latest roadmap…
The fenced agent in one picture
The roadmap
Nine stages, from threat modeling to governance. Each entry says why it matters.
Incidents worth studying
Learn and practice
The production checklist
Your ticks are saved in this browser only.
More
Latest update
Loading this week's changes…
Every week: new tools, papers, and incidents. All weekly logs
Join the community
Help make AI agents trustworthy
Found a great tool, paper, or incident write-up? Suggest it. Every merged contributor is credited in the weekly update and the Fencing Token newsletter.