Editorial

Apache Iceberg has prohibited new equality deletes in version 4 — the one write path that never had to know which file it was changing. The prohibition is forward-only, and every v4 reader must keep applying the deletes that no v4 writer is allowed to create.

Iceberg has prohibited the one write path that never read what it changed, and because the prohibition requires no rewrite, every reader must keep applying the deletes that no writer is allowed to create.

Kubernetes now has a first-class API for AI agent sandboxes, and it reached v1beta1 last month. Read the field comments and it has already decided what an agent is allowed to keep: a session starts fast only while it is anonymous, and a suspension preserves only the part that made it yours.

An agent sandbox is fast exactly while it is interchangeable and durable only across the storage that disqualifies it from being fast, so a Kubernetes CRD now sets the ceiling on what agent runtimes above it can remember between sessions.

A vLLM scheduling proposal filed on 4 September reports, almost in passing, that changing which requests share a batch altered 96.6% of completions byte for byte. That is not a flaw in the proposal — it is what every throughput setting in an inference server has always done, measured for once.

Which other requests share your batch determines the tokens a model emits, so an inference server's scheduler belongs to its output contract rather than its transport, and the only available fix prices determinism as a throughput loss that no architect has been asked to authorise.

Three fixes landed in the x402 SDKs in one week and all had the same shape: hold the whole response until the payment settles. That is not a bug class. It is what a payment protocol does to a serving path when the money is the last thing to happen.

Because x402 settles after the handler has run and reports the result in a response header, getting paid now costs the server the entire response held in memory, and the scheme written for token-metered AI billing is precisely the one that cannot avoid it.

The Model Context Protocol has chartered a working group to give its read-only Resources a write path, complete with optimistic concurrency control. The mechanism is old, modest and correct. It also assumes a client that stops when it is told no.

Services are presented to models as filesystems because models write that interface fluently, and the write path MCP has now chartered rests on a concurrency contract whose client reads refusal as prose.

The Model Context Protocol's July revision deleted the session, the handshake and stream resumability, and moved cross-call state into handles the agent carries in its own tool arguments. It is the trade that made the web scale. The web had a client that remembered exactly; this one does not.

MCP did not remove state when it removed the session — it moved continuity into a model's context window and made re-running the tool the protocol's answer to a broken stream, relocating two guarantees from infrastructure an operator can inspect to a component nobody can.

OpenAI is reported to be buying tens of thousands of Mac minis to teach models to operate desktop software. It is the largest bet yet placed on the idea that the world's systems will never be re-plumbed, and architects are about to file it in the wrong place.

Computer-use agents are a migration technology that the industry is quietly booking as an integration architecture, and the difference will be paid for in systems nobody can specify.