Understand the operating model.
Learn why software factories need a lifecycle of their own and see the principles that keep autonomy governable.
You will leave withA clear mental model and vocabulary for explaining FDLC to your team.
FDLC learning library / Review candidate
Find the guidance you need to build a trustworthy software factory.
Choose a practical path, explore a topic, or search the complete FDLC draft reference. The library connects the operating model to concrete architecture, implementation, and adoption work.
Start with your outcome
Choose a path through FDLC.
You do not need to read the library front to back. Each path connects a question to a short, deliberate sequence.
Build your first bounded factory.
Move from an intended outcome to a working factory line with explicit verification and evidence.
You will leave withA practical sequence for building and proving one useful workflow.
Design a trusted factory platform.
Work through the control boundary, authority model, independent verification, and production observability.
You will leave withAn architecture checklist for keeping intelligence flexible and authority bounded.
Adopt FDLC across an organization.
Assess maturity, sequence adoption, establish governance, and define the operating responsibilities around the factory.
You will leave withA staged adoption conversation grounded in controls, ownership, and measurable outcomes.
What the library gives the community
From shared language to repeatable practice.
Learn the model
Build a common vocabulary for intent, authority, evidence, qualification, and outcomes.
Apply it to real work
Use guides, tutorials, patterns, and examples to design one bounded factory line.
Adopt it responsibly
Connect architecture and operations to maturity, governance, and organizational ownership.
Explore by topic
Use the library as a reference.
Go directly to the part of FDLC that matches the decision or implementation work in front of you.
5 documents
Foundations
The lifecycle, delivery loop, maturity model, and operating principles.
Browse foundations →19 documentsArchitecture
Control boundaries, authority, evidence, security, routing, and operations.
Browse architecture →12 documentsBuild guides
Complete factory patterns for common engineering outcomes.
Browse build guides →16 documentsTutorials
Step-by-step implementation tasks for factory engineers.
Browse tutorials →24 documentsPatterns
Reusable solutions for governing and operating software factories.
Browse patterns →22 documentsSpecification
Normative objects, schemas, examples, and conformance guidance.
Browse specification →Loading the Learning Library…
For reviewers and maintainers
Inspect the evidence behind the preview.
These checks establish integrity and publication boundaries. They do not qualify the draft or replace Product Owner review.
Open verification evidence and publication limits
Manifest-backed routes
Manifest-derived
Reported, never shadowed
Detects stale output
What automation proves
The content pipeline can be reproduced and tested.
It does not settle open semantic decisions, verify external Mission Control files, adjudicate proposed taxonomy, or authorize replacement of existing pages.
- 95 allowlisted review and machine-readable artifacts
- Canonical collisions remain a future preserve, merge, or supersede decision
- Soft-launch links are labeled Preview; routes remain outside sitemaps and search indexing