
Eval gate passed, production broke: add a smoke eval to agent deploys
A 96% offline score, a 3-second timeout and 212 double refunds. The 20-case, 3-minute check that stops it at 5% traffic.

A 96% offline score, a 3-second timeout and 212 double refunds. The 20-case, 3-minute check that stops it at 5% traffic.
The JWT was valid. The model still picked the customer ID. Move identity into the state so a fooled model can't reach the wrong data.

Retries come from four layers and can multiply to 18 runs of one action. Seven rules make a dangerous tool call happen exactly once.

In my RAG eval, [X] of [N] failures never had the evidence in context. A second agent would have failed the same way at about 4x the tokens.

Reserve an estimate before the model call, correct it after, and give every agent to run its own budget.

Three caches in front of an agentic RAG system, and five cases where a cache hit must be treated as a miss

One RAG pipeline, many users: four checkpoints that keep every answer inside the asker's own documents. Grounded RAG in Production, Part 2. When one RAG pipeline serves many teams or customers, the lo

An identity provider issues the tokens, the API only verifies them, and neither the model nor an uploaded PDF gets a say in who the user is.
