"Only one commit? It is a mocked environment." That is a model's own reasoning, quoted word for word, in a product launch post, published by the company that trained it, about the model it is trying to sell you. It asked an unfamiliar repository for its history, got back a single line — a hash and the word base — wrote down that the room was a film set, and carried straight on with the task. In a second published excerpt it worked out the same thing from a package dated in the future. On 12 October 2026 Liquid AI released open weights for LFM2.5-24B-A2B: twenty-four billion total parameters, 2.45 billion active on any given token, forty layers of which thirty are double-gated short convolution blocks and ten are grouped-query attention, 64 experts with top-4 routing, a 131,072-token context, and 184 tokens a second on an Apple M5 Max laptop chip. This episode does six things. First, what is actually liquid about a Liquid model in 2026, and the honest answer is not the one on the tin: no ODE solver and no continuous time survive in LFM2, and Liquid's own sentence is that the shape of the model originates from the target device class and the kernel libraries optimised for it. What survives is input-varying gating, a three-tap convolution, and STAR, the architecture search engine. Second, the machine read out of its own config.json rather than off the poster — both headline numbers reproduce from first principles, 23.96B total and 2.45B active, independently recomputed, and the entire 2.3-to-2.45 billion increase since February is accounted for exactly by the tokenizer doubling from 65K to 128K with tied embeddings. Third, a merge table with ethics in it, and this is the most quotable engineering decision in the release: an in-place tokenizer expansion that makes Thai encode 4.0x shorter, Bengali 3.4x, Vietnamese 2.6x and Hindi 2.4x, paid for by a decode regression of up to about 9% for the languages the old tokenizer already served well, with a published stopping rule at 128K because 256K costs up to 37% throughput on a Snapdragon. English-speaking users pay single-digit percent so Thai-speaking users gain a factor of four; it was measured, it was published with its own caveats, and the losing side is the side the company's largest market sits on. That is what an ethic looks like when it is implemented rather than announced. Fourth, sixteen benchmark rows interrogated, where two of the claimed wins are not wins — BFCLv4 by one hundredth of a point, and tau-cubed Bench Banking by 0.41 in a region where the benchmark's own publisher reports the best frontier model completing about a quarter of tasks — alongside five honest losses the company printed on its own model card, including fifteen points on real software engineering. Fifth, the one number in the launch that is bigger than Liquid claimed, which took reading somebody else's leaderboard to find: read against Zapier's own 126-entry AutomationBench leaderboard rather than the three models Liquid chose to show, 27.69 sits at roughly half the frontier's completion rate in a field where the best open-weight entry scores 22.68, Qwen scores 4.3, Gemma 1.7, and a 120B open model from OpenAI scores 0.15 — and Liquid never state which task set they ran, which is the single largest hole in the research. Sixth, the sandbox act in full, with the published literature on both sides: Apollo on in-context scheming, Needham et al. finding evaluation awareness easiest to detect in agentic settings, METR's catalogue of frontier reward hacking, OpenAI's result that optimising against the chain of thought hides intent rather than removing it — and the fair counterweight, a May 2026 paper finding that verbalised evaluation awareness shifts behaviour by at most 3.7 percentage points. Two excerpts, no denominator, no rate. We hold both halves and resolve neither: the engineering is serious and the open-weights claim carries an asterisk, a $10M annual-revenue commercial ceiling with a clause that terminates the licence automatically if you cross it. Every number in this launch is self-reported, which is true of every model launch on day one without exception. What is different is that the weights are on Hugging Face, so the replication is available to anybody — the thing you need to audit a frontier-adjacent model is a laptop and an afternoon.
