The filesystem is the bus, not the chat

ProblemContext passed between Bots through conversation is re-read and re-paid for on every turn, and it disappears when a thread ends.

TechniqueTreat /workspace as the internal bus. Research, drafts, evidence, decisions and handoffs are written there. A message between Bots carries a path and one line of context, never the content, so a second Bot resumes exactly where the first stopped.

Why it worksA file is a pointer and a conversation is a payload. Moving state to disk improves reliability and cost at the same time, which is rare enough to design around.

When to useAny roster with more than one Bot, and any single Bot whose work spans days.

When not toNever really. Even a solo Bot benefits from state that outlives the thread.