How to use this
The OS in five minutes — and the workflows that get the most out of it.
1The mental model
The OS has five layers. You mostly touch the command center (this UI); everything underneath is plumbing that skills and agents use.
The vault is the source of truth (markdown). graphify turns your repos and business docs into queryable graphs. This UI is the single screen that shows and uses all of it — you never edit files to use it.
2What each screen does
3Get the most out of it
A · Query graphs instead of re-reading repos (your token-saver)
When you need to understand a codebase, ask the graph first — in the query box, or a terminal. It traverses the prebuilt graph (cheap) instead of an AI reading dozens of files (expensive). Use it before any “how does X work” task.
cd ~/Projects/rentijer graphify query "how does eVisitor check-in work"
B · Add a new project (~10 min)
1. Graph the repo (free — no API key needed):
cd ~/Projects/<new-repo> graphify . --obsidian --obsidian-dir ~/neviox-os/vault/graphify/<new-repo>
2. Add one entry to command-center/os.config.ts → projects[] (copy an existing block). 3. Refresh:
cd ~/neviox-os/command-center && bun snapshot && bun dev
C · Keep graphs fresh after you code
cd ~/Projects/<repo> && graphify . --update cd ~/neviox-os/command-center && bun snapshot
D · Capture work as you go
Drop a line into vault/projects/<project>.md when you ship or learn something. That’s the raw material the Publicist agent turns into LinkedIn posts once the growth module is switched on.
4Deploy / redeploy
The app is portable — it reads bundled data, not your local filesystem — so it runs on Vercel unchanged. The deployed site is a read-only mirror; when graphs or the vault change, refresh and redeploy:
cd ~/neviox-os/command-center && bun snapshot git -C ~/neviox-os add -A && git -C ~/neviox-os commit -m "refresh snapshot" # then redeploy (Vercel)
Keep the repo private — the vault and graphs contain client/business detail.
5The rules it runs on
Full detail lives in CLAUDE.md.