Discord — the interface
The server map, forum conventions, tags, and how to handle files.
Discord is the primary way to work with Atlas. Channels are organized so every conversation lands in the right context automatically.
Server map
| Channel | What it's for |
|---|---|
| 🧠・talk-with-atlas | Main line to Atlas — anything, cross-domain, ad-hoc |
| 🗂・dossier | One post per client company. Who they are, stakeholders, engagement. Atlas keeps the company dossier updated from whatever you drop here. |
| 💼・projects | One post per build (personal or client). Naming convention: <Project Name> | <Company> — the suffix tells Atlas which client it belongs to. |
| 🎓・career | Job search, interviews, resume, leads pipeline |
| 📚・learning | Skill trees and lessons (backed by Metis) |
| ✈️・travel | One post per trip — planning, bookings, packing |
| 🛠️・improvements | Making the AI stack itself better |
| 🎬・movies / 🎮・games | Watch/play backlog — recommendations, never tasks |
| 🛒・buy-list | Purchase wishlist — Atlas can compare and price-check |
| ⏰・reminders | The reminder bot's channel — Done/Snooze buttons live here |
| 🪧・notice | Read-only announcements |
Forum conventions
- Post titles matter. In
💼・projects,Leads Tracker | Acmetells Atlas the project and the client — it loads that company's full context before replying. - Tags mirror status. Every forum has tags (🔍 discovery, 🔨 building, ✅ done…). Tag your post; filter by tag to see state at a glance.
- Post bodies stay thin. The thread is intake and conversation; durable facts get written to the vault by Atlas. Don't maintain long post bodies.
Files and documents
- Small files (under ~30 MB): attach directly in the relevant post.
- Big or keep-worthy documents (client PDFs, audits): they belong in the vault under
Sources/<Company>/— then tell Atlas to digest them into the dossier. The chat is ephemeral; the vault is forever.