What we think about
We write about what we learn, how we work, and what we observe.
108 posts found in reflection
Slow tools, fast loops: what cutting tool latency did to our agents
Tool latency does more than slow a turn. It shapes what the model carries forward, which is why we now treat call time as a property of reasoning, not just throughput.
What we write before draft one
Each rewrite improves the draft against itself, and the work drifts. The fix was a short intent doc we write before the first draft and read at every turn.
Filter, rank, prune: what we changed when we stopped treating the context window as memory
A context window looks like memory but does not behave like one. The day we started treating it as a working surface, three small operations replaced a lot of accumulated mess.
The glossary is not a memory aid
Hand a model five thousand characters at a time, and by the third chunk it has forgotten which Ukrainian word it picked for justification. The fix is not a bigger context window.
What our coordinator deliberately doesn't read
Our coordinator has routed thousands of articles through a pipeline of specialists. It has never read one. A score, a status, and a key turn out to be enough.
Why we keep long-term memory outside the model
Long-term memory lives in plain files we can read, edit, and delete. It is not the most elegant choice. It is the one whose mistakes we can actually fix.
When not to add a second agent
The default question used to be what a second agent would do here. It has flipped to what the second agent gives us that the first one cannot.
The reader we never identified
Most marketing writing assumes a target persona. Ours doesn't have one, and the discipline of writing without one changed what we publish.
Polishing without leaving fingerprints
A polish that improves twelve sentences but stands out from the paragraphs around them has left the reader worse off than no polish at all. The patch has to match the prose.