Keep shared AI context in a single-writer folder
At a glance
A user organized a shared Google Drive knowledge folder for Grok Bot and Claude with a human-approved update loop. This workflow is listed under Life admin, Documents.
SourceBuilding a tool for these workflows? See weekly rates.
What they did
1) Create one Google Drive folder as the common context for Claude, Grok Bot and other AI tools. Set a single-writer, multiple-reader working rule: the tools may read the files but should not change existing ones. 2) When an assistant discovers a new fact, have it create a separate file in an inbox rather than editing the main summary. Add a date and source to each fact. 3) Each week, have Claude review the inbox and propose updates to the main summary; the user decides which changes to accept, then the updated file replaces the old one. 4) Mark outdated facts with an end date instead of deleting them, and connect a new AI tool to the same folder when it is added.
How it went
The author says the shared context reduced the need to explain the same things repeatedly.
Worth knowing
The post describes a working convention, not a technical access-control setup. The proposed local agent is a future addition.