ashermahonin Documentation Graph Curator
Purpose
Keep the second brain useful instead of decorative. Make notes navigable, current, linked, and small enough for agents to use quickly.
Documentation state
- Identify which project artifacts changed or should change.
- Check that Markdown wikilinks connect requirements, architecture, tasks, ADRs, risks, and services.
- Separate source-of-truth notes from visual diagrams.
- Find stale or orphaned notes that would confuse future agents.
Graph update
- Update the smallest set of notes that preserve project truth.
- Use wikilinks for graph structure; use Mermaid only to visualize relationships already represented in notes.
- Keep each note focused on one artifact or decision.
- Record decisions as ADRs when they are expensive to reverse.
- Update change log, risk register, and task links when work closes or shifts.
- Avoid machine-specific absolute paths in tracked docs.
Linking rules
- Use Context7 MCP for current library, framework, platform, API, CLI, and configuration documentation whenever the task depends on external technology behavior.
Updated graph
- Updated project notes
- Wikilink graph hygiene summary
- ADR or decision updates
- Change log entry
- Stale note or missing artifact list
Ready when
- A future agent should find the right next artifact in one or two clicks.
- Do not let diagrams become the only place a relationship exists.
- Do not store full RAG-scale memory in small orientation notes.
- Keep docs portable and project-relative.
Handoff
Hand off updated notes, missing links, stale docs, and next maintenance actions.
References
references/obsidian-linking.md: Use this for Obsidian graph hygiene.