2 ms·
we've been running AGENTS.md in production on helios (https://github.com/BintzGavin/helios https://github.com/BintzGavin/helios) for a while now. each role own
by GBintz 8mo ago
we've been running AGENTS.md in production on helios (https://github.com/BintzGavin/helios https://github.com/BintzGavin/helios) for a while now.
each role owns specific files. no overlap means zero merge conflicts across 1800+ autonomous PRs. planning happens in `.sys/plans/{role}/` as written contracts before execution starts. time is the mutex.
AGENTS.md defines the vision. agents read the gap between vision and reality, then pull toward it. no manager, no orchestration.
we wrote about it here: https://agnt.one/blog/black-hole-architecture https://agnt.one/blog/black-hole-architecture
agents ship features autonomously. 90% of PRs are zero human in the loop. the one pain point is refactors. cross-cutting changes don't map cleanly to single-role ownership
AGENTS.md works when it encodes constraints that eliminate coordination. if it's just a roadmap, it won't help much.
- bavell 8mo agoMight be some interesting nuggets in your article but my eyes rolled so hard at this part I had to stop reading: "The system does not assign tasks. It defines gravity." Helios looks cool though!