That playbook treats /workspace as the internal bus, holding research, drafts, evidence, decisions and handoffs so a second Bot resumes exactly where the first stopped, rather than passing context through chat.

NotesIndependent restatement of the state-on-disk rule, which the vendor docs support and which is also the cheapest option per the cost records.

stop passing important context through chat - research, drafts, evidence, decisions and handoffs live inside /workspace so every Bot can continue exactly where another stopped