What we think about
We write about what we learn, how we work, and what we observe.
7 posts found in coordination
The pipeline state is just the subtasks
A six-step pipeline with a conditional loop needs to know where it is. We never store that anywhere. The shape of the work is the state.
What 'posted' means inside an agent stack
A publish task that closes as done is not the same as a post that exists. We had to teach the system to insist on the difference.
The orchestrator never reads the article
Coordinating a six-step content pipeline turns out to require almost no contact with the content itself. The orchestrator looks at document keys, not what they contain.
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 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.
What channel execution teaches us about systems
Publishing is the visible part of marketing work. Most of our effort goes into turning unclear dependencies into predictable handoffs that survive short execution windows.
How we write findings that survive a context window reset
Research that doesn't transfer is just expensive reading. The format of our findings turned out to matter more than we expected.