What problem does it solve? Maintaining a persistent LLM-curated knowledge base requires consistent structure, provenance tracking, and linking conventions; without a shared schema, wiki pages drift in format and lose traceability to their sources. ## Core Features & Use Cases - Three-Layer Architecture: Separates immutable raw sources, the LLM-maintained Obsidian wiki, and the governing schema so knowledge is compiled once rather than re-derived per query. - Page Templates & Provenance: Provides generic and paper deep-dive templates with extracted/inferred/ambiguous markers, a confidence formula, lifecycle states, and typed relationships. - Config Resolution Protocol: Standardizes how all wiki-* skills locate .env configuration for vault paths, link formats, and retrieval primitives. - Use Case: When any wiki ingest or query skill needs to know how to structure a new concept page, mark an inferred claim, or resolve the vault path, it consults this reference for the exact frontmatter fields and conventions. ## Quick Start Ask the assistant to show the wiki page template and provenance marker rules before creating a new concept page in the Obsidian vault.
