What's New¶

This page is a short reader-facing log of major additions to the book and reference runtime. It is not a replacement for git history; it exists to show that the project is active and what is already here.

Current as of June 4, 2026.

Book¶

Editorial QA pass on May 14, 2026¶

The first review-remediation QA slice is closed: the Chapter 1 decision frame was moved from a table into extraction-safe prose for HTML/PDF/plain-text surfaces, and fast-moving chapters, Sources, and What’s New now carry a fresh editorial review date. The broader print/publication quality pass remains in progress.

Why it matters: the external book surface now depends less on table rendering quirks and is clearer about when the fast-moving agent-security sections were reviewed.

Part VIII on the lifecycle of agent systems¶

The book now includes a full block on SDLC -> ADLC, change management, assurance loops, supply chain, retirement, misalignment, behavioral evals, AI-native observability, and inventory control.

Why it matters: the site now covers not only architecture and rollout, but the lifecycle of an agent system after release.

A stronger production contour across Parts I-V¶

The book now includes sharper bridges between architecture, retrieval, execution, and eval discipline:

• Part I now separates runtime architecture more explicitly from the training layer and the product surface;
• Part II now gives a clearer taxonomy for prompt injection, jailbreaking, and action hallucination;
• Part III now strengthens the retrieval contour with semantic gap, HyDE, RAG first, and a clearer distinction between continued pretraining and SFT;
• Part IV now adds practical guidance for large tool catalogs, semantic tool filtering, and explicit MCP host / client / server roles;
• Part V now adds a stronger product framing for latency budget and a more practical treatment of LLM-as-a-judge.

Why it matters: the book now covers not only the baseline platform layers, but also the everyday production questions that tend to surface between design review, eval loops, and rollout.

Reference¶

A reusable reference layer¶

The site now includes reference pages for:

• traces and event catalog;
• eval datasets and grading contracts;
• policy bundles and approvals;
• change review and rollout gates;
• lifecycle artifacts;
• memory retrieval contracts.

Why it matters: readers can now move directly from explanatory chapters to reviewable schemas and contract artifacts.

Runtime¶

Runnable reference runtime¶

The repository includes agent_runtime_ref, a small runnable package that now supports:

• approvals and delegated authorization context;
• controls and lifecycle runtime-control inspection;
• lifecycle artifacts;
• session export and replay summaries;
• eval dataset export;
• trace export with redaction, redacted summaries, replay preservation, and schema versioning.

Why it matters: the book is now backed by runnable code, not only narrative documentation.

Practical Appendix¶

A stronger practical appendix¶

The site now includes:

• a glossary;
• cheat sheets;
• case studies;
• policy templates;
• a research frontier page;
• a community roadmap.

Why it matters: readers have fast access to checklists, case studies, glossary entries, and practical assets without reading the entire book linearly.

Navigation¶

Stronger entry pages¶

Updated:

• Start Here;
• Reference Layer;
• Cheat Sheets.

Those pages now make it easier to find short paths into topics such as:

• semantic tool filtering;
• HyDE and RAG vs training;
• latency budget and routed pipelines;
• LLM-as-a-judge and judge calibration;
• the difference between prompt injection, jailbreaking, and action hallucination.

Why it matters: the new topics are now visible not only inside individual chapters, but also at the reader entry-point level.

Publish Readiness¶

A cleaner site before publication¶

The print/publication quality pass is in progress, not fully closed.

Closed so far:

• draft and planning pages are excluded from the published site and sitemap;
• OpenGraph/Twitter metadata and a social preview image were added;
• the search index, sitemap, robots file, local assets, anchors, alt text, and external links were checked;
• basic navigation and canonical fallback redirects cover the main hand-copied entry points;
• the public-link availability record was refreshed on May 20, 2026 after all nine public-packet links returned HTTP 200;
• the packet blocker register, waiver/decision log, line-length guard, and packet labels are print/export-friendly;
• the Part VIII role map is now print-friendly;
• Chapter 1 now has a reader orientation block, a stable decision frame, and a compact print-ready exit that works without relying on live site navigation;
• Chapter 13 now has a technical reader orientation and compact print-ready exit for the eval dataset -> verifier contract -> rollout gate chain;
• the READMEs in all three languages now include a fast-forward publish checklist for main and docs-prod.

Remaining before this can be called print-ready: deep EN/ZH cleanup, independent rendering/export QA, independent sample copy-edit, sample export QA, and target-specific manuscript/online-companion packaging.

Why it matters: the published site should keep moving toward a polished reader-facing product, not feel like a raw build of Markdown files.

What this means for readers¶

• You can use the book as a handbook.
• You can reuse the reference pages as engineering starting points.
• You can run the example runtime instead of reading only Markdown.
• You can anchor the architecture in recent material from OpenAI, Anthropic, Google, Microsoft, and NIST.

Continue¶

• Start Here
• Reference Layer
• Book Plan
• Sources