Agentic Cookbook

Executable experiments in agent workflows, protocol analysis, structured outputs, evaluation, provenance, and agent-native commerce.

This is a portfolio-style lab: broad, experimental, and practical. Each cookbook is small enough to inspect, deterministic enough to test, and explicit about its safety boundary.

Recipe contract

Every cookbook should have:

• a one-command run path;
• public or synthetic inputs;
• checked-in expected output;
• a CI smoke test;
• no credentials required by default;
• no external writes by default;
• a clear note about what the recipe demonstrates and what it does not do.

Quick start

python3 scripts/run_recipe.py structured-output-validator
python3 scripts/run_recipe.py repo-health-snapshot
python3 scripts/run_recipe.py agent-payment-simulator
python3 scripts/run_recipe.py recipe-scaffolder
python3 scripts/check_expected_outputs.py
python3 scripts/check_public_safety.py

Or with make:

make run RECIPE=structured-output-validator
make smoke

Generated outputs are written to outputs/<recipe>/actual.json and compared against each recipe's expected/output.example.json.

make smoke also runs a lightweight public-safety scan for common accidental leaks such as absolute local paths, private-key blocks, dotenv files, and likely credential assignments. The scan is a backstop, not a substitute for human review.

Starter cookbooks

Cookbook	Area	Network	Credentials	Demonstrates
structured-output-validator	AI engineering	No	No	JSON contract validation and readable failures
repo-health-snapshot	Developer automation	No	No	Open-source project health summarization from fixtures
agent-payment-simulator	Agentic commerce	No	No	Buyer/provider quote, delivery, receipt, and dispute states
recipe-scaffolder	Meta-tooling	No	No	Turning an idea into a reproducible cookbook plan

Safety boundary

Recipes use synthetic or public fixtures by default. Live network/API modes, if added later, should be opt-in and clearly marked. No recipe should require private keys, wallet signatures, cookies, tokens, account data, or authenticated services for its default path.

Status

Experimental. Recipes are intended to be readable portfolio artifacts, not production services.