I've been going back and forth on an architecture question for weeks and I'd like to hear how you handle it. My current setup: - Vault (Obsidian, Git repo, also a Claude Code project): processes, SOPs, decisions, strategy, research. It's the "brain" of the business, and the agents work from it. - Dashboard (FastAPI + React + Postgres, hosted on Vercel): numbers, P&L, team KPIs, CRM-style modules, internal tools. They live in separate repos. The vault still runs locally on my Mac, but it's moving to a VPS soon. The idea I can't let go of: Put both in one repo. The vault would be the "backend" (knowledge, rules, processes) and the dashboard the "frontend" everyone uses online, including the team. What speaks for it: - One place, one version, no "two sources of truth" - Claude Code sees the knowledge and the code at the same time and can change both together - Usable online instead of being tied to my laptop - The team works through one interface instead of Obsidian + dashboard + Notion - Syncing between the dashboard and the vault stops being a separate project What speaks against it (and why I've held off so far): - They hold two very different kinds of data: text and knowledge on one side, structured numbers on the other. Those usually belong in different stores. - The vault changes constantly because agents write to it. In the same repo, every note change could trigger a deploy. - Access control: not everyone who uses the dashboard should see strategy and decision notes, and the reverse is true too. - Vercel is serverless. You can't just host a writable Markdown vault there, so you need your own server or a database anyway. - Coupling: if one breaks, the other goes down with it. The alternative would be to keep them separate, move the vault to a VPS and connect the two via API/MCP. They'd be connected without being merged. My questions for you: 1. Do you keep your knowledge base (docs/SOPs/vault) and your internal tools in the same repo or separately? 2. If you've made your vault usable online, how did you do it? VPS, Git sync, database, MCP, a custom frontend? 3. How do you control who on the team can see what? 4. Has anyone merged the two and regretted it later, or the other way around?