obsidian-kb-artifacts

Create a JSON Canvas file under Maps/ with file nodes pointing to existing notes in Sources/Papers and Knowledge, plus edges showing relationships like uses, extends, or supports. Validate that every file node target exists and all edge endpoints reference valid node ids.

Use a small YAML frontmatter block with fields like type, status, and tags, then reference other notes with [[wikilinks]] and external URLs with Markdown links. Prefer folder-qualified links when note names are ambiguous and keep notes readable rather than raw dumps.

Bases are explicit-only and should not be generated by default. Create a .base file only when the user asks for database-like views, such as a table of active experiments, and never use Bases as the canonical registry or source of truth.

No, the Obsidian CLI is an optional helper for search, reading notes, and daily appends. The filesystem remains the source of truth, and knowledge base maintenance continues with filesystem-only operations if the CLI is unavailable.

Canvas files are derived artifacts, not the source of truth, so durable content belongs in Markdown notes first. Avoid storing registry metadata, long-form synthesis, or unstable scratch thinking in canvas nodes, and do not auto-generate project-wide mega-graphs.