Verification is the constraint, not capability
How we organise
Inside Anthropic: how building software is changing (Gergely Orosz)
Orosz spent time in Anthropic’s San Francisco office and interviewed four people who ship there, so the reporting is first hand. The number everyone will quote is the Bun rewrite to Rust: more than half a million lines, once estimated at 12 months, completed in 11 days for roughly 165,000 dollars of tokens. Verification now consumes more time than implementation, as the actual bottleneck rather than a formality. Projects are capped at a maximum of two engineers, while two-pizza teams, planning discipline and PRDs for complex work all survive intact. Claude Managed Agents still took about six months and still needed re-architecting halfway through.
Talent: we would read the practices thrown out as the ones that existed to coordinate people writing code. The practices that survived were the ones that existed to decide what should be built and to establish whether it works. If you are planning headcount on the assumption that AI removes engineering effort, you have the shape wrong, because it relocates the effort onto the scarcer function. A firm that could not staff good review before will find that constraint binding much harder now, since the thing it was rationing has become the thing it needs most.
Work out what proportion of your engineering time currently goes to verification, and whether that proportion has been rising or falling. Falling, against rising output, means the gap is being banked rather than closed.
Kimi K3 licence (Moonshot AI)
K3 is described everywhere as open weights. The model card is genuinely open; the licence is source-available rather than open source. Any model-as-a-service operator whose group revenue exceeds 20 million dollars over any consecutive 12 months must sign a separate agreement with Moonshot before commercial use. Above 100 million monthly active users or 20 million dollars of monthly revenue, the product must display “Kimi K3” prominently in its interface. Internal use is exempt.
Finance: none of that is unreasonable and Moonshot are entitled to it. The point is that “open weights” has stopped being a licensing answer and become a licensing question, where the answer changes with your revenue. Anyone building a commercial product on a self-hosted frontier model needs a lawyer reading the licence text rather than a summary of it, and the threshold that catches you is a number your finance function already knows.
Take the models your teams have self-hosted and check each licence against your group revenue. The exposure sits with whoever signed nothing, which is usually nobody.
How we build
Six agent harness capabilities for higher model performance (NVIDIA)
NOOA makes the agent a single Python class. Methods are capabilities, fields are state, docstrings are prompts, type annotations are enforced contracts, and a method body of three dots is completed at runtime by a model loop. NVIDIA report 82.2 per cent on SWE-bench Verified with GPT-5.5, at roughly half the token cost of the harnesses they compare against. Tool results pass by reference as live Python objects rather than being serialised into the context window, so no compaction is needed.
Engineering: that last decision is the one we would steal, and it is mentioned almost in passing. As an engineering choice it is a token-efficiency argument. As an assurance choice it is something else. A live object can be inspected after the fact and a compacted summary cannot, because the compaction has already thrown away whatever the reviewer would need. Every harness that summarises its own history to fit the window is quietly destroying the evidence trail, and nobody writes that down as a design trade-off.
Ask what your agent harness does when the context window fills. If the answer is that it summarises, ask what a reviewer would have left to read.
The Regression Tax (arXiv)
Across nearly 6,000 paired runs on two office-automation benchmarks and three model-and-harness stacks, the authors find that the best-performing skill libraries win mainly by regressing less rather than by gaining more. Three mechanisms are named. Skill-description osmosis, where a skill alters the model’s behaviour merely by sitting in context even when it is never invoked. Then grounding displacement, and verification displacement, both of them cases where the presence of a procedural skill crowds out the model’s own checking of its work. They conclude that reliability depends more on grounding and on verification than it does on which skills you happened to pick.
Engineering: that lands directly on how these libraries get built in practice, which is additively. Someone writes a skill, it helps, it stays. Nobody measures what it cost the runs where it was irrelevant, because nobody instrumented for a regression they were not expecting. A skill library needs a removal process as much as it needs an addition process. Almost none of them have one.
Count the skills, prompts or tools loaded by default into your agents, and find out when one was last removed. Never is the usual answer, and this paper prices it.
How we assure
Discovering cryptographic weaknesses (Anthropic)
Anthropic’s Mythos preview cut the small-key security of HAWK, a NIST post-quantum candidate, from 2^64 down to 2^38. It took about 60 hours and roughly 100,000 dollars of API cost, and it halves the key strength, removing the size advantage that made HAWK attractive. Separately the model invented a fingerprint they call a Möbius Bridge, speeding the best known seven-round meet-in-the-middle attack on AES-128 by between 200 and 800 times. Neither result touches production systems. Anthropic report that the AES result took Mythos about a week to conceive, and took two researchers close to a month to gain confidence it was correct. They then state plainly that human researchers may become bottlenecked on studying and validating these results.
Risk: we read this as a vendor publishing a finding against its own commercial interest, and as the clearest statement anyone has made of where this is going. The output side scales and the checking side does not, because checking requires the specific expert who can hold the problem, and that person does not become available faster because the model got cheaper. One detail matters for anyone designing multi-agent systems: the HAWK result came from a harness where one worker prematurely rejected the winning idea and a second recovered it. The discovery was a property of the pair. So was the near miss.
Name the people in your firm who could validate your highest-value AI output. If the list is one name long, that is your throughput, whatever the model does.
Anthropic’s position on open-weight models (Dario Amodei)
Worth reading directly, because the summary circulating is wrong. Anthropic state they have never advocated banning open-weight models, and describe such models as a public good where they lack dangerous capabilities. What they back is chip export controls, a crackdown on industrial-scale distillation, and mandatory pre-release safety testing for all sufficiently capable models, open or closed alike. What they dispute is the claim that open weights necessarily help defenders more than attackers. Two things are being conflated across the coverage. The open-weights industry letter has Google and OpenAI as signatories, with Anthropic absent. NVIDIA’s Open Secure AI Alliance, launched with roughly three dozen partners including Microsoft, IBM, Red Hat, Hugging Face and the Linux Foundation, has none of the three.
Ethics: anyone merging those two rosters will state something false in either direction, and the alliance list updates live, so a hard number will be wrong by the time it is published. The alliance’s own supporting evidence is the strongest part of its case. Hugging Face analysed more than 17,000 recorded actions during July’s intrusion on a self-hosted open-weight model, because the closed tools refused the forensic work. That is an argument about what stays available under adverse conditions rather than an argument about ideology. It is much harder to wave away.
Before your firm takes a public position on open weights, check which document you are actually endorsing and who else has signed it. The two rosters in circulation share almost nobody.