0% read on this device
Browse the curriculum

Start Here

Vision

First Principles

Operating Model

Domain Model

Agent Factory

Runtime Architecture

AI Engineering

Autonomous Workflows

Verification & Delivery

Factory Platform

Quality Engineering

Security & Governance

Case Studies

Labs

Interview Practice

Research Journal

Reference

Curriculum/Reference/A focused view of boundaries, contracts, state, authority, failure paths, and tradeoffs drawn from this chapter.
Reference7 min readoverview

AI Software Factory Mastery Curriculum

The curriculum moves from the purpose of the factory to its operating model, domain, runtime, assurance systems, implementation, and leadership use. The sequence matters. Runtime mechanisms make sense only after the learner understands the

Status: ReferenceRisk: variableMaturity guide →
Claim boundaryThis is curriculum guidance. It does not by itself prove a production implementation.
architecture mode

A focused view of boundaries, contracts, state, authority, failure paths, and tradeoffs drawn from this chapter.

3. Operating Model

Explain how humans and agents divide responsibility across intent, planning, execution, validation, approval, recovery, and learning. Examine governance, progressive autonomy, organizational transformation, human attention, and factory economics. Distinguish factory-owned deployment governance from deployment execution delegated to CI/CD systems.

Chapters:

4. Domain Model

Develop the authoritative chain from organizational scope to accepted outcome:

Company -> Workspace -> Repository -> Factory Configuration -> Mission -> Plan -> WorkOrder -> Task -> Attempt -> Evidence -> Pull Request -> Release

Each concept must explain the decision it owns, what it does not own, its lifecycle, its relationships, and the failure caused when layers are collapsed.

Chapters:

6. Runtime Architecture

Study the systems that turn authorized work into durable execution. Topics include React, Convex, Hono, executors, worktrees, GitHub, queues, state machines, concurrency, retries, cancellation, recovery, and orchestration.

Implementation-specific material must remain clearly separated from enduring runtime principles.

Chapters:

8. Autonomous Engineering Workflows

Turn general agent capability into explicit workflow products. Onboard repositories before granting authority, then distinguish feature, defect, test, dependency, security, incident, production, modernization, and knowledge work by trigger, evidence, risk, recovery, and accepted outcome.

Chapters:

Supplemental: Mission Control Case Studies

Use Mission Control to examine real architectural decisions, implementation tradeoffs, failures, and lessons. Every case study cites the exact product source and commit while preserving the distinction between product documentation and personal learning.

Current case studies:

External review

Review this chapter.

Challenge a claim, boundary, missing failure mode, unclear term, or unsupported evidence statement.

  • Claim
  • Boundary
  • Failure
  • Evidence