Founder OS - Infrastructure
Shipped Changelog Diagrams
AI Context Architecture
Real-time shared memory for AI-augmented operators. Supabase as the single source of truth. 22 tables. 438 tests. Operator-scoped API keys.
Live Metrics
--
Operators
--
Projects
--
Syncs (24h)
--
Collisions (24h)
--
Memories
--
Avg Push
--
Avg Pull
Operators
Loading...
Working On (last 8 hours)
Loading...
Live Activity Feed
Loading...
System Architecture
How It Works
Session Start
Git pulls latest sync code from GitHub, then pulls context from Supabase. CLAUDE.md, rules, memories, commands, skills, projects, and journals all materialize to your machine.
While Working
Claude Code has full context: who you are, what you're working on, what the team is doing. 80+ skills available via MCP. Session journals track your work automatically.
Session End
Auto-pushes your changes to Supabase and commits to GitHub. Journal entry logged. Next operator who starts a session gets your updates.
Three-Tier Memory
Global
Org-wide: brand standards, API refs, methodology. All operators receive.
Operator
Personal: feedback, preferences, project notes. Operator-scoped. Never bleeds to other operators.
Project
Scoped to working directory. Shared across operators on same project.
Operator Onboarding
Each step depends on the previous. Do not skip steps.
Admin Side (Don runs these)
# 1. Register operator + seed identity config
python3 run_sync.py add-operator nick 'Nick' 'Content / Social'
# 2. Store their FOS Skills API key
python3 run_sync.py set-skills-key nick fos_k_...
# 3. Generate their auth token (365-day JWT)
python3 generate_operator_token.py nick
# 4. Add as GitHub collaborator to Matt-Gray-Founder-OS/fos-context
# 5. Send them the token + operator setup instructions below
Operator Side (new team member runs these)
Prerequisites
Python 3.9+ installed (brew install python)
Node.js installed (brew install node)
Claude Code CLI installed (brew install claude-code)
GitHub account created + collaborator invite accepted
Step 1: GitHub SSH Keys
# Generate key pair (press Enter for all prompts)
ssh-keygen -t ed25519 -C "your-email@founderos.com" -f ~/.ssh/id_ed25519 -N ""
# Start SSH agent and add key
eval "$(ssh-agent -s)" && ssh-add ~/.ssh/id_ed25519
# Copy public key to clipboard
pbcopy < ~/.ssh/id_ed25519.pub
# Paste at: github.com > Settings > SSH and GPG keys > New SSH key
# Test connection (should say "Hi username! You've successfully authenticated")
ssh -T git@github.com
Do not proceed until ssh -T succeeds.
Step 2: Clone + Bootstrap
git clone git@github.com:Matt-Gray-Founder-OS/fos-context.git ~/dev/fos-context
cd ~/dev/fos-context
bash bootstrap.sh nick
# Paste the token from admin when prompted. That is the only prompt.
Bootstrap automatically: creates credentials, verifies operator exists, seeds identity config, pulls all shared context, registers your machine, installs 80+ skills via MCP server, and runs a health check.
Step 3: Restart Claude Code REQUIRED
Bootstrap installs two systems that require a fresh Claude Code session to activate:
Context Sync Hooks - auto-pull on session start, auto-push on session end
Founder OS Skills MCP - 80+ skills via MCP server (velocity-hooks, brand-positioning, etc.)
If Claude Code was already running, quit and reopen it. The MCP server and hooks only load on startup.
Step 4: Verify Everything Works
Context Sync:
1. Open Claude Code in terminal
2. You should see SYNC_OK in the startup output
3. Type /start - confirm your name in the Identity section
Skills MCP:
4. Ask Claude: "What Founder OS skills are available?"
5. Claude should call list_founder_os_skills and return 80+ skills
6. If you see "Unknown tool" or no MCP tools, restart Claude Code again
Troubleshooting:
- No SYNC_OK at startup: run cd ~/dev/fos-context && python3 run_sync.py health
- Skills MCP not connecting: run cd ~/dev/fos-context && python3 run_sync.py setup-skills
- Identity shows wrong name: tell Don, identity config needs repair
Dependency Chain
GitHub account > SSH keys > collaborator invite accepted > git clone works
Admin registers operator > token generated > bootstrap has valid auth
Admin stores skills key > bootstrap fetches it > MCP server installs with zero prompts
Python + Node + Claude Code > bootstrap installs dependencies > hooks + MCP registered
Total time: ~5 minutes from invite to working system.
FOUNDER OS CONTEXT ARCHITECTURE - Auto-refreshes every 60s - --