The interesting demos book travel. The deployments that survive contract review match invoices to purchase orders. Six jobs boring enough to work, and how to build them safely....
The team builds something impressive in three weeks, demonstrates it to an approving room, then spends nine months not shipping it. The blockers are always downstream of the model....
Every ML proposal says we have a lot of data. It is almost always true and almost never the relevant question. Five checks, and the reason retrieval projects need no training data at all....
The same input produces a different answer, so the assertion fails, so someone deletes the assertion. Four scorers in order of cost, and how to fail the build on a real regression rather than on normal variance....
Neither major US provider trains on API data by default. That is the settled question. The exceptions in the retention terms, and the leak in your own retrieval layer, are the ones worth your attention....
The model call is rarely the whole invoice. A worked example at 1,000 requests a day, the two levers that actually move the number, and the lines that have no published price at all....
Knowledge problems are retrieval problems and behaviour problems are tuning problems. How to tell which one you have, and what each approach really costs to run....








