Skip to content

Reference Layer

If the book explains why a safe agent system should be built this way, the reference layer helps answer what exactly should be captured in artifacts, schemas, and contract pages.

This layer is intentionally supportive, not primary. It exists to anchor the book's argument in reusable engineering materials, not to replace the reader journey of the book itself.

Use this section when you need to:

  • find the right contract page quickly;
  • prepare a design review or rollout review;
  • extract reusable artifacts for your team;
  • move from conceptual chapters to applied engineering materials.

If you are new to the project, start with the book first. Come here when you want the supporting schemas, checklists, and contract surfaces behind the main argument.

What this layer does not promise:

  • it does not replace the book's reader journey;
  • it does not explain the main causal argument chapter by chapter;
  • it does not try to be the primary place where trade-offs and layer boundaries are learned.

Start here

For a short path in, start with:

  1. Glossary
  2. Cheat Sheets
  3. Reference Package

Support-triage artifact route

If you read the book through the support-triage case, keep the trace, eval dataset, policy bundle, approval record, incident record, change rollout, lifecycle artifact, and registry operations pages next to it. Those contracts turn the duplicate-ticket incident from a story into a reviewable artifact set.

Schemas and contract pages

Practical pages

Fast Topic Routes

If you do not need the whole reference layer, but only a short path into one concrete topic, start here:

Continue

The simplest rule is:

  • use the book for argument and sequencing;
  • use the reference layer for support artifacts and implementation-facing detail.