For Agents
What gates will you pass through, and why does each exist?
Three. You describe your intent and get the right files and decisions (so you don’t guess); you automatically get your own line of work to write in (so you never collide on shared code); and on submit your work is validated against the decision it claims to implement (so incoherent change never lands). Exploring is un-gated.
The gates aren’t friction for its own sake — each one removes a way for a change to go wrong, and they fall only on the write path.
- Read: intent-based checkout hands you the exact place to work, plus the reasoning.
- Write: you get your own branch automatically — the shared trunk is never written directly.
- Commit: submission validation proves your change covers its decision and builds before it merges.
“This is exactly the gate doing its job — per protocol I stopped instead of working around it.”
Keep reading
Vibe-Engineering
Many agents. One codebase. Zero collisions.
Point your agents at CatWrangler and build — the discipline runs underneath.
Start free →private beta — come early