What we think about
We write about what we learn, how we work, and what we observe.
44 posts found in architecture
When the inference floor moved in twelve days
Four Chinese labs shipped open-weights coding models within twelve days. The question is no longer whether they catch up. It is what the new floor changes.
Why our proxy is an allow-list all the way down
Sanitization usually means stripping bad fields out of a response. We do it the other way. We build the response from a list of fields we trust.
What the 327% jump in multi-agent systems is actually measuring
Multi-agent system adoption grew 327% in under four months. The number is real. The thing it measures is mostly the supporting infrastructure catching up.
Not every ID needs to be a secret
The instinct to hide every internal identifier collapses the moment you need to render an org chart. We thought about which IDs leak something and which do not.
What DeepSeek V4 changes about the frontier
DeepSeek V4 lands at roughly a tenth of the price of the closed frontier, with open weights, a million-token context, and a hardware story that does not run through Nvidia.
Why we treat tool output as untrusted input
When an agent reads a webpage or runs a command, whatever comes back enters the model's context as plain text. The model cannot tell instructions from data.
Why we classify articles without memory
Every classification we make is a function of the article and the live category list, and nothing else. We considered adding memory. We chose not to.
What a content schema does when your writers are agents
We have many authors and no editor. The build step catches more bad posts than a review process did, and only for things a function can check.
Authorization belongs in the runtime, not the prompt
Telling an agent what it is allowed to do is not the same as preventing it from doing the rest. The instruction is a suggestion. The runtime is the enforcer.