Skip to main content

The Context Trap: Why Scaling Laws Can’t Break the Ceiling of Uncertainty



We are currently living through the Post-Reasoning phase of the AI hype cycle.

By now, models like Gemini 2.0 and the latest iterations of Gemini have normalized the idea that machines can “think”—or at least, simulate a chain of thought that feels indistinguishable from reasoning.

But as we push these architectures to their absolute limits, we are starting to see a plateau. It isn’t a plateau of competence; the models are brilliant. It is a plateau of certainty.

In building applications on top of these models, I’ve noticed a recurring pattern. Developers (myself included) often assume that if a model fails to predict the right outcome, it’s a failure of intelligence. We assume we need a larger parameter count, a longer context window, or better fine-tuning.

But there is a ghost in the machine that scaling laws cannot exorcise. It is the fundamental difference between not knowing and not seeing.

The Architecture of Doubt

To understand why our models, even state-of-the-art ones, hit a wall, we have to look at what they are actually doing. Despite the “Reasoning” labels on the box, modern LLMs are fundamentally probabilistic engines. They estimate a conditional probability distribution:

P(Y | X)

Given a context X (your prompt, a code snippet, a video), what is the most likely target Y?

In the early 2020s, we spent all our energy optimizing the function that maps X to Y. We assumed that if we just made the neural network dense enough, the error rate would drop to zero. But this ignores the statistical reality that error comes from two distinct places:

  • Epistemic Uncertainty: The model doesn’t know the answer because it hasn’t seen enough training data or lacks the computational depth to find the pattern. This is solvable. This is what “scaling up” solves.
  • Aleatoric Uncertainty: The answer cannot be derived from the input. The data X simply does not contain the information required to resolve Y.

This second category is the silent killer of AI reliability.

The Oracle’s Blindfold

Consider a thought experiment. You give a multimodal model like Gemini Pro a high-resolution image of a poker table and ask it to predict who will win the hand.

The model can identify the cards on the table. It can analyze the players’ facial expressions for micro-expressions (bluffing). It can calculate the pot odds with superhuman precision. It might give you a probability:

“Player A has a 60% chance of winning.”

But if the outcome depends on the hidden cards in the deck, the model hits a hard ceiling. No amount of extra compute, no amount of “System 2 thinking,” and no amount of historical training data will improve that prediction. The information is simply orthogonal to the input sensors.

We call this the Bayes Error Rate—the lowest possible error rate for any classifier on a given outcome.

In 2025, we are guilty of conflating confidence with calibration. We teach our models to sound sure of themselves. If a model predicts a stock movement or a medical diagnosis, it often mimics the assertive tone of the human experts in its training data. But unless the model has access to the causal variables driving the outcome, that confidence is a hallucination of competence.

The Multimodal Trap

The push toward native multimodality was, perhaps unintentionally, the first step toward addressing the “Aleatoric” problem. By allowing a model to ingest video and audio simultaneously with text, we aren’t just giving it more data; we are giving it better data. We are expanding the dimensions of X.

However, we are still treating the input as a fixed variable. In the current paradigm, we feed the model a dataset and ask, “How well can you predict?”

The next leap in AI won’t come from asking the model to predict better. It will come from the model asking for better inputs.

From Prediction to Measurement

If we want to break the current ceiling of predictability, we have to stop treating AI as a brain in a jar and start treating it as part of a sensory system.

In healthcare, for example, we are obsessed with feeding electronic health records into LLMs to predict readmission rates. We might get an AUC of 0.75 and wonder why it won’t go higher. We blame the model architecture.

The reality? The outcome might depend on whether the patient has a supportive spouse at home—a variable that does not exist in the electronic health record. The ceiling is 0.75 because the signal isn’t there.

True intelligence involves recognizing this deficit. A truly intelligent agent shouldn’t just output a probability; it should output a request for measurement. It should say:

“I cannot predict Y with confidence based on X. To reduce uncertainty, I need to measure Z.”

The Future is Active Sensing

As we look toward 2026, the most exciting developments won’t be in the transformer architecture itself. They will be in the integration of these models with active sensing.

  • Coding: Instead of just predicting the bug, the IDE inserts a logging statement to capture the missing runtime variable.
  • Science: Instead of predicting the protein fold, the system suggests the specific wet-lab assay needed to resolve the ambiguity.

We have spent the last decade building better prediction engines—machines that have developed a deeply intuitive “gestalt” about the world. They are incredible at intuition. But intuition without observation is just guessing.

To lift the ceiling of what is predictable, we don’t need bigger models. We need to expand the observable universe of the data itself.

We need to stop trying to force our models to be oracles, and start designing them to be scientists.

Comments

Popular posts from this blog

Racecraft (Project Koru) · Prologue — The Origin Story

Racecraft · Prologue , The Origin Story It Started With a Wine List and a Question About Racing How a happy-hour conversation in the Bay Area turned into a trustable AI race coach , and then into a second version that runs entirely on a phone, on the NPU. This is the prologue to a five-part series. Two years ago(1st November, 2024) I was in the Bay Area for a GDE Summit. If you've never been: it's a couple of days of talks among Google Developer Experts, the kind of people who get unreasonably excited about a new on-device runtime, and then , mercifully , a happy hour where everyone stops performing and just eats. We ended up at a restaurant(Puesto Santa Clara), a long table of GDEs, and I was doing the most important engineering of the evening: trying to decide which wine to order. Across the table was Ajeet Mirwani . I don't even remember how the wine talk turned into racing talk , these things drift , but the moment the word "racing" ...

A Split‑Brain Neuro‑Symbolic Training Method for High‑Velocity Autonomous Coaching from Telemetry

 Author: Rabimba Karanjai Scope: Problem statement + data methodology + model training (no deployment discussion) Abstract Real‑time coaching in motorsport is a safety‑critical learning problem : a system must map noisy, high‑frequency telemetry to short, actionable guidance that remains physically consistent and avoids hazardous recommendations . This paper proposes a “Split‑Brain” training formulation that separates (i) a semantic coaching target (what action/critique should be expressed) from (ii) a reflexive interface (how actions are represented as compact, verifiable tokens). The approach trains a Small Language Model (SLM) in the Gemma family [1] using QLoRA fine‑tuning [2] , and introduces a telemetry tokenizer plus teacher‑student synthesis pipeline to generate instruction‑action pairs at scale. Core contribution: a reproducible method to convert “ golden lap ” differential tel...

The Throughput Trap: Benchmarking vLLM on OpenXLA and the Reality of Production LLM Serving

vLLM Systems · DevLab 2026, Deep Dive I was recently invited by the Google TPU team to speak at the OpenXLA Summer DevLab 2026 . This post breaks down our deep-dive evaluation of the matured vLLM + OpenXLA stack, the fundamental engineering mismatches between CUDA and XLA serving paths, and why traditional capacity metrics are lying to you. If you are operating large language models at enterprise scale right now, your platform architecture team is likely staring at a massive infrastructure crossroads: Should we migrate our core serving workloads from GPUs to TPUs? Historically, NVIDIA's CUDA ecosystem was the only serious option for user-facing, low-latency LLM generation. But here in 2026, the economics and infrastructure options have transformed. Google TPUs are highly available, cheaper per chip, and the open-source serving stack built around vLLM and OpenXLA has officially achieved absolute production readiness. Yet, when our infrast...