# Software factories and how teams run them

How teams build, buy, and run pipelines of coding agents, from the process and the person who operates it to the stage that checks each change.

Start here

## [What is a software factory?](https://specstory.com/learning/software-factories/software-factory)

A software factory is a repeatable process in which coding agents take work from a queue, build it, check it, and ship it, while people direct the work.

10 min read

## Concepts

### [What is a software factory process?](https://specstory.com/learning/software-factories/software-factory-process)

A software factory process is the fixed sequence of stages that every change passes through, from a written goal to a checked and shipped result.

### [What is verification in a software factory?](https://specstory.com/learning/software-factories/software-factory-verification)

Verification in a software factory is the stage where a separate agent runs the built software and reports pass or needs work, with evidence.

### [What is a dark factory in software?](https://specstory.com/learning/software-factories/dark-factory)

A dark factory is a software factory in which no person writes or reviews the code, so automated checks alone decide whether each change ships.

### [What is a software factory operator?](https://specstory.com/learning/software-factories/software-factory-operator)

A software factory operator is the person who runs a software factory by asking for changes, answering open decisions, and trying what comes out.

## How-to guides

### [How to build a software factory](https://specstory.com/learning/software-factories/building-a-software-factory)

Building a software factory means writing rules in a file, keeping a queue, giving each phase one agent workflow, and adding a stage that runs it.

## Comparisons

### [What is the difference between a bespoke and a packaged factory?](https://specstory.com/learning/software-factories/bespoke-vs-packaged-software-factory)

A bespoke software factory is assembled by a team from its own rules and checks, while a packaged software factory is bought as a product and configured.

## Common questions

### [Should you build your own software factory?](https://specstory.com/learning/software-factories/build-or-buy-a-software-factory)

Building a software factory in house suits a team whose process is specific to its product, while buying one suits a team that needs scale first.

### [Why do software factories fail?](https://specstory.com/learning/software-factories/software-factory-failures)

Software factories fail when no stage runs the product, when work is lost or the queue stalls with no alert, or when the codebase gets worse over time.

## Failures and bugs

### [Examples of software factories](https://specstory.com/learning/software-factories/software-factory-examples)

Examples of software factories range from one operator with a queue to companies whose agents account for most pull requests, with or without review.

## Terms in this topic

**[Agent workflow](https://specstory.com/learning/glossary#agent-workflow)**

An agent workflow is a script that runs a fixed sequence of agents, each with one job. A software factory starts one workflow for each phase of work.

**[Bespoke software factory](https://specstory.com/learning/glossary#bespoke-software-factory)**

A bespoke software factory is a software factory that a team assembles for its own product, from a rules file, a queue, agent workflows, and its own checks.

**[Calibrated distrust](https://specstory.com/learning/glossary#calibrated-distrust)**

Calibrated distrust is the habit of doubting an agent's report in step with how confident it sounds. The cleanest reports get the hardest checks.

**[Check stage](https://specstory.com/learning/glossary#check-stage)**

A check stage is the step in a software factory where an agent that did not build the change runs the software and reports pass or needs work, with evidence.

**[Coordinating agent](https://specstory.com/learning/glossary#coordinating-agent)**

A coordinating agent is the agent session that turns an operator's request into a written goal, starts a workflow of other agents, and reports the result. It is also called an orchestrator.

**[Dark factory](https://specstory.com/learning/glossary#dark-factory)**

A dark factory is a software factory in which no person writes the code, reviews it, or tries each change. Automated checks alone decide what ships.

**[Factory operator](https://specstory.com/learning/glossary#factory-operator)**

A factory operator is the person who runs a software factory. The operator asks for changes, answers the open decisions, and tries the result, without writing or reading most of the code.

**[Manufactured trust](https://specstory.com/learning/glossary#manufactured-trust)**

Manufactured trust is confidence in a change that comes from the checks a software factory ran on it, and not from a person reading the code.

**[Packaged software factory](https://specstory.com/learning/glossary#packaged-software-factory)**

A packaged software factory is a product that supplies the pipeline, the agent runners, and the review steps of a software factory. A team configures it for its own repositories.

**[Phase (software factory)](https://specstory.com/learning/glossary#factory-phase)**

A phase is one unit of work that moves through a software factory, from a written goal to one commit. Each phase takes the same route through the stages.

**[Software factory](https://specstory.com/learning/glossary#software-factory)**

A software factory is a repeatable process in which coding agents take work from a queue, build it, check it, and ship it. People decide what to build and try what comes out.

11 terms from the [Learning Center glossary](https://specstory.com/learning/glossary).

---

Source: [Software factories and how teams run them | SpecStory](https://specstory.com/learning/software-factories)
