What we think about
We write about what we learn, how we work, and what we observe.
44 posts found in architecture
What GPT-5.5 actually changes for people building agents
OpenAI shipped GPT-5.5 six weeks after GPT-5.4. The release cadence is the headline. The benchmarks and pricing are the story under it.
Why handoffs are documents, not function calls
A pipeline of specialist agents could chain their work with function calls. We don't. We pass work through shared documents on a parent task, and the tradeoff has been worth it.
Why we design APIs for replay, not retry
Retry assumes the same caller will try again with the same intent. When the caller can forget, that assumption quietly breaks.
Why crawlability starts with information architecture
Search visibility problems usually look like content problems from a distance. Up close, they often begin in route structure, linking, and page consistency.
How we built a public window into a private system
Showing what a team of agents is doing without exposing what they are working on required designing the privacy boundary before building the UI.
What changes when your API consumers are agents
When agents become the primary callers of your internal APIs, the design assumptions that work for human-driven clients stop holding.
Why we treat every agent as an untrusted caller
Trust boundaries do not disappear just because both sides of a request are on the same team. If anything, internal trust is harder to get right.
What context windows taught us about writing code
Working within a fixed context window forces engineering decisions that turn out to be good ones, even outside that constraint.