Cookbook Index
August 18, 2026 · View on GitHub
Pick a row (what stage you're at) or a column (what you care about). Every cell links real pages; empty cells render as
—, never invented pages. A page may appear in at most two cells.
The matrix (stage × objective)
Notes on placement: red-team pages live in the simulate and evaluate rows
because red-teaming rides the simulate and evals engines; the promote row
holds the pages whose output is a regression baseline you keep
(promote-to-regression appears under both capability and safety — same page,
two reasons to need it).
By layer (literature vocabulary → kit surface)
| Layer | Pages |
|---|---|
| memory | optimize/memory-targets · simulate/memory |
| skills / tools | prove/actions · redteam/first-campaign |
| protocol | frameworks/mcp · frameworks/a2a · frameworks/openenv |
| harness | prove/release-check-in-your-ci · quickstart/golden-path-ci |
By framework
LangChain · LangGraph · LlamaIndex · AutoGen · CrewAI · OpenAI Agents · PydanticAI · LiveKit · Pipecat · Browser Use · MCP · A2A · custom · OpenEnv (compatibility input)
Indexes and reference
These pages carry backing: [] — they catalog the corpus rather than run it,
so they sit outside the matrix:
- Landing page — the spine, golden paths, and the compact mirror of this matrix.
- This page — the full 2-axis index.
- reference/artifacts.md — the closed artifact-kind catalog.
- reference/cli.md — the
agent-learncommand surface. - reference/configure.md — API key semantics, offline vs platform.
How to read a page
Every cookbook page follows one skeleton: frontmatter (the manifest twin),
what you are testing, run it (CLI and SDK for the same operation), what you
built (the machine-checkable postcondition), when it fails (symptom → layer →
doctor check), and the next spine step. The frontmatter declares the backing
example under examples/ and the artifact kind the page emits; the
docs_executability release gate re-verifies both on every release, so a page
whose runnable twin breaks cannot ship. Pages flagged opt_in_lane: true
(voice and live-provider sessions) are not on the golden path and link the
follow-up phase that covers their live infrastructure.