Frameworks implement the book’s boxes. They do not redefine them. Map concepts first; pick a library second. APIs drift — verify against current docs before production. [VERIFY]
Book concept Typical framework / product feature
Control loop Agent runner / executor loop FSM / graph LangGraph nodes & edges; workflow DAGs Tools + schemas OpenAI / Anthropic tool calling; framework “tools” MCP server/client MCP SDKs; gateway products Policy-as-code Usually custom — rarely first-class Checkpoint / resume LangGraph checkpointers; Temporal workflows Memory store Framework “memory” modules; often vector-centric — impose your types Orchestrator Crew-style roles; or plain workflow engine A2A A2A SDKs / task brokers — org boundary only Traces OpenTelemetry integrations; vendor observability Eval harness Often bolt-on — keep evals/ yours HITL Interrupt / approval nodes; external queues Workers / queues Celery, Temporal, cloud queues, custom lease workers Model routing Gateways (litellm-style, vendor routers)
ShopOps LangGraph-ish
AgentFSM statusNode + conditional edges checkpoint rowCheckpointer blob Policy deny Edge to escalate / awaiting_approval before tool node Ledger append Side-effecting node writing to your log — not chat
Do not let “the graph” hide authz. Gates remain code.
Book Runner
Tool registry Registered tools Sessions Conversation/session objects ≈ working context — still add typed state Guardrails Partial overlap with policy; keep hard compliance in your engine
Book Temporal
Long-running case Workflow Tool call Activity HITL wait Signal / update At-least-once Activity retries + idempotency keys you still own
Framework = security — never.Vector memory default — override with typed controller.Multi-agent roleplay templates — justify with Ch 15 criteria.Hidden prompts — pin and version visible artifacts.Eval skipped because the demo UI looks good.
This appendix intentionally avoids pinning minor version APIs. When you adopt a framework:
Write the twelve-step design (Ch 50) without naming the library.
Map each artifact to a framework feature.
Implement a spike that preserves policy tests from ring-0/1.
Document escape hatches where the framework cannot express a gate.
Official LangGraph / Agents SDK / Temporal / MCP / A2A docs — [VERIFY URLs at time of use]
Cross-links: Ch 7–8, 16, 31–32, 47, 50