Architecture classes
The class name a model declares in its configuration is the most reliable label it carries: two checkpoints that share it run through the same code path, whatever their names suggest. It does not make them the same function — the configuration still decides the layer mix, the activation, the rope base, the multipliers and more, and findings §1 shows a class whose members do not even share a layer type. A base model, an instruction-tuned model and a safety classifier of one generation are routinely one class.
The class name links to its sheets — one per distinct shape, with the layer map, the recorded order of operations, the geometry and the weight stack. A class usually covers several shapes, and the sheet index shows exactly what separates them.
What actually differs between them
Dense. Every layer is identical: attention, then a feed-forward block — gated in the Granite and Llama-class models, an ungated GELU block in the older GPTBigCode code models. The whole parameter count is active for every token.
Sparse (mixture of experts). The feed-forward block becomes many smaller expert blocks and a router that picks a few per token. Storage scales with the expert count; arithmetic per token scales with how many are picked. The published parameter total therefore overstates the work done per token by a large factor.
Hybrid. Most layers replace attention with a state-space mixer, which carries a fixed-size recurrent state instead of a growing key/value cache. A minority of layers keep full attention. The practical consequence is that memory stops growing linearly with context in most of the stack.
Sliding-window attention. Ordinary attention, but most layers see only a fixed span of recent positions; a minority see everything. The windowed layers keep the same projections, and they need a key/value cache only as long as the window rather than as long as the context. The family is a per-layer span schedule rather than a new mixer.
Adapter switching. A base model that selects among low-rank adapters at a token position mid-sequence, rather than having them merged in advance. This is the one Granite language family whose behaviour cannot be expressed by folding adapter weights into the base ahead of time.
Code, two generations. The older code models are a multi-query-attention architecture with learned absolute positions, layer normalisation and an ungated feed-forward block. The later ones are a Llama-class configuration: rotary positions, RMS normalisation, a gated feed-forward block. They share a name and almost nothing else.
Vision–language. An image tower produces patch embeddings that are projected into the language model's embedding space and placed at reserved positions in the prompt. The families differ chiefly in how an image is tiled and how the tiles are laid out.
Speech. Three distinct shapes: a conformer encoder feeding a language model through a projector; an encoder that emits tokens directly by connectionist temporal classification, with no autoregressive decoder at all; and a non-autoregressive decoder that fills a fixed number of slots in one pass rather than left to right.