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

Factory Observability and Agent Runtime Telemetry

An agentic factory can be busy while making no progress, cheap while producing unsafe work, or successful according to a model while violating authority. Operators need to understand outcome, control state, execution health, cost, and evide

Status: Draft for studyRisk: highLifecycle: executeContent 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.

runtimeharnessenvironment5 min chapter
Open the source exercise

Trace one WorkOrder from dispatch through a timed-out Attempt, lease expiry, retry, PR publication, validation, and acceptance. Show span links, authoritative records, metrics, evidence, and alerts. Explain which data can be sampled and which cannot.

4. Tradeoffs

Full-fidelity traces improve debugging but increase cost, privacy risk, and cardinality. Sample successful low-risk detail while retaining unsampled domain/audit/evidence records and error traces. Metrics aggregate well but lose causality; traces explain one run but not fleet trends. Logs remain useful for unstructured diagnostics but should not be the primary integration contract.

5. Current Mission Control Implementation

Mission Control contains runEvents, runArtifacts, health/metrics surfaces, a monitoring dashboard with secret-pattern redaction, model-router usage fields, QC views, and execution/trace inspector UI. The current staged working tree adds stronger Attempt lease events and execution-manifest lineage; those staged-only additions are not treated as committed capability.

The implementation is not yet a demonstrated end-to-end OpenTelemetry architecture. Cross-service trace context, standardized model/tool spans, durable alert ownership, evidence-freshness SLOs, and complete cost attribution to validated customer outcomes remain incomplete or proposed.

External review

Review this chapter.

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

  • Claim
  • Boundary
  • Failure
  • Evidence