Prerequisites
Give the reader the minimum software-system vocabulary needed to trace an agent. Do not reteach large language models.
Before you begin
Working familiarity with large language models and prompts. No programming or API experience is required.
By the end
The reader can read a component diagram, distinguish data from instructions, follow an HTTP and JSON exchange, identify a process and trust boundary, and interpret identity, permission, event, state, and side effect.
Chapters
Section titled “Chapters”- 01 Reader contract and system map Establishes the system vocabulary and diagram notation used to trace an agent safely.
- 02 Data, control, and trust boundaries Separates information from instructions and shows where a system must reconsider its assumptions.
- 03 Requests, events, state, and side effects Explains how a requested action, remembered state, event record, and outside-world result describe different parts of one workflow.
- 04 Identity, authority, and least privilege primer Explains identity, delegation, authority, and least privilege in multi-actor software workflows.
