Online Companion¶
The online companion holds material that should remain versioned, testable, and independently updateable outside the print manuscript.
The book keeps the argument, decision criteria, and minimal contract forms. This section keeps complete CLI walkthroughs, runtime configurations, trace and event catalogs, evaluation datasets, sources, and reference walkthroughs.
Main routes¶
- Runtime configs and MCP boundary
- Runtime CLI
- Eval datasets
- Traces and events
- Templates
- Checklists
- Changelog
- Errata
- Example artifacts:
artifacts/trace-demo.jsonl,artifacts/trace-failed-tool-timeout.jsonl,artifacts/trace-post-dispatch-timeout.jsonl,artifacts/session-failed-tool-timeout.json,artifacts/eval-failed-run-timeout.json,artifacts/eval-unknown-effect-reconciliation.json - Filled examples:
examples/capability-contract-support-ticket.md,examples/release-decision-record-support-ticket.md,examples/incident-record-support-ticket-timeout.md,examples/production-readiness-support-ticket.md,examples/context-manifest-support-ticket.yaml,examples/threat-map-negative-tests.yaml,examples/slo-card-support-ticket.yaml,examples/adlc-transition-support-ticket.yaml,examples/readiness-rubric-support-ticket.yaml - Complete reference package walkthrough
- Complete source list
Practice path for a safe agent¶
Readers who want to reproduce the material should start with the complete reference package walkthrough. It connects chapters to agent_runtime_ref files, CLI commands, companion artifacts, and tests. The shortest practical path is inspect-agent for inventory, simulate-run for a controlled run, dump-events and inspect-trace for evidence, inspect-approvals for the human gate, export-eval-dataset for evaluations, and check-rollout and check-controls for the release decision.
What belongs here¶
- Complete YAML configurations and review forms.
- CLI commands and expected JSON surfaces.
- Trace and event catalogs plus validation-message catalogs.
- Evaluation datasets, verifier contracts, and rollout judgment examples.
- Long source catalogs, changelog, errata, and update rules.
What stays in the book¶
- Why an architectural decision is needed.
- Which risk it controls.
- Who owns the action and its evidence.
- How a team knows that runtime, policy, trace, evaluation gate, and rollout are ready.
Chapter map¶
This map connects every print chapter to the corresponding topic in the online book and the closest executable or reference artifact. Link names matter more than internal site numbering: if the online structure changes, readers can still find the topic and its verifiable artifact instead of guessing which web chapter has the same number.