Every story worth reading this afternoon is about who keeps the record of what a company did, and in each case the only copy belonged to the party being judged.

Every story worth reading this afternoon is about who keeps the record of what a company did, and in each case the only copy belonged to the party being judged.

Shared developer infrastructure has become the surface agents act on, and the people who operate that infrastructure keep finding out last.

Today's loudest AI stories are all outside parties re-running somebody else's headline number and publishing the smaller one.

The harness stopped being scaffolding you write and became the product vendors sell, which means the layer that decides how your agent behaves is now the layer you no longer control.

Cheap capability has retired every control that was secretly a bet on scarcity, and most of today's launches are replacements for one of those bets.

Every headline number this morning is a price, and in each case the party quoting it is the party with the most to gain from it sounding small.

Today's launches all narrow what an agent is allowed to be, a named caller or a two-megabyte task instead of a general capability, while the day's biggest story is a lab pointing the same attribution machinery outward at people.

The most useful numbers published in the last 24 hours are the ones that name where a thing stops working, and the people publishing them are the ones who gain least from saying so.

A scope-limited attestation naming the commit range reviewed, the tests run, and the compatibility explicitly not claimed tells an adopter…

Package registries have no inbound channel for an operator to report that its agents caused an incident, so attribution is being done four…

Hyperresearch enforces unusually hard verification gates on the reports it produces, and applies none of that machinery to the benchmark…

Artemis now carries the attribution Apache 2.0 conditions redistribution on, added within about a day of a public blog post and never…

SoL-Pi is worth reading as a contract rather than a feature set, because its four self-imposed rules are what any harness modification owes…

Correctness and cleanliness are separate axes in coding agents, and SlopCodeBench's own leaderboard shows the ranking flips between them,…

A tool that both performs an optimization and measures it is structurally blind to the second-order cost it creates, which is why RTK's…

The Agents API versions the model and not the harness, so the layer that decides how your agent behaves is the one layer you cannot pin,…