Project Root Docs Cleanup Draft¶
Purpose¶
Inventory documentation and text files at the repository root and propose moving them into the docs/ tree (or archiving) to centralize knowledge and reduce duplication.
Prerequisites¶
- Align with repository documentation conventions (front-matter, section order, wikilinks).
- Confirm which files are intentionally kept at root (e.g., README.md, mkdocs.yml).
Steps¶
- Inventory root-level docs.
- Propose destinations and note any link changes required.
- Execute moves in a PR, update links, and validate.
Inventory (as of creation)¶
AGENTS.md→ Keep at root (authoritative rules). Add a mirrored index page underdocs/development/linking back here.ARCHITECTURE_REVIEW_SUMMARY.md→ Move todocs/architecture/.CONVERSION_COMPLETE.md→ Move todocs/history/with a short context note.LAPTOP_SYNC_COMMANDS.sh→ Keep as script; add entry indocs/software/scripts.md.MERGE_CHECKLIST.md→ Move todocs/development/and cross-link from contributor docs.PROJECT_SETUP_STATUS.md→ Move todocs/project_overview/.QUICKSTART_DIMOS.md→ Move todocs/integrations/ordocs/software/agent/depending on content; ensure canonical DIMOS pages exist.README.md→ Keep at root (project landing). Ensure it links to key docs pages.TODO.md→ Move todocs/development/or convert into GitHub issues/roadmap entries..env*files → Keep in root for developer convenience. Leave these files untouched for now per current policy. Documentation should reference the standard single.envpattern going forward, but do not modify or remove existing.env*files in this pass..shadowhound_env→ Deprecated; retain file only for backward compatibility. Ensure all docs avoid referencing it.
Validation¶
- Re-run wikilink validation after moves and update all cross-references.
- Confirm
mkdocs.ymlupdates if new top-level docs are added to navigation.
References¶
docs/development/per_directory_review_plan.mdfor process and acceptance criteria.