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 focused view of boundaries, contracts, state, authority, failure paths, and tradeoffs drawn from this chapter.
Labs2 min readlabQuick Readfailure injection lab

Orchestration Failure, Recovery, and Cost Lab

Prove bounded convergence and safe recovery under provider degradation, unknown side effects, budget pressure, duplicate delivery, partial multi step results, and human escalation. Attribute the whole cost to the accepted or failed outcome.

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

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

Hands-on lab

Prove bounded convergence and safe recovery under provider degradation, unknown side effects, budget pressure, duplicate delivery, partial multi step results, and human escalation. Attribute the whole cost to the accepted or failed outcome.

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

practice2 min chapter
Jump to validation criteria

1. Synthetic workflow

Build a three-step workflow: inspect a synthetic repository, generate a small change, and publish a mock review request. Pin workflow, model profile, tools, context, policy, evaluator, environment, attempt/tool/time/token/cost budgets, stop conditions, and approved fallback.

3. Failure injections

  1. Duplicate one dispatch command and prove lease/state/idempotency controls prevent duplicate execution.
  2. Return transient model errors long enough to open a circuit. Verify bounded jittered backoff and either approved fallback or explicit pause.
  3. Make the publish tool time out after applying a mock side effect. Verify reconciliation before retry.
  4. Feed repeated evaluator failures with no measurable improvement. Verify the loop stops and escalates instead of spending the remaining budget.
  5. Exhaust the token or monetary reservation one unit before a model call. Verify no overrun and that safe teardown/containment capacity remains.
  6. Crash the controller after a child result but before the join commit. On restart, reconcile the result exactly once.
  7. Pause and resume after changing a governing context or capability version. Verify resume is denied and a new attempt or explicit replan is required.
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