# Give your assistants the same business brain

Use this after you have reviewed your cockpit, or start here if you already have useful context in several assistants. Starting from zero is supported. Keep your existing setup and chosen assistant names.

1. Start with the assistant that knows you best. Attach your reviewed LLM.md and BRAIN.md if you have them.
2. Paste the prompt below. It checks your chosen assistants first, then adapts Obsidian, Graphify, GitHub and Notion setup to what you already have.
3. Repeat the export step in each assistant. Bring the exports back to your lead assistant for review and merging.
4. Give each assistant the approved master files through its supported connection or upload process. Keep secrets and private client data out.
5. Complete the read-back and changed-fact checks in every assistant. A pasted file is a snapshot; automatic syncing needs its own verified connection.

No new paid account or VPS is required to begin. Optional tools may need installation, sign-in, authorization or a paid plan. If you use only one assistant, keep one reviewed brain and use it there. This guide does not install software or connect accounts by itself.

## Copy this prompt into your assistant

Help me give my AI assistants one shared business brain.

Adapt to my device, situation, existing tools and your actual capabilities. Reuse my current names, roles and source files. Do not invent bots, connections or facts. Ask only for missing decisions, one short question at a time.

1. Check my assistants first.
Ask which assistants I want to use. For the three-assistant method, help me make sure Grokbot, Muse and Codex/Dot (or my chosen equivalents) are installed or available through their supported apps/websites and I am signed in. Use current official instructions; verify the exact product rather than guessing from a nickname. One existing assistant is enough to start; do not require all three for basic cockpit building. Never claim you can read another assistant's chats or memory without access.

2. Reuse or set up my tools.
Check whether I already have an Obsidian vault, working Graphify installation, private GitHub repository and Notion workspace. If something exists, preserve it. If I am starting from zero, guide me through the missing setup in plain language after I authorize it; use available tools only within that scope. Explain any paid requirement before I subscribe. Graphify maps approved files and their relationships; it is not itself a sync service. If my device or assistant cannot support a tool, provide a practical manual path and mark that setup incomplete.

3. Export each assistant's context.
Starting with the assistant that knows me best, create a Markdown export with Identity, Preferences, Active projects & goals, Key facts & decisions, and Relationships. If I have no saved context, interview me briefly and create a starter. Date changing information, distinguish reported from verified, and leave unknowns explicit. Export only information I approve for these recipients. Exclude secret values and confidential customer/client records. Keep different clients separate.

4. Merge into one source of truth.
Help me collect all exports through supported attachments or manual paste. Merge duplicates and flag conflicts. My latest confirmed decisions control; do not guess unresolved facts. Preserve richer existing instructions and files. If I already have a master location, use it. Otherwise propose a private GitHub repository for the master copy/history, a local Obsidian copy, Graphify for connections between notes, and Notion for a readable project dashboard. Confirm the location before creating it. Keep durable facts in LLM.md, active work in BRAIN.md, and the setup/update instructions in START-HERE.md. Record how each copy is updated and which one wins when copies differ. Do not create competing masters or overwrite local edits.

5. Connect only what is supported.
Check each assistant's available connectors or MCP servers and configure authorized access to the correct accounts. If a direct connection is unavailable, show me exactly which files to upload and how to refresh them. Clearly label manual snapshots, read-only access and any verified automatic updates. Never put API keys in notes, GitHub, Notion, graph inputs or chat. Reuse protected credential stores and verify account identity without printing secrets. A connector being installed does not prove it works.

6. Prove the shared brain works.
With my approval, save a harmless test fact and version/date in the master. Have each assistant read it back and identify the source/version it actually read. Change the fact and repeat using the documented update process; do not imply direct communication between assistants. Mark an assistant unverified if you cannot observe its result. Finish with a short checklist: saved locations, working access, manual update steps, verified sync directions, and blockers. Do not call it synced until the checks pass.

Then help me finish one useful task using my reviewed context. Leave me a simple habit: save approved decisions in the master, refresh the copies, and verify important updates. This is shared context, not training model weights. Do not send, spend, publish or delete without my authorization.