Agent loops ship megabytes of context across VPC and cloud boundaries on every turn, and the freight never shows up on the model invoice. Why the Hadoop-era rule of moving compute to data is back, and how to audit the gravity of your inference stack.
Most 'hallucinations' are freshness incidents in disguise. The context window is a materialized view over ten upstream sources — and it needs lineage, freshness SLAs, and backfill plans like any other data pipeline.
Text-to-SQL agents fail on semantics, not syntax. Benchmarks show semantic layers lift agent accuracy from 84% to near 100% — why the metrics layer you half-built for BI is the tool contract your data agent is missing.
Coding agents generate slightly-wrong UI faster than any designer can review it, and style-guide prompts decay. The fix: make design tokens the only importable source of design values, enforce them with lint rules and types, and turn your design system into a contract that fails the build.
Inversion attacks recover the exact text behind embeddings — including names from clinical notes — which makes your vector store personal data, not anonymous math. How deletion requests fail against soft deletes, snapshots, and surrogate IDs, and the propagation architecture that fixes it.
AI agents read your stack traces and CLI errors far more often than humans do — and they execute them as instructions. How to write error messages that converge retry loops instead of sending fleets of agents spiraling.
A fine-tune is a fork of someone else's codebase, and every base-model release is an upstream rebase you didn't schedule. Deprecation clocks, LoRA portability walls, and the fork-economics rule for when prompting plus retrieval beats owning the weights.
The moderation classifier in front of your LLM is a second model on the critical path — with its own latency tail, drift, and outages. How to budget its latency, choose fail-open vs fail-closed on purpose, and monitor the gate like the model it guards.
Coding agents write flawless React but hallucinate your in-house ORM. Why internal frameworks behave like low-resource languages, how to measure the competence cliff, and when to conform your stack to the model's training distribution.
AI-generated code that looks idiomatic but targets a two-year-old version of your stack is a bug class review can't catch. Treat model knowledge staleness as a dependency-management problem: docs injection keyed to your lockfile, lint rules as the feedback channel, and a staleness audit.
Rename a column and the compiler catches every consumer except your system prompt. Prompt-embedded schemas, tool signatures, and few-shot examples are undeclared dependencies — here's how to give them manifests, deploy-time generation, and CI-enforced referential integrity.
A credential that transits an LLM's context can't be un-leaked — it is copied into traces, prompt caches, memory stores, eval fixtures, and provider logs before rotation ever runs. Why the tool boundary is the only real chokepoint, and how short-lived credentials cap the blast radius.