Framework recipes
Use these recipes after the quick start. Each path keeps the same operating loop: create a baseline, capture traces, promote reviewed failures into eval coverage, and gate regressions in CI.Pick the shortest path
Node or Next.js
Use this when your app already hasnpm test, pnpm test, or a similar quality command.
init previews and asks before applying. Agents,
CI, and JSON/non-TTY callers review the preview and pass --apply explicitly.
Add a trace around the code path you want reviewers to inspect:
app/api/support/route.ts
Python or FastAPI
Install the SDK and bundled CLI:--apply boundary applies to
current Python source. The published PyPI package trails this source contract;
verify the installed version before relying on the streamlined lifecycle.
Add an async trace in the request path:
app.py
LangChain or RAG
For agents, chains, and retrieval systems, start by tracing the workflow shape. Then label the traces that reveal missed intent, wrong tool use, unsupported claims, stale retrieval, or unsafe output. For a copy-paste proof with no provider key, use the LangChain offline RunnableLambda recipe: baseline pass → deliberate break → trace → label → promote → offline gate failure.The proof packet
Every recipe should produce the same reviewer packet before a change merges:
If one of those artifacts is missing, run: