Inkitt reported that the system was shipping code daily in a technical article published by Inkitt Tech. The Agi Letkiewicz Tanner Lead Engineer at Inkitt, described it as Event-driven orchestrator that coordinates short-lived agent containers rather than relying on a fixed pipeline. Individual stages handle specification, implementation, verification, CI failure repair, and merge conflict resolution.
The orchestrator persists each run in a database, allowing execution to resume from its recorded state. Inkitt's one-shot PR creator architecture (Source: Inkitt Blog Post) The orchestrator separates decision-making from side effects. Its core transition function maps the current run state and incoming event to the next action without directly accessing a database, network, or language model.
