Software can have a production line now

For years, saying that software is not a shoe factory was an honest way to stop a bad process. A shoe is cut from a pattern. Stations repeat. Add hands and the line moves faster. Software was usually the pattern itself: each feature was designed while it was being built.

Fred Brooks wrote the consequence in The Mythical Man-Month. Adding people to a late project makes it later. The craft that followed kept the warning. The cost sat in invention. Copying the result was nearly free. You could not speed the work by treating every change as another pair of shoes.

A production line has four pieces. A pattern that already exists. Stations that repeat a known step. A tolerance that says how far the result may drift. An inspection that can reject the piece.

None of that requires the work to be mindless. It requires the work to be recognizable. If you can say what goes in, what must come out, and how you will notice a bad result, you have the start of a line.

Online, in this piece, means the change has entered that production line: specified, generated, tested, reviewed, and ready to ship. It does not mean published on the internet.

An agent can take a station when the pattern is already there. It needs a specification, examples of how this kind of change was done before, and a check that says whether the result is acceptable. The agent drafts, runs the check, revises, and leaves the change ready for a person. Specification, generation, test, review, release. That sequence is a production line for a kind of change you already know.

The line does not decide which shoe is worth making. A person holds the pattern and the inspection. New architecture, taste, product judgment when the brief is ambiguous, and anything a check cannot declare wrong stay there. So does accountability. Someone still answers for what shipped.

The limit is useful. The line covers the part that is already repeatable. The rest of the work stays a craft.

Scraplay builds these lines where the work is repeatable: agents in a fixed sequence, a check before the result is trusted, and a person who can reject it. If a change in your system already has a pattern, it can go online. If it does not, there is no station to pretend.