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/Operating Model/A focused view of boundaries, contracts, state, authority, failure paths, and tradeoffs drawn from this chapter.
Operating Model5 min readchapter

Enterprise Adoption and Factory Maturity Model

Enterprises often buy agent capability faster than they build the operating system required to govern it. A maturity model must describe observable organizational capability, not enthusiasm, model intelligence, or the percentage of code gen

Status: Draft for studyRisk: highLifecycle: intent · plan · verify · learnContent reviewed 2026-08-11Maturity 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.

Whiteboard exercise

Reconstruct and defend this chapter’s architecture.

Reconstruct the architecture, name each boundary, and defend the tradeoffs.

governancehuman authority5 min chapter
Open the source exercise

Map a 5,000-engineer enterprise across the eight maturity dimensions. Select one product corridor for Level 2, show a 90-day adoption plan, define baselines and promotion gates, and respond to a CIO who wants autonomous production deployment in quarter one.

4. Tradeoffs

Maturity models can become compliance theater. Prevent this by requiring retained proof and by assessing actual workflows, not policy documents. Uniform enterprise standards improve control but can suppress local learning; define mandatory boundaries centrally and allow teams to experiment inside them. Early automation can show fast savings while increasing hidden review and incident costs, so measure total human and operational effort.

5. Current Mission Control Implementation

Mission Control expresses several Level 2 foundations: governed Missions/Plans/WorkOrders, Tasks and Attempts, leases, execution manifests, receipts, approval records, policy concepts, model routing, and operator views. Study branches add stronger sandbox and publication controls.

It has not yet earned a product-wide Level 3 claim. QC adapters are mocked, release automation is shadow mode, policy configuration has blocked the golden path, and the complete browser-initiated flow lacks accepted retained evidence. The honest rating is capability-specific: architecture and domain model approach Level 2/3 design, while the supported end-to-end operating proof remains below that claim.

External review

Review this chapter.

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

  • Claim
  • Boundary
  • Failure
  • Evidence