What it takes to gate a deploy on agent behaviour
Unit tests are deterministic and fast. Agent tests are neither. Here is how to gate on them anyway.
Read itResources · Engineering notes
What building the detector taught us, including the parts where we got it wrong first.
Unit tests are deterministic and fast. Agent tests are neither. Here is how to gate on them anyway.
Read itA version that fixes two scenarios and breaks two has an identical pass rate and a completely different meaning.
Read itThe same agent, tested over HTTP and over WebSocket, yields different amounts of truth. Here is the part that differs.
Read itScripted conversations are reproducible and cheap. They are also blind in a specific, predictable way.
Read itA test suite that quietly passes the checks it could not perform is worse than no suite at all.
Read itLLM judges are useful for tone and helpfulness. They are the wrong tool for verifying that a business rule was followed or a tool actually ran.
Read itEvery incident should end with a permanent test. Here is how teams turn one-off agent failures into a suite that keeps growing.
Read itThe most expensive agent failure is a confident sentence about something that never happened, and a transcript cannot see it.
Read itConversation, policies, tools, outcomes and regressions, a practical model for deciding what to evaluate and in what order.
Read itPass rate alone hides the failures that matter. A short guide to the metrics worth putting on a dashboard.
Read itRefund windows and discount ceilings should be typed rules evaluated mechanically, not paragraphs buried in a system prompt.
Read itTool errors that the agent papers over are harder to find than outright hallucinations. Here is how to surface them.
Read itWhy small prompt edits produce distant behaviour changes, and how version comparison surfaces them before release.
Read itMost escalation bugs are not about whether the agent escalated, but about what the human received when it did.
Read itWhat a sensible CI pipeline looks like when the artefact under test is a prompt, a model version and a tool set.
Read itA failure report an engineer can act on in one sitting: transcript, trace, root cause, evaluator verdicts and a repro seed.
Read it