Missing pages, split candidates, and new connections should be found deliberately before hub pages become overloaded.
Purpose
The goal is to identify subtopics with enough practical value to deserve their own page.
Breakdown is useful when a hub page has grown large, when several pages mention the same idea, or when the user wants new directions for the wiki.
Workflow
- Read index.md, recent log.md, and relevant hub pages.
- Search
wiki/for recurring named concepts, techniques, workflows, tools, books, people, or systems without dedicated pages. - Identify bloated pages where a subtopic has enough substance to become its own page.
- Rank candidates by usefulness to the user’s active systems, number of references, and clarity of purpose.
- Present a candidate table before creating pages unless the user has already asked to create them.
- When creating pages, add backlinks from parent pages and update index.md.
- Append a
compileormaintenanceentry to log.md.
Candidate Test
A candidate page is worth creating when it can support:
- a clear role in the knowledge base,
- a useful summary,
- practical implications,
- related links,
- and at least one source or parent page.
Avoid pages that would only contain a definition and one vague paragraph.
Common Split Patterns
| Parent Pattern | Split When |
|---|---|
| Hub page | A subtopic needs several substantial paragraphs. |
| Technique page | A step has its own operating procedure or failure modes. |
| Synthesis page | A recurring concept becomes useful outside the original synthesis. |
| Book page | A takeaway becomes a general principle used elsewhere. |
| Workflow page | A recurring sub-step becomes reusable across workflows. |
Output
Use a table like this before creating pages:
| Candidate | Proposed folder | Why it matters | Current references | Priority |
|---|