{"found":true,"collection":"patterns","library_url":"https://www.grokbotdb.com/library/pat.workspace-as-bus","generated":"2026-09-06T05:32:11Z","citation":["Quote the record id and its source_url (or provenance if there is no URL).","Include last_verified or observed_at when present. Do not present an old date as current.","If tier is community and confidence is low, say so. Do not launder it into a fact.","If the database does not hold the answer, say that. Do not invent Grok Bot product claims.","Contradictions are data: when conflicts_with is present, report both records rather than picking a favourite.","Deprecated and removed records stay visible. They are history, not current guidance."],"record":{"id":"pat.workspace-as-bus","name":"The filesystem is the bus, not the chat","category":"architecture","problem":"Context passed between Bots through conversation is re-read and re-paid for on every turn, and it disappears when a thread ends.","technique":"Treat /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_works":"A 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_use":"Any roster with more than one Bot, and any single Bot whose work spans days.","when_not_to":"Never really. Even a solo Bot benefits from state that outlives the thread.","manual_ref":"1.6","evidence":"reported","attributed_to":"AdiiX","source_url":"https://x.com/adiix_official/status/2095112166579839383","related":["pat.state-on-disk"],"confidence":"medium","first_seen":"2026-09-03","last_verified":"2026-09-05"}}