A software factory is not many agents writing code. It is a production system: a validated specification and a reusable pattern go in, typed assembly stations transform them, independent checks decide what advances, and a durable run record lets the work resume after a failure. This site starts from one deterministic function and climbs, one idea at a time, to the WatchAlgo case study and to enterprise factories with integration, authorization, governance and release gates.
WatchAlgo needed thousands of algorithm problems, each with a description, solutions and a visualization. Doing that one at a time does not scale, and letting agents run unchecked produces work that only looks done. Software factory engineering decides what is fixed in the pattern, what each station must prove, what runs in parallel, how a long run survives an interruption, and when a person has to approve.
A factory before AI, extracting a pattern, the specification as a contract, the smallest factory, typed stations, and where a model belongs and where plain code does.
A problem as a production unit, station decomposition, the visualizer and three narrative flavors, large backlogs, long runs and checkpoints, evidence of correctness.
Demand intake, reference patterns, platform foundations, an insurance intake and orchestration factory, data and integration, CI/CD, governance and safe scaling.
First-pass yield, rework and cost per accepted unit, failure and recovery scenarios, the tooling landscape and a full enterprise blueprint.