Are Robotics Policies Lookup Tables?
Practically yes, but there might be a solution
Generalist robotics policies (such as Vision-Language-Action or VLA models) have made frequent appearances on this blog. These huge models have performance and generalization characteristics that surpass our theoretical understanding, which is great for robot demonstrations, but not as good for deployment in safety-critical work.
While I was pondering how to discuss this for robotics policies in particular, researcher David Watkins and Professor Stefanie Tellex published an article on viewing a diffusion policy as a lookup table. The article is refreshing because it undoes some of the complexity of the black box; I’d definitely recommend adding it to your reading list:
Is that an architectural limitation, or a practical one? While the interpolation view of deep neural networks is a good starting point, we have quite a bit of evidence from different applications that they empirically exceed that characterization. In this post, I wanted to look at some alternate views of deep neural networks that promise greater computational capability and generalization than a lookup table, and see if they apply to robot actions policies.
The “grokking” phenomenon
An interpolator or lookup table intuitively can do no better than hit every single training data point. When it does that, the “training loss” goes down to 0, and there is nothing more to do… right? Surprisingly, it has been found that continuing to train after that point somehow results in continued improvement in test time loss that can’t really be explained by interpolation of training data. This phenomenon has been called grokking:

In 2023, Gromov showed that this can occur even with very small feedforward MLPs:
Could robotics policies exhibit grokking and generalize actions outside their training datasets?
I think the answer to this is no, and I’ll give some reasons for this:
The cases where grokking has been observed are supervised classification-style tasks with very clear objectives, with the test set and training set having very similar characteristics (they are drawn from the same distribution). This is a much more difficult claim to make for robot actions; even the objective is difficult to state.
The modular arithmetic task has an algebraic symmetry structure that can be literally encoded in a neural network (i.e. you could hand-design a network that exactly solves the task). Robotics tasks are much more messy — maybe there is a low-dimensional structure that encodes the solution, but it’s not really obvious that that exists.
In summary, while deep neural networks have demonstrated unexpected generalization capability, this is practically unlikely with robotics action-generation policies. In that situation, the “fancy lookup table” view is appropriate, with the ensuing failure modes described in the Watkins & Tellex post.
The dynamical systems view
A second factor to consider is that robots continually interact with the environment, causing the policy to become a component in a dynamical system. Even smooth, simple dynamical systems can produce very complex and even chaotic behavior:

LLMs which generate their tokens autoregressively (iteratively, one after the other) are also dynamical systems! There is evidence (from a Merrill et. al ICLR 2024 paper) that iterative reasoning genuinely moves an LLM up to a computational class that can solve any polynomial-time algorithm.
They show that this effect is specifically because of the autoregressive text generation, i.e. the dynamical system effect, and not the underlying transformer architecture.
Returning to robotics, in my previous article on embodied intelligence, I talked about Rodney Brooks’ subsumption architecture and its view of the “world being the model” — it doesn’t make sense to even talk about the policy without looking at its interaction with the world.
A robotics policy is always situated in a dynamical system:
observation1 = Sensing(state1) # Robot sensing
action1 = Policy(observation1) # Robot policy
state2 = World(state1, action1) # The dynamics of the world
# ... and repeatDoes this effect help upgrade a robotics policy from a lookup table?
I believe the answer to this is no, and I have an intuitive explanation for why.
In an autoregressive LLM loop, it generates the “scratchpad” itself, and it can address it by the attention mechanism. These two aspects form a remarkable connection to a Turing machine!
A Turing machine is a mathematical model of computation describing an abstract machine that manipulates symbols on a strip of tape according to a table of rules. Despite the model’s simplicity, it is capable of implementing any computer algorithm.
Replace “strip of tape” with “scratchpad,” the “manipulation of symbols” with the generation of reasoning tokens and lookup using self-attention, and it appeals strongly to intuition why Merrill et al found the computational class upgrade.
In contrast, the typical memoryless robot policy doesn’t really get to store arbitrary items on the tape, nor look them up at will. While the policy interacts with the world, there is no guarantee that the observation contains all the ncessary information, leading us to a partially-observable Markov decision process (POMDP). In fact, the classic Kaelbling et al 1998 paper (with over 7000 citations!) shows that the optimal policy for a POMDP is a function of the entire belief state (given the entire observation-action history) and not of the instantaneous observation, and discusses how finite-memory controllers can be extracted in some cases.
There have been recent efforts to imbue robotics policies with the same “scratchpad” capabilities; for example see the Zawalski et al 2024 Embodied Chain-of-Thought paper, and the pi0.7 model, which both generate subtasks before the action.
However, these efforts are in the perception / cognition part of the pipeline; the action head itself is still lookup-table-class and has exactly the limitations that Watkins & Tellex describe in their post. I.e., while you can get generalization at the larger behavioral level, the actions themselves will be interpolations of those in training datasets.
Actually moving beyond lookup tables
The behavior of even simple deep neural networks can be inexplicable by theory (e.g. the Gromov reference above), and even less is known formally about complex robotics policies. In this post, we went over a couple of ways that these policies could potentially sneak up to be more than interpolators of their training data. Still, in practical terms today, most action heads are lookup tables.
However, there are ways to move beyond that! At the end of my embodied intelligence post I described the potential benefits of action generation using reinforcement learning (RL) or model-based control. These techniques have the ability to not only consider embodiment and environment features (the prior article’s point), but also generalize beyond any collected data.
RL generates its own data (though it is typically defined at the training stage) and model-based control will effectively explore and generate new solutions online. There are some approaches in the literature emerging to try and combine these strengths with a foundation model for perception and cognition, but it is far from a common paradigm, and I haven’t seen careful studies of the resulting generalization capabilities yet. It’s an area of research that I believe is quite promising and will be keeping an eye on!
Thanks for reading! If you enjoyed this post, please like (❤️) and restack — it helps others find my writing. Subscribe to receive new posts.







I have to wonder if RL would really be able to move beyond the look-up table interpretation though. Since RL still has the problem of exploration (or coverage). From what I've heard there was a fork in RL for robotics in which there was a question of if pure RL policies should be task-based or if they should be tracking-based. Task-based in the end lost out because it's much harder to solve the problem of exploring enough to learn a good behavior without getting stuck in a local optima. Now it seems like you either need human demonstrations to "warm-start" the policy or you go with RL tracking policies. Perhaps I'm misinterpreting your idea at the end though! I'd love to hear more