Constraint is moving from the prompt into the plumbing
How we organise
AA-Briefcase agentic knowledge-work leaderboard (Artificial Analysis)
An independent leaderboard that scores models on knowledge work rather than code. AA-Briefcase runs 91 tasks across four multi-week projects in data science, product management, banking operations and heavy industry strategy. Each task produces a real deliverable, a spreadsheet or a deck or a report, graded on rubric checks plus pairwise analytical and presentation quality. Read inside a single model rather than down the ranking. Claude Opus 5 reads 1720 Elo at maximum effort, 1693 at the next tier down, 1606 below that and 1470 at medium.
Finance: that 250-point range is wider than the gap between Opus 5 at its lowest listed tier and most of the models ranked beneath it. The lever your operating model actually controls, which is how much inference budget a task is granted, now moves the outcome more than the procurement decision everyone is arguing about. Most organisations have a model selection policy. Almost none have an effort budget policy, so the quality of the work is being set by whatever default each team happened to leave in place.
Find out who sets the effort or thinking budget for your AI tasks, and what a tier costs. Nobody at all is the usual answer, and it is the more expensive one.
How we build
The new rules of context engineering for Claude 5 generation models (Anthropic)
Anthropic reports removing more than 80 per cent of Claude Code’s system prompt for its newest models with no measurable loss on internal coding evaluations. The post generalises that into five reversals of advice the industry spent eighteen months codifying. Give the model rules becomes let the model use judgement. Supply worked examples becomes design expressive tool interfaces. Front-load the context becomes disclose it progressively. Repeat the important instructions becomes put the guidance in the tool description, where it is read at the moment of use.
Architecture: the claim with the widest blast radius is that examples now constrain a capable model’s exploration rather than assist it. If that holds, every carefully curated few-shot library in a governed enterprise platform is a liability rather than an asset, and the accumulated instruction debt needs auditing rather than extending. Note what replaces the prose. Not less control, but control relocated into the interface the model acts through, so the constraint stops being something you say and becomes something the tool surface enforces.
Measure the system prompt your platform team ships, in tokens, and ask when each section was last tested for whether it still earns its place.
How we assure
The Stack v3 (Hugging Face Code Research)
The largest open corpus of source code yet released. The training split runs to 15.9 TB across 713 languages drawn from 173 million repositories, roughly 4.9 trillion tokens. The full corpus reaches 113.7 TB across 224 million repositories and 43.9 billion files, with a crawl cutoff of 7 August 2025. Rows are grouped by repository rather than by file, which makes repository-context pre-training possible for the first time at this scale. Licences are detected file by file through ScanCode and propagate through the directory trees. Files that are not permissively licensed are excluded from both releases rather than flagged for whoever comes later. Personal data is redacted on the training split, and the whole thing ships under ODC-By with a public opt-out.
Risk: we would read this for the governance rather than the size. Provenance is handled where the corpus is built, not left as a policy question for whoever trains on it later, which is a template other publishers will be measured against. It settles an argument as well. If your organisation has public repositories, it is now demonstrably inside a frontier training set, and what you can prove about your own code supply chain has stopped being hypothetical. All three items make the same move. Instructions are the weakest control available, because they depend on the thing being governed choosing to comply, so the constraint is going into the structure instead. It is the difference between a policy saying do not touch the credentials and an architecture in which the credentials were never in the container. The caution is that moving constraint into structure only helps if the structure underneath is sound. A context layer sitting on ungoverned metadata is a faster way to be wrong.
List which of your repositories are public, and ask what you could prove about the licence and provenance of the code inside them.