Learn how Factory records work, checks a proposed change and keeps the evidence. Choose a page for what you need to do now.
Factory is pre-release local infrastructure. The complete customer delivery process is still in development. Current scope and evidence.
Current status
4 October 2026 · bounded local development complete. Independent qualification covers 36 installed module families, individually callable stages and two complete 13-stage workflow rehearsals on synthetic Products with controlled collaborators. The accepted source passed 3,321 root and 27 Dashboard checks. Joint qualification record.
Merged main 6716ed9d separately passed full CI: 3,321 root and 27 Dashboard tests. The immutable local receipt retains its original pending-CI field; this later run establishes merged-main verification.
| Established locally | Still open |
|---|---|
| Installed module contracts, individual stages and joined workflow rehearsals | Adoption in a commissioned external system |
| Bounded execution, independent checking and guarded local integration | Qualified live model routes and real service connections |
| Published docs, diagrams and module portraits | Customer delivery, product release and measured customer benefit |
All 42 epics remain open: 27 customer-value and 15 adoption epics. Local qualification does not close their broader outcomes. Next: commission real external adoption, qualify live providers within the owner's limits, then deliver one useful Product Slice with independent evidence. Acceptance and remaining limits · Adoption requirements.

Visual understanding
Explore the diagrams: every module's input supplier, responsibility, result and reuse boundary, plus the workflows that connect them.
How work flows
Need → Slice → Candidate → Verdict → Receipt → Assessment
A proposed change, a technical pass and a measured customer benefit are different things. Understand those distinctions.
The Factory workflow candidate documents individually callable stages and prepared-prefix concert composition. Follow its caller procedure to retain original requests and resolve uncertainty. The current qualification records bounded local stage and composition acceptance; the caller procedure explains its remaining external and live gates.
Tutorials
Follow a complete learning exercise with a known result.
- Verify your first fixture. Run a passing check, inspect its evidence and compare a failing check.
How-to guides
Solve a specific task in an existing checkout.
Reference
Look up a contract, limit or evidence record.
- Module contracts.
- Acceptance and review evidence.
- Design tokens and UI rules.
- Documentation ownership.
Explanation
Understand the decisions behind Factory.
- The value lifecycle.
- Architecture.
- Independent adoption: Modules, Workflows and Factory.
- Provider events and Intelligence: the proposed MCP notification boundary.
- Core values.
Module map
How Modules, Workflows and Factory fit together is the map, in levels of detail: the Factory at a glance, what every part can do, which Workflow uses which Module and each Module's significant sub-parts, then each Workflow's ensemble. How the parts fit together explains each Module's responsibilities and relationships.
Modules
Understand the individual parts, then follow a module's reference when you need its exact API. Module names describe responsibilities, not steps you must complete as a user.
Meet the modules
Module guides
Browse the module explanations.
Planned next
The proposed delivery plan describes the work ahead, and the roadmap puts it in order. The build review records what has actually been accepted.
Go deeper
How these docs are organised. Meet Plumb and the module characters.
