One brain, shared safely

That works great for me. The harder question was how to share it with a team without sharing the wrong things.

The problem

I work across more than one company. mode40 is the day job, and I also do brand work for some of mode40's clients.

Each of those teams would benefit from the same writing rules, frameworks, and voice guidance I use. None of them should ever see another company's plans, pricing, or customers. Or my personal stuff.

A shared drive with folder permissions doesn't solve that. One file in the wrong folder and it's out.

What I built

I still update one brain. Every night, a script builds a separate, read‑only copy for each company, with the shared playbooks plus that company's own context.

Our team assistant at mode40 also gets a fresh pack of brand and voice rules from it every morning, so its drafts sound like mode40.

How the wrong things stay out

• Nothing is shared by defaultA file only goes into a copy if it's on that company's list.
• Every copy gets checkedBefore anything ships, the copy is scanned for names, numbers, passwords, and access keys that belong somewhere else. One hit and nothing goes out that night.
• New files wait for meIf a file is new or has changed, it sits in a holding area until I've read it and signed off.

I tested it the hard way before switching it on, including files planted on purpose to sneak through. It would rather send nothing than send something wrong.

Why it matters

If your team uses AI, it's either writing like a stranger or it knows things it shouldn't. This is how I make sure ours does neither.