The knowledge base needs lightweight read-mostly audits that answer: what shape is it in right now, and what should improve next?
When To Use
Use a status check when the user asks:
- what needs cleanup,
- whether the wiki is healthy,
- what pages are most important,
- what should be improved next,
- or whether the public site has obvious structure problems.
Workflow
- Read index.md, recent log.md entries, and the top-level
wiki/folders. - Count wiki pages by folder and page type when useful.
- Identify recently updated pages.
- Identify likely orphans, pages missing source sections, stale pages, and bloated pages.
- Check for public/private risk at a high level.
- Return a concise report with recommended next actions.
- Write a durable report to
outputs/audits/YYYY-MM-DD - Wiki Status.mdonly if the report is substantial.
What To Report
Useful status fields:
| Field | Purpose |
|---|---|
| Page counts | Shows where the wiki is growing. |
| Recently updated pages | Shows current activity. |
| High-value pages | Shows pages that anchor the system. |
| Orphan candidates | Shows pages that need links. |
| Split candidates | Shows pages that may be too broad. |
| Source gaps | Shows pages that need better citation. |
| Public/private risks | Protects paid, private, or sensitive material. |
| Recommended next actions | Turns the audit into a plan. |
Rules
- Do not reorganize files during a status pass unless the user asks.
- Do not rewrite pages during a status pass unless there is a clear small fix.
- Prefer concrete page-level recommendations over generic advice.
- Keep the report short enough to act on.