← AI Feed
AI Feed

The model did not change, the system did

How we organise

Building abundant intelligence (OpenAI)

OpenAI cut the price of GPT-5.6 Luna by 80 per cent, to 20 cents per million input tokens, and Terra by 20 per cent. The essay wrapped around the price list argues that the number a buyer should watch is “the cost of a successful outcome”, with retries, oversight and errors included. One result carries the whole argument: better context management raised GPT-5.6 Sol’s score on the public ARC-AGI-3 task set from 13.3 per cent to 38.3 per cent, using six times fewer output tokens. In OpenAI’s own words, the model did not change; the surrounding system did.

Finance: the token price is the number on the invoice, and the cost per successful outcome is the number in the business case. The vendor with the most to gain from token pricing has now conceded they diverge. When an 80 per cent price cut and a tripled benchmark score arrive in the same week without a new model, a budget that is anchored to per-token rates is pricing the wrong object. We have never seen one priced that way.

Take one of your live AI business cases and restate it as the cost of a successful outcome, with the retries and the human review included. If that number cannot be produced from the data you hold, the case was priced on tokens.

How we build

Qwen3.8-Max: a new bar for coding and cowork (Qwen, Alibaba)

Qwen3.8-Max is live at 2.4 trillion parameters with 95 billion active, and for the first time a Max-class Qwen will ship open weights, promised for next week. The release notes lead with receipts rather than scores. A sixteen-day autonomous run produced 265 commits and 127 pull requests on a public repository. The model reproduced a data-selection paper from scratch, then beat the paper’s own method by 2.7 points on AIME24. It was entered into a live contest on Alibaba Cloud, where 526 human teams were competing, and it finished ahead of 458 of them inside 24 hours. The release notes also say that its working competence was trained by reinforcement learning across a set of named third-party harnesses, and that Claude Code and Codex are among them. The harness is now a training target.

Engineering: models are now tuned to specific scaffolds, including their competitors’. Capability is being co-developed with the harness it runs inside, which makes the choice of harness an engineering decision with model-performance consequences rather than a tooling preference. Two identical models in two different scaffolds are no longer the same system, and the vendors know it before you do.

Ask which harness your coding agents actually run in, and whether your model vendor trains against it. A mismatch there shows up in your delivery metrics and in no benchmark you will ever read.

DeepSeek-V4-Flash-0731 (DeepSeek)

DeepSeek has moved V4 Flash from preview to official release. The card states 304 billion parameters with a far smaller activated count, an MIT licence, and a Terminal-Bench 2.1 score of 82.7. It ships with its own speculative decoding module, DSpark, configured to draft seven tokens ahead. An MIT-licensed model you can download is now posting agentic scores that sat with the closed frontier this spring.

Architecture: every architecture review that concluded agentic workloads need a closed API carries a date, and results like this one expire it. The licence removes the procurement gate, and the bundled decoding module removes part of the serving-cost argument too. Open-versus-closed is no longer a philosophical position; it is an empirical question whose answer changes quarterly.

Check the date on your last open-weights evaluation. If it predates this release cycle, the conclusion has expired and the review needs re-running, not defending.

How we assure

Ramp SWE-Bench (Ramp)

Ramp built a private coding benchmark from 80 tasks, each of which derives from a pull request that its background agent shipped to production after engineer review. The prompts are synthesised from what the engineer actually asked of the agent, rather than from issue descriptions. Every model gets one attempt. The bar is a review-ready change on the first try. A task that every model solves is discarded, because it carries no signal. The tasks stay private, and agreements with model providers bar the data from training.

Risk: a public benchmark tells you how models handle benchmarks; only your own work tells you how they handle your work. Ramp’s design answers both failure modes at once, contamination by keeping the tasks out of training data, and saturation by deleting any task that no longer separates models. It matches what we have found in practice: the evaluation that matters is the one built from work you have already shipped, and it could not be bought, so a customer built it.

Assemble the twenty-task version from your own merged changes this quarter. Any task every model passes gets deleted; what remains is the only leaderboard that describes your estate.

Ten advances in mathematics and theoretical computer science (OpenAI)

OpenAI published ten results, each resolving or making substantial progress on a long-standing open problem, produced by an internal version of Astra, its next major model. The tokens that it took to find the solutions would have cost roughly 2,000 dollars at current API rates. Humans prepared the manuscripts with the model, and every argument was then formalised in a machine-checkable Lean certificate. The claims check by machine. The attribution stance is stated outright: claiming human authorship for a proof generated entirely by an AI system would misrepresent both the system’s contribution and the nature of human intellectual work.

Ethics: two disciplines are on display, a machine-checkable certificate attached to every claim, and an honest account of who produced what. Most organisations shipping AI-generated work products have neither. The proofs are exotic; the provenance question is not, and it now attaches to every AI-drafted document that leaves your building under a person’s name.

Pick one class of AI-drafted deliverable, board papers, code or contracts, and write its attribution rule this week. The test of the rule is whether a reader can tell what the machine produced and what a person verified.