Software Factory
Pabrik Software
A system of work where triggers, not humans, start agent sessions, so more work runs AFK.
A software factory is a system of work where triggers start agent sessions rather than people. A pull request opens, a test fails, a ticket is labelled, a nightly job runs. The agent picks the work up and works through it, and a human reviews the results.
The point is to move the human from starting work to judging work. A factory makes the routine flow without a person deciding to start it, which means more of it can run AFK, and the human time that remains is spent on the parts that genuinely need judgement.
A factory needs a queue with priorities, a definition of done per task type, permission rules per task type, and a way to report back. Without those it is just a script that happens to call an API. The most common failure is building the trigger before agreeing on what good output looks like, and then reviewing a hundred tasks that all need the same rework.
Related terms
AFK
A working pattern where the user starts a session and leaves the agent to run unattended.
Dark Factory
A codebase, or part of one, where a software factory writes the code and no human ever reviews it.
Agentic Workflow
A process where an agent does a meaningful part of the work, not just answers a question about it.
Ticket
A unit of work small enough to be scoped, done, and checked.
Human Review
The user reading the code the agent produced and forming a judgement on it. Reading the diff counts; reading the summary does not.
Want this working inside your team?
It starts with one conversation about your workflow.