Initial AI Software Factory Research Canon
This canon establishes the first body of sources for the guide. It is not a claim that every source is correct or equally authoritative. It identifies the materials that should be studied, compared, tested, and challenged.
A focused view of boundaries, contracts, state, authority, failure paths, and tradeoffs drawn from this chapter.
Flow, organizations, and economics
| Source | Initial use |
|---|---|
| The DevOps Handbook | Study flow, feedback, continuous learning, deployment systems, and organizational change. |
| Accelerate | Study evidence-backed software-delivery measures, causal reasoning, and organizational performance. |
| Team Topologies | Study cognitive load, team boundaries, interaction modes, platforms, and fast flow. |
| Toyota Production System | Study flow, quality at the source, just-in-time work, automation with a human touch, waste, and continuous improvement without forcing a literal manufacturing analogy onto software. |
Mission Control
Mission Control is the primary implementation case study. Study notes must reference the exact commit, relevant product decision or ADR, source paths, tests, observed browser or runtime behavior, and known gaps. Mission Control documentation is evidence about Mission Control. It is not the universal definition of an AI Software Factory.
Review this chapter.
Challenge a claim, boundary, missing failure mode, unclear term, or unsupported evidence statement.
- Claim
- Boundary
- Failure
- Evidence