AIFactory takes a signed plan and builds it, each task inside its own throwaway Kubernetes Job. The last three weeks were less about new capability and more about a category of bug that is specific to autonomous systems: the builder reporting state that was true of its intention rather than of the world.
Most autonomous coders are trusted on their word. They report a green test suite and you believe them, because there is no cheap way to check. AIFactory is built so that word costs nothing and the evidence costs everything: a passing test checkbox is impossible unless a real test runner actually executed. On 2026-07-19 we drove a plain GitHub issue through the whole pipeline, plan to verdict, with no humans in the loop, and this is the build side of that run.
When a build can only run on one node, you do not have a cluster — you have one machine with extra steps. This is the story of removing the last thing that pinned an AIFactory build to a single node, why it took three small changes instead of one, and exactly where the honest line sits between "shipped" and "proven."
This was a concurrency week. AIFactory started it as a single-instance app that ran one build at a time inside its own pod, and ended it with a control plane that can run many builds at once across replicas, plus the plumbing for moving the heavy work out of the web-server pod entirely and into per-task Kubernetes Jobs. The last part is not finished — and the honest version of that is the most useful thing in this post, so it gets its own section near the end.