What problem does it solve?
A topic map is a synthesized overview of a subject area. Where entries capture individual pieces of knowledge, a map connects them — explaining how things evolved, how they compare, and where to start depending on what someone needs.
Maps serve two audiences equally:
- Humans wanting to understand a topic landscape at a glance
- Future agents that need to quickly orient themselves before answering questions or creating more entries
A map is worth creating when there are enough related entries (roughly 4–5+) that the relationships tell a story worth telling.
Core Features & Use Cases
Maps synthesize relationships across related entries into a narrative landscape for humans and future agents. They are worth creating when there are enough related entries (roughly 4–5+) that the relationships tell a story worth telling.
- For humans: provides a landscape view of a topic and a quick orientation.
- For agents: offers a synthesized overview to orient before answering questions or creating more entries.
- File location and structure: docs/maps/<slug>.md; Frontmatter with title and tags; Suggested body structure including Overview, Landscape, Where to start, and optional Learning Path.
- Lifecycle: gather entries, write the map, commit changes to keep it up to date.
Quick Start
Gather related entries, write docs/maps/<slug>.md, then commit.