Inside the Software Factory
You've heard us say we built the Software Factory to run your entire Software Department. This is what it looks like inside.
The floor builds the work. The brain senses, plans, remembers, sleeps on it and learns. Three keys on the front rail only a person can turn.
An isometric factory on a workbench. A conveyor in front carries one tray past a ticket printer, a glass display case with a measuring arm, a magazine of blanks, a press, a gantry with two tool heads and a foreman's booth, a stamping turret, a gate with eight pins beside a fenced test cage, and a dock with a beacon. Behind the line stand a pegboard of tools, parts bins, a card sorter, a sorting desk with a stamp and a card cabinet. A raised shelf along the back holds a switchboard, a drafting table, a test bench with a gauge and a drum that links cards. Cables run from the shelf to the floor and from the dock back to the intake. Three key switches sit on the front edge.
Pick an example order and start the line. It stops at each owner key until you turn it.
Where the work is made. Seven sections, left to right along the line.
Your current site sits under glass. We crawl it as deep as its size calls for, then write one page: what to keep, what to reimagine, what to drop, and what the rebuild will cost.
We work like a car factory. Parts every site runs unchanged come sealed and pinned, so one fix reaches every site. Options come in open bins and are changed to fit you. What only you asked for is built in your own repo.
Every new site starts as a copy of the same chassis.
Each skill is written once and runs on Claude and on Codex. A skill carries only the method. What is specific to your business lives with your project.
The Overseer runs the work from its booth. Each unit gets its own Builder in its own copy of the code, and read-only Workers do the digging.
Codex finds, Claude judges. Where units share a seam, one bench joins them.
Art direction decides the visual world before any screen is drawn. A second model writes and edits the copy against one voice contract.
Eight checks run on every change: rebase, review, test, document, lint, push, pull request and CI.
In a fenced copy, a cast of bug-makers tries to break it: hostile, careless, rushed, confused and elderly users. A judge from a second model family scores screenshots at desktop and phone width.
Rollout runs in a safe order: settings first, then additive database changes, then code, then anything destructive. Smoke checks run against the live site, and forms are proven to deliver.
Where the work is sensed, planned, remembered and improved. Five sections on the shelf and along the back wall.
Orders come in by text, by chat or in the team channel. Every caller gets the right door: owners, engineers and guests each see a different factory.
When a run gets stuck, it texts a person and waits for the answer.
A fuzzy idea becomes stars you can test. We freeze the contract at every seam between parts, give each seam a stand-in, and slice the work into units. Every unit traces back to a star.
Every working session is captured. Secrets are stamped out before anything is stored or read by a model. An extractor and a reviewer turn what remains into entities, events and facts.
The next session starts with what the last one learned.
The day's notes are digested every six hours. Every couple of weeks, duplicate memories merge, contradicted facts retire and stale ones are archived.
A thumbs-down on any reply becomes a failure case. Skills are tuned against a suite of eval cases and kept only when the score holds and the cost falls.
Every ruling the owner makes on a piece of copy becomes a dated line in the voice log.
Just let us know about your business. We'll reply with what the Software Department can do for it.