Prompt and Model Versioning
Or: The day the diff was empty and the behaviour wasn't

Search for a command to run...
Articles tagged with #system-design
Or: The day the diff was empty and the behaviour wasn't

The new model swept the golden set, the regression suite, and the LLM as judge evals. Then CSAT dropped. The eval did not lie. The eval measured exactly what it was built to measure. That was the problem.

Every "rogue agent" story is really an engine story in disguise: an agent that exceeded its budget operated in a system without one, and an agent that double executed a tool did so because the engine let it.

When the interviewer says "design an ML serving platform at scale," your infra instincts will betray you on every dimension: the bottleneck is GPU memory, output length determines latency, and the batching strategy you learned for image classifiers is worse than useless here.

A support agent is the only employee you will ever deploy that can issue ten thousand refunds a second, has read every page of your help center, and will cheerfully invent a return policy if the retrieved documents come up short. Scale that carefully.

The moment an LLM starts narrating retrieval results, your retriever becomes your access control layer. Filter permissions anywhere above that and you have built a very sophisticated data leak with excellent citations.
