Wikilinks create two core node classes: family/template/recipe concepts and problem-number nodes in the private overlay. Concept relations form the backbone; problem-to-template links create natural clusters; sparse problem links retain only a few useful neighbors.
Recommended views
| Purpose | Graph filter | Depth |
|---|---|---|
| Original concepts only | tag:#algorithm-atlas/concept | 2 |
| Templates only | tag:#algorithm-atlas/template | 2 |
| Composite recipes | tag:#algorithm-atlas/recipe | 2 |
| Private problem clusters | tag:#algorithm-atlas/private-problem | 1–2 |
| Review from the current template | Open Local Graph | 2 |
Reading the edges
- Concept → concept: prerequisite, specialization, alternative, dual, composition, or same-shape/different-operator.
- Problem → template: a metadata-only candidate mapping until reviewed.
- Problem ↔ problem: a sparse neighbor based on candidate-template and tag overlap, useful for review ordering only.
- Problem and account nodes under
Private/are excluded from commercial exports.
Setup suggestions
- Apply a filter before showing the full private catalog.
- Group by tag, but do not rely on color as the only meaning.
- Prefer Local Graph depth 2 for concept study; enter the problem space from a template node.
- The project never overwrites
.obsidian/graph.json, preserving your vault preferences.