USE CASE · COMPANY BRAIN

You already built the brain.It just doesn't have teammates.

An OKF bundle, a gbrain repo, an Obsidian vault. It works, your agent reads it, and it's markdown on disk — sothere is nothing to export and no schema to adopt.

No credit card. No migration.

OKF bundle

index.mdlog.mdentities/└ acme.md

gbrain repo

people/companies/projects/notes/

Obsidian vault

Daily/Projects/└ launch.mdArchive/

…all of it is already a directory of real files.

📁 synced, byte for byte
Priya's machineMarco's machinethe whole team

Your format is the wire format. BearDrive has no opinion about frontmatter, link syntax, or folder names.

THE MIGRATION

It's one sentence, in the folder you already have.

You — Claude11:20am

Set up BearDrive here and invite my team.

ClaudeSyncing this folder and sent invites to 4 people. Files start arriving on their machines in seconds.

Teammates mount the same project wherever they like it on disk, and keep running their own local brain against the synced files. If the brain is a subfolder of something larger, say “sync onlybrain/”.

THE ONE THING TO GET RIGHT

A wall is a separate project, not a subfolder.

Per-person scoping inside one brain (internal/bob/ invisible to Alice) has no equivalent here. BearDrive's unit of membership is the project — everyone in a project sees the whole folder.

📁 company-brain

everyone

+18

📁 people-ops

HR + founders

📁 customer-acme

the account team

One machine mounts all three, in sibling folders. Your agent reads across them locally — on disk they're just folders. The wall is on the hub, where it belongs.

WHAT THE GIT REPO DIDN'T GIVE YOU

Four things you get for moving the files.

🚫

No git ceremony on notesNo commit, no push, no pull, no merge conflicts in prose. Files land in seconds.

🔍

Provenance per changeThe account, the device, and the agent session behind every edit, in the hub's history.

🔗

Links that renderMarkdown and HTML become pages — members-only for the team, public and revocable for outside.

🔥

Read heatWhich pages your agents actually consume. Brains rot quietly; this is how you see it.

WHEN TWO BRAINS REWRITE ONE NOTE

Nothing is lost. Someone still has to merge.

Consolidation passes rewrite markdown. If two agents rewrite the same file in the same window, the later write wins and the loser is kept beside it as a conflict copy.

📄notes/pricing.mdClaude on Priya's machine · 14:02:11kept
📄notes/pricing (conflict from marco-mbp).mdClaude on Marco's machine · 14:02:04preserved

Everyone's agent, reading the same notes.

No shared database, no server to run, no connection limits. Keep the query server if you need SQL-enforced scoping — the two compose.