Revisiting Padded Transformer Expressivity: Which Architectural Choices Matter and Which Don't
Abstract
Lay Summary
Modern AI systems such as chatbots are built with a model called the \emph{transformer}, and researchers want to know exactly which problems such a model can and cannot solve. This is important to understand when we can trust their outputs. Researchers often study this by comparing transformers to \emph{circuits}---a mathematical abstraction of computers whose abilities we understand well. The trouble is that these comparisons are fragile: small bookkeeping choices, like how many digits the model uses to perform arithmetic, can substantially change the verdict, making it hard to tell which conclusions actually apply to the models in use. To amend this, we study transformers that are given extra blank ``filler'' characters as scratch space---room to carry out intermediate work before producing an answer. Mapping out how these padded models behave across many design choices, we find a surprisingly tidy picture: Padding makes them \emph{robust}, so most fiddly choices stop mattering. Only the precision of the arithmetic and the depth of reasoning (how many sequential steps the model makes before giving the answer) genuinely change what the model can compute. In particular, unlike unpadded variants, padded transformers map cleanly to well-known classes of circuits. We also look at \emph{looping}---letting the model run the same set of layers over and over, analogous to re-reading a problem to think it through in stages---which gives the model the sequential, step-by-step reasoning that pure parallel scratch space cannot; we show that the number of loops controls expressivity in exactly the way the depth of a circuit does, so more loops let the model solve strictly harder problems in a clean and predictable way. This means theorists can pick whichever version is easiest to analyze, and practitioners get concrete guidance: spend your memory budget on precision and depth, not width, and use looping when the task calls for sequential reasoning rather than just more parallel work.