His governed agent system checks production logs daily, files bug reports, and deploys twice a day
A developer runs his own repos and production server under a written constitution file in every repo. Automated runs check production logs daily and file bug reports. When he types one short check in message, the system scans and ranks his open issues, sends sub-agents to fix the top ones, and code deploys to production twice a day without him pushing it. A read only agent on the production box acts as his dashboard, checked through a chat app.
How it works
- Every repo carries a constitution file that sets the rules for the agents
- Automated runs check production logs daily and file bug reports
- He types a short check in message
- The system scans and ranks open issues and sends sub-agents to fix them
- Code deploys to production twice a day on its own
- On Fridays the check in starts a strategy and roadmap review instead
- His read only production agent takes his notes and questions and files them as issues for the next round
Why it’s worth knowing
His whole input most days is one short message. The system does the watching, the ranking, the fixing, and the shipping on a written set of rules he set once.
Where it’s from
Summarized from a public post on news.ycombinator.com. See the original ↗