The wrapper around the model is real engineering, and it can do a lot. There’s still a line it can’t cross: anything that happens inside inference itself.
Harness engineering, wrapper engineering, context engineering: different names for the same idea. The discipline of designing what surrounds the model—prompts, tools, retrieval, validators, memory features, observability—is where a lot of practical AI value gets produced. Treating it as serious work is overdue.
But the wrapper sits outside the model. It controls inputs, routes outputs, manages context. It cannot change what happens inside the inference engine. There’s a class of overclaiming in the AI engineering community that blurs that boundary, and the blurring is starting to cost credibility.
A few examples of how the line gets crossed.
“Models can remember.” The wrapper is storing selected facts and re-injecting them into context on each call. Useful, not memory.
“Models can learn.” The model is frozen, and the original training run took months and billions of dollars. What looks like learning is curated re-prompting plus pattern-matching on what got injected. Real learning architectures are being explored in research, but not in the products making the claim.
“RAG fixes hallucination.” The literature is consistent that RAG mitigates rather than eliminates. The mechanism—the model’s internal weights overriding retrieved context—sits inside inference, where the wrapper can’t reach.
“Long-context handling is solved.” Recent models have improved markedly on simple retrieval, but multi-hop reasoning across long contexts is still uneven, and “lost in the middle” remains a documented failure mode that wrappers route around rather than remove.
None of this means harness engineering doesn’t matter. It does. The constraints, the validators, the retrieval pipelines, the budget controls, the observability: that’s all real work, and the gains are real.
What it means is that the wrapper is remediation, not resolution. Pattern completion at scale resembles reasoning closely enough that it’s genuinely useful. This isn’t autocomplete on steroids. It also isn’t reasoning, and the gap between resemblance and substance is where the wrapper’s reach ends. I spend a lot of my book, Spanning Change, on this distinction. It feels like hair-splitting until you’re trying to debug a system that’s confidently wrong.
If a wrapper claims to solve memory, learning, hallucination, or long context, ask which one. Then ask how.