veronica
12d5258e20
A - docs/README.md:149-190 rewritten. It prescribed a competing front-matter schema
(title/type/audience/status/source_of_truth) adopted by 4 of 128 live documents. Two
documented conventions in one repo is the defect this pass removes, so the README now
documents the contract and the 4 files convert in the same commit: `type` dropped
(kind replaces it), `title`/`audience`/`source_of_truth` kept.
B - source-of-truth leaves the kind enum, which is now 6 values, and returns as an orthogonal
boolean. kind was carrying two independent facts. docs/requirements/native-kanban-sot.md
is stamped `kind: spec` + `source_of_truth: true`, which is what it always was.
C - status gains `completed`. Applied to the two executed plans, on artifact evidence rather
than on their own say-so: --purpose push|merge ships in ci-queue-wait.sh, and every section
the README plan specifies exists in docs/README.md today.
D - kind follows content, never filename. docs/native-kanban-sot/TASKS.md is `kind: spec`
because its body says "a build plan, not a task tracker". The name stays wrong; that is a
rename and it is out of scope here.
E - the contract covers .md only, written into the README as a decision with vision's
YAML.parse measurement as the reason, so the omission does not read as an oversight.
F - channel-protocol.md guide -> spec. Applied, with a correction the reviewer should see: the
ruling cites "7 normative MUSTs" and there are ZERO uppercase RFC2119 terms in that file.
Control: the identical grep returns 25 lines in docs/requirements/native-kanban-sot.md. The
citation half of the finding does hold and is larger than stated. Consequence recorded in
the worklist: the file's own banner now contradicts its header.
Verified: 128 live .md under docs/ (127 baseline + this PR's worklist), 107 stamped, 0 invalid
kinds, 17 operator-held + 3 supersede-stamp deferrals + 1 generated = 21 unstamped. 107+21=128.
Control: the verifier reports valid=False when a kind is corrupted to `nonsense`, so the
0-invalid result is a real result. prettier --check clean across docs/.
kind, status
| kind | status |
|---|---|
| guide | active |
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 — resolvable current navigation and authority-gated migration summary.
- 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— quarantined historical source; verify every claim before promotion. See the documentation catalog for its disposition.- The former root
QUICKSTART.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.