User Guide
Status: Partially migrated. The quickstart, web-dashboard reference, and Discord conversation workflow are current.
This book is the canonical home for end-user workflows, user-visible behavior, product concepts, and user troubleshooting. Keep installation, deployment, security controls, and recovery procedures in ADMIN-GUIDE/; keep implementation detail in DEVELOPER-GUIDE/.
Start here
- Documentation atlas — placement rules and source-of-truth boundaries.
- Documentation sitemap — existing navigation is transitional and still contains legacy paths.
- Quickstart — install Mosaic, complete setup, and launch a session.
- Web dashboard — current routes, navigation, chat persistence, projects/tasks views, settings, and admin behavior.
- Discord conversations — current authorized parent-channel, thread, attachment, and control workflow.
Chapter map
| Chapter | Scope | Status |
|---|---|---|
getting-started/ |
First-use setup, orientation, and quickstarts. | Quickstart is current; additional pages are planned. |
concepts/ |
User-facing terminology, product concepts, and mental models. | Scaffold only. |
workflows/ |
Task-oriented procedures for using Mosaic Stack. | Discord conversation workflow is current. |
product/ |
Current product surfaces and visible behavior. | Web dashboard reference is current. |
troubleshooting/ |
User-visible failures, diagnostics, and fixes. | Scaffold only. |
Current pages
- Quickstart — the verified installed-CLI first-use path.
- Web dashboard — verified current Next.js dashboard behavior and limitations.
- Discord conversations — verified current Discord user workflow.
Every promoted page must be added to this index and to SITEMAP.md in the same migration slice.
Migration backlog — not current navigation
These are source candidates, not current user guidance:
_old_structure/guides/user-guide.md— historical source; verify every claim before promotion. The former rootQUICKSTART.mdwas an empty placeholder and has been replaced by the current page above.
Do not link to the quarantine as a current user path. Create a new page only after classifying its audience, status, and evidence in the migration report.
Authoring boundary
New user-facing documentation belongs under one of the chapter directories above. Use a lowercase kebab-case page name, state whether commands are current or held, and link back to this index plus related canonical sources.