The Frontier LLM
A composite blueprint of the open-weight frontier: hybrid or compressed attention, ultra-sparse MoE, widened residual streams, FP4-native training and serving.
20 components, 2026-11
ArchDiff keeps one reference blueprint of how state-of-the-art LLMs and agents are built, current as of November 2026, with every component explained at research depth. Each real model, and each improvement a member proposes, is shown as a diff against it.
--- frontier-llm@2026-11+++ deepseek-v4-1-flash@2026-09
23 of 27 components unchanged+0~3−1
blueprints/
Two composite blueprints of the November 2026 frontier. Select any component for how it works, why it won, its trade-offs and its sources.
A composite blueprint of the open-weight frontier: hybrid or compressed attention, ultra-sparse MoE, widened residual streams, FP4-native training and serving.
20 components, 2026-11
The long-horizon, tool-using agent harness you would build in November 2026
18 components, 2026-11
models/
Every profiled model drawn on the blueprint: what it keeps, what it does differently and what it leaves out, cited to its own report, config or code.
DeepSeek, September 2026
DeepSeek-V4.1-Flash552B + 196B Engram total, 16B (8B in prefill) active
Causal encoder-decoder MoE: decoder reads encoder-projected KV, CSA2 shares KV across layers, FP4 KV at 890 B/token, Engram, DSpark.
+0~3−1
Thinking Machines Lab, July 2026
Inkling975B total, 41B active
5:1 sliding-window/global GQA with a learned relative-position bias instead of RoPE, short causal convs, encoder-free image and audio.
+0~5−3
Moonshot AI, July 2026
Kimi K32.8T total, 104B active
93 layers of 3:1 KDA / gated MLA with no positional encoding, Block Attention Residuals and a 16-of-896 latent MoE in MXFP4.
+0~5−3
NVIDIA, June 2026
Nemotron 3 Ultra550B total, 55B active
Mamba-2 does most of the token mixing, 12 NoPE GQA layers anchor it, and LatentMoE routes 22 of 512 experts in a 2,048-dim latent.
+0~4−7
proposals/
Think a component should be different? Change it on the diagram and make the case. Good diffs get merged.
Open a proposal
Pick any component and replace it, add something after or alongside it, or remove it. Say what it fixes, what it costs and which papers or results back it.
Members vote
The diagram shows your change in place, so everyone sees exactly what would be different.
An AI reviewer checks it
Once it has enough votes, the reviewer opens the cited sources and checks every claim against them.
Approved diffs are merged
The change becomes a commit in the blueprint's history, and any commit can be reverted.
Loading proposals…
One email a month: what changed in the blueprints, newly profiled models and the proposals that were merged. Read past changes