CI

I used to want one agent that could do everything. Write the PR, tidy the calendar, answer Slack, review the diff, remind me about lacrosse pickup — one conversational surface, one “brain,” one place to yell when something was wrong. It felt efficient until the failures started rhyming. Coding work leaned on personal-assistant shortcuts. Calendar noise interrupted engineering focus. A gateway that looked like a helpful front door became a noisy hallway where every request sounded the same, and “the agent is up” — meaning the process is running, the light is on — stopped meaning either job was actually done. ...

This is part 1 of the Agent production system series. Start with the system map if you haven’t read it yet. On the interactive diagram: Eval gates. Demo agents look smart until they touch a real repo. In a demo, the agent writes the code, the code runs once, everyone claps. Nobody checks what happens the second time, or the tenth, or the time the agent decides the fastest way past a failing test is to delete the test. Then you learn the hard lesson: intelligence without a gate is just a faster way to ship a bad change. ...