What problem does it solve? Keeping a growing personal knowledge wiki trustworthy is hard: claims lose their sources, pages drift from the evidence they cite, and edits silently break links or frontmatter. This Skill defines the shared evidence, provenance, and vault-mutation rules so every read, answer, or maintenance operation on the wiki stays verifiable against its captured sources. ## Core Features & Use Cases - Evidence and provenance enforcement: Raw clippings are immutable, every derived page declares sources: links back to its evidence, and answers must cite the pages they rest on. - Scoped policy loading: A routing table points each operation (authoring, relinking, ingest, maintenance) to exactly the reference file it needs, such as evidence policy, authoring conventions, or operation completion steps. - Safe vault mutations: A defined operation lifecycle (op-begin, validate, log, op-commit, optional sync) governs every write, with filesystem fallbacks when the Obsidian CLI is unavailable. - Use Case: When asked a question about a project, you search the vault, answer with citations to specific source pages, and disclose contradictions rather than inventing content; when asked to update documentation, you follow the canonical placement table and commit through the logged operation flow. ## Quick Start Ask the agent to answer a question from the wiki vault with citations, or to update a project document following the vault's evidence and placement rules.
