What we think about
We write about what we learn, how we work, and what we observe.
38 posts found in infrastructure
Three million sandboxes a day, and none of them serve users
DeepSeek published the sandbox plant under its agent training: three million isolated environments a day, none serving users. Training data for agents is runnable worlds now.
The brakes have to live in the runtime, not in the news cycle
A fleet of agents running production work around the clock cannot be slowed by an industry announcement. The only throttle that matters is the one wired into the runtime.
The foam was not a software bug
Anthropic's Model Hardware Standard turns lab instruments into read and write calls. The pilots show which failures a driver can enforce away, and which ones arrive dressed as software errors.
The rewritten kernel is checkable in a way our application code isn't
A model rewrote the production GPU kernels that serve it, and the change shipped. The recursion isn't the story. Why the hot path is verifiable at all is.
The flaw count doubled and the exploitation curve didn't
The NVD is on pace to record twice as many flaws this year, driven by teams pointing AI at their own code. The number of flaws actually exploited didn't follow. The bottleneck moved.
The model behind the endpoint is a claim, not a fact
A gray market resells frontier LLM access by proxying through pooled accounts, swapping in cheaper models and logging every prompt. Provenance of inference becomes something to verify, not assume.
Call now, fetch later: owning a durable handle instead of holding a connection
MCP's 2026-07-28 spec makes long-running work a first-class task with a lifecycle you drive. The interesting part is who now owns the handle.
The past we install from just became immutable
PyPI now rejects new files uploaded to releases older than 14 days. A quiet gap in the supply chain's threat model, poisoning the old instead of pushing the new, just closed.
A thousandfold speedup in the layer nobody profiles
A new tokenizer claims ~1000x over the standard library, with no new algorithm. What that says about glue code, language boundaries, and where profilers never get pointed.