Coverage is not proof.
Use this map to separate documented architecture, editorial maturity, validation, and operational evidence.
44 chapters, 8 stages, 3 case studies.
A review-ready chapter is ready for external scrutiny. It does not imply that the described implementation is operationally proven.
What is covered. What is not proven.
Reference architecture
Lifecycle, logical components, trust boundaries, authority, evidence, inventory, and minimum-sufficient autonomy.
Review-ready architecture; full implementation conformance remains unproven.Open the chapter →02Agent Factory
Capability identity, registries, packaging, dependency resolution, certification, promotion, and revocation.
Review-ready architecture; unified production registry remains unproven.Open the chapter →03Repository intelligence and workflows
Onboarding, owner validation, instructions, architecture, dependencies, build, tests, data, readiness, and the workflow catalog.
Catalog and contracts are review ready; only the first bounded workflow has partial evidence.Open the chapter →04Verification & delivery
Testing, artifacts, CI/CD, migrations, compatibility, progressive release, rollback, and production outcomes.
Architecture is review ready; the complete production path remains unproven.Open the chapter →05Factory platform
Portal, catalog, golden paths, scheduling, cost, fairness, resilience, disaster recovery, and operator experience.
Architecture is review ready; fleet-scale and recovery proof remains unproven.Open the chapter →06Security & governance
Agentic threats, policy, identity, secrets, privacy, provenance, licensing, and compliance.
Core controls and review-ready additions exist; full adversarial evidence remains unproven.Open the chapter →07Control & operations
Emergency control, decision rights, SLOs, cost, continuity, drift, triage, response, and verified closure.
Review-ready contracts; exercised fleet-scale operating proof remains unproven.Open the chapter →08Evaluation & learning
Datasets, graders, uncertainty, experiments, optimization, regression control, and human promotion.
Architecture is review ready; production optimization and rollback remain unproven.Open the chapter →Every stronger claim needs stronger evidence.
- 01Missing
No accountable coverage exists yet.
- 02Scoped
The boundary is named; a complete chapter is not yet available.
- 03Draft for study
Useful working material awaiting technical and editorial review.
- 04Review ready
Complete enough for external architecture, technical, editorial, and usability review.
- 05Validated
Review feedback and defined evidence checks are complete.
- 06Operationally proven
Repeatable evidence exists for an exact implementation and operating scope.
Challenge the boundary, claim, failure, or evidence.
Use the reviewer guide for focused architecture, builder, operations, security, or guide feedback.
