Month three of an agent programme should produce a decision — one with evidence behind it that survives contact with someone who did not build it.

Suppose a pilot comes back positive: the treated group beats the control group on the headline measure, the delta lands on a single slide, and the room starts talking about rollout.

A LangGraph playbook is the graph itself: typed state, deterministic nodes, conditional edges, and the routing between them. The model proposes inside that structure; the structure decides. The policy lives in the graph, not in the model, so a model swap changes one node's inputs and outputs, not the rules.

Operations has a number in front of it, and the number has not moved. A flat line can mean the thing measured is genuinely flat, or that the instrument stopped reading. Only one of those is a fact about contractors. The other is a fact about a reader that received a value it had not been taught, declined to parse it, and turned its entire lane into "missing" while the chart kept its axes. In LangGraph terms that reader is a node in a StateGraph, which is where the fix belongs.

The programme was ready and waiting on a legal answer, not a build. The fastest option to switch on had no consent ruling on record, and no amount of engineering closes that.

The read-out was flat. The room split into the two explanations always available after a null: the model wasn't good enough, or the test was too small. Both assume the experiment was about the model. Both usually miss the point. The forecast, written down before the run, said every candidate was predicted to move the metric by less than the design could resolve.

Three weeks after the read-out, the meeting happens. Not the launch review — the other one. Someone from procurement, or legal, or the VP who inherited the budget, asks how the cohort was chosen. The room looks for a document that predates the number and finds a deck that postdates it. The evaluation criteria live on a single slide, written in the week the traces started looking good. The success threshold appears in the same sentence that reports clearing it.

A number arrives in the review pack. Someone asks where it came from. The answer is a thread, a notebook, and an engineer who is on leave.

The question arrives in a budget review, dressed as a hypothetical: is the agent already able to email our contractors?

The most expensive component in an agent is not the model. It is the record you decided not to write. LangGraph's answer is a checkpointer compiled into the graph and keyed by the run's thread id, saving graph state between steps so a restarted run resumes from its last checkpoint instead of starting again (LangChain docs, persistence).