mosaicstack/stack
1
0
Fork 1
Code Issues 246 Pull Requests 7 Actions Packages Projects Releases 15 Wiki Activity

docs: replace stale sitemap inventory

Browse Source
This commit is contained in:
Jason Woltje
2026-08-10 18:35:46 -05:00
parent 16920c4a6f
commit 7ddd2f5e1d
3 changed files with 69 additions and 127 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/README.md
+9 -9
View File
@@ -205,17 +205,17 @@ The initial structure pass defined the target structure without moving or rewrit
## Current transition state
The structure is being established incrementally while classified content migration proceeds. During this transition:
Classified migration is active and the audience books now contain verified current pages. During this transition:
- The target directories listed above are a blueprint; not all indexes or chapters exist yet.
- `docs/_old_structure/` remains available for reference but is not current documentation.
- Existing root documentation files remain until their migration destinations are reviewed; migrated pages must leave a verified navigation path.
- `docs/SITEMAP.md` has current scaffold entry points but still contains legacy paths and will be refreshed as pages are migrated.
- The target directories listed above remain the placement contract; some planned chapters are not populated yet.
- `docs/_old_structure/` remains available for migration evidence but is not current documentation or command authority.
- Root control and API artifacts remain until their authority and destination decisions are approved.
- `docs/SITEMAP.md` contains only resolvable current navigation plus a non-linked summary of authority-gated migration groups.
- No external publishing platform is assumed. The canonical source remains this repository under `docs/`.
## Non-goals for this pass
## Current migration boundaries
- Do not move, delete, or rewrite the archived documentation.
- Do not rewrite the product PRD, active task rollup, API contract, or sitemap yet.
- Do not create a documentation website or publishing pipeline.
- Do not bulk-promote or bulk-rewrite quarantined documentation; classify and verify each coherent slice.
- Do not rewrite product requirements, orchestrator-owned task state, mission status, or the API contract without the required authority decision.
- Do not create a documentation website or publishing pipeline as part of content migration.
- Do not treat Obsidian metadata as product or project source of truth.