Wiki Scope
The problem is not a lack of content. It is a lack of editorial boundaries.
What belongs in the main path
- approved projects and their specific documentation
- architecture and integration notes that go beyond repository READMEs
- deployment and operating context when it is tied to a project
What stays out of the main path
- old handoffs
- expired phase plans
- long TODOs, brainstorm documents, and historical reports
- imported READMEs with broken links and foreign repo context
- projects without a clear role in the current stack
Utility test
A page only deserves top-level space if it does at least one of these jobs:
- explains an approved project in more depth than GitHub should
- captures architecture, integration, or deployment detail that is project-specific
- provides a focused runbook tied to a project or cross-project dependency
- helps someone work inside the approved project surface
Next cleanup layer
To make the wiki genuinely refined, the next work is:
- hide or remove historical pages from the main path
- trim imported READMEs and remove broken links
- rewrite oversized pages into focused project documents
- consolidate duplicates and overlapping documents