Systems — what handles what
KairOS, the reminder bot, Metis, and the scheduled jobs.
Atlas orchestrates several dedicated systems. The routing question is always: "which system owns this kind of information?"
The map
| System | Owns | How you touch it |
|---|---|---|
| The Vault (Obsidian) | Company dossiers, project blueprints, source docs, watch/buy lists | Via Atlas in Discord, Obsidian on desktop, or vq in a terminal |
| KairOS | Tasks, calendar, leads pipeline, budget | Web app, or ask Atlas ("create a task…", "what's today?") |
| Reminder bot ("Time Wizard") | Nagging until things are done | Automatic — any KairOS task with a due date gets nagged in ⏰・reminders with Done/Snooze |
| Metis | Learning: skill trees, lessons, XP | 📚・learning forum; Atlas authors plans, Metis verifies and mints XP |
| Hermes cron | Scheduled system jobs (syncs, weekly briefs) | Runs on its own; ask Atlas in 🛠️・improvements to change schedules |
Routing rules (the ones that matter)
- Reminders → KairOS task, never a chat promise. The reminder bot only sees tasks.
- Client facts → the dossier, never chat memory. If it matters next month, it goes in a file.
- Backlogs (watch/play/buy) are not tasks. No due dates, no nagging — they're menus to pick from.
- One improvement at a time in
🛠️・improvements, with small reversible changes.
Scheduled jobs
| When | What |
|---|---|
| Daily 20:00 | Agent config synced to GitHub |
| Daily 21:00 | Vault auto-committed and pushed |
| Daily 15:30 | Day briefing (calendar, tasks, main quest) |
| Monday 08:00 | Client portfolio brief posted to 🗂・dossier |
For developers / AI tools
- The vault self-documents for agents:
AGENTS.md(+CLAUDE.md) at its root. - Everything is keyed to IDs and files, not names — channels can be renamed freely.
- Config lives in a dotfiles repo, synced daily; every change is a git commit somewhere.