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/Labs/A rapid review of the chapter’s existing Quick Read, principles, definitions, lessons, and review material.
Labs2 min readlabQuick Readfailure injection lab

External Capability Intake and Recertification Lab

Qualify a synthetic external tool through ownership, provenance, data use, security, service, side effect, cost, incident, exit, certification, publication, drift, revocation, and recertification controls.

Status: Review readyRisk: highLifecycle: define · execute · verify · learnContent reviewed 2026-08-30Maturity guide →
Claim boundaryThis chapter references implementation evidence. Inspect its evidence boundary before treating a claim as proven.
study mode

A rapid review of the chapter’s existing Quick Read, principles, definitions, lessons, and review material.

Quick Read

The chapter in one pass.

~2 min

Qualify a synthetic external tool through ownership, provenance, data-use, security, service, side-effect, cost, incident, exit, certification, publication, drift, revocation, and recertification controls.

Hands-on lab

Qualify a synthetic external tool through ownership, provenance, data use, security, service, side effect, cost, incident, exit, certification, publication, drift, revocation, and recertification controls.

Execute the existing Markdown instructions and retain the required output and evidence.

practice2 min chapter
Jump to validation criteria

2. Intake review

Record source and build provenance, component inventory, licenses, security and privacy assessment, credential and network design, subprocessors/data-use assumptions, service limits, incident notification, business owner, technical owner, and independent reviewer. Resolve the exact artifact digest; a moving version label is insufficient.

Evidence boundary

Curriculum maturity is not implementation proof.

This chapter defines architecture or practice. It does not by itself prove a corresponding production implementation.

CurriculumReview readyImplementation evidenceNot asserted hereInspect evidence map →
External review

Review this chapter.

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

  • Claim
  • Boundary
  • Failure
  • Evidence