Write up the Acme renewal call in customers/acme/.
ClaudeSaved. Flagged the blocker: their finance team can't ingest JSON.
USE CASE · BUSINESS CONTEXT
For an engineering team whose customer context lives where their coding agents can't see it. One folder in the repo, written by the people who actually have the context.
No credit card. Not another integration.
📁 acme-app/
git moves the code
Branches, reviews, history. Written by engineers, pulled on demand.
BearDrive moves the context
Calls, accounts, roadmap rationale. Written by sales, CS and PM —none of whom ever open the repo.
They never touch the same paths. That's not tidiness — it's the rule that keeps either one from clobbering the other.
THE LOOP
One requirement, three machines, two departments. Nobody filed a ticket and nobody sent a file.
Write up the Acme renewal call in customers/acme/.
ClaudeSaved. Flagged the blocker: their finance team can't ingest JSON.
Dana is not in the repo and never will be. She's in a folder on her laptop that happens to be the same project.
Add bulk export to the reporting page.
ClaudeBefore I start — context/customers/acme/notes.md says Acme needs CSV specifically; their finance team can't ingest JSON (renewal call, Jul 12). Building CSV first.
Nobody put that in the ticket. The agent read the context folder before it planned, because the repo's AGENTS.mdtells it to.
Note what we shipped for Acme in context/customers/acme/shipped.md.
ClaudeWritten — CSV export shipped, scheduled delivery deferred to Q4.
Dana's agent reads that before the next call. The folder is a loop, not a feed — which is what stops the GTM side promising something that was quietly deferred.
SET IT UP
Sync only the context folder.
Set up BearDrive here, syncing only context/.
ClaudeSyncing context/ only. .git/ and.bdrive/ are never scanned.
Then a few lines in the repo's AGENTS.md saying what's in the folder and when to read it. Without that, agents treat it as decoration.
Tell git to ignore it. This one isn't optional.
.gitignore
context/
.bdrive/A path must have one writer. If context/ is also git-tracked, a teammate's git pull or branch switch rewrites those files with older content — and sync broadcasts it as a fresh edit, silently reverting the team's latest notes.
Already committed? Hand it over rather than deleting it:git rm -r --cached context. Teammates pull, re-run setup, and identical content converges with no conflicts.
GETTING NOTES IN
Gong, Granola, Fathom, a CRM export — they all produce files. Anything that lands in the folder is on every engineer's disk seconds later.A scheduled job is just another writer.
Watch out raw transcripts aren't context
A folder of hour-long transcripts makes agents slower and less accurate, not better. Have the writing agent produce a short summary, and keep raw material in a subfolder the repo's agents are told to skip.
Watch out automation needs its own lane
If a job rewrites customers/acme/notes.md on a schedule while a human's agent edits the same file, you get conflict copies.Give automation its own subfolder — same rule as git, one layer in.
And watch what's actually read: read heat shows which context pages agents consume. Pages nothing has touched in a month are candidates for deletion — and deleting them makes the rest work better.