giordanorogers Obsidian Wiki Maintainer
Purpose
Turn source material into a maintained local Markdown wiki. Preserve provenance, separate source notes from synthesis, and keep the vault healthy over time.
First Step
Identify the vault path and mode. The default wiki path is "$HOME/Library/Mobile Documents/iCloudmdobsidian/Documents/Wiki". If you can not find this path, search for "Documents/Wiki". If this directory still cannot be found, ask the user for clarification.
Modes
Ingest
Capture raw material and metadata.
- Preserve source URL/path, author/org, title, date, capture date, and access notes.
- Put unprocessed material in an inbox/raw area.
- Do not overwrite original source files.
Source Note
Create one note per substantive source.
Include:
- Summary.
- Key claims.
- Evidence or method.
- Limitations.
- Useful quotes when helpful/relevant.
- Links to related concept notes.
- Status and review metadata.
Compile
Synthesize multiple source notes into concept or wiki notes.
- Separate synthesis from source extraction.
- Link back to source notes.
- Mark confidence and unsupported assumptions.
- Prefer clear concept boundaries over excessive atomization.
- Create or update map-of-content notes for larger topics.
Answer From Vault
Answer using vault notes and source links.
- Search relevant notes before answering.
- Cite note paths or source links.
- Distinguish vault-supported claims from outside knowledge.
- If the vault lacks evidence, say what is missing.
Health Check
Inspect vault quality.
Check for:
- Broken links.
- Orphan notes.
- Duplicate or near-duplicate concept notes.
- Missing frontmatter.
- Unprocessed inbox/source items.
- Stale notes.
- Unsupported claims.
- Contradictions or unresolved disagreements.
Review Queue
Create a user-review list for decisions that should not be automated:
- Merge or split concepts.
- Resolve contradictions.
- Promote draft notes to reviewed notes.
- Delete or archive stale notes.
- Choose canonical names and aliases.
Suggested Folder Schema
Use or adapt the existing vault convention. If there is no convention, propose:
00 Inbox/
10 Sources/
20 Concepts/
30 Projects/
40 Maps/
90 System/
Do not impose this schema on an existing vault without user approval.
Suggested Frontmatter
Use existing frontmatter conventions if present. Otherwise use a compact schema:
---
type: source | concept | map | project | health | log
status: inbox | processed | draft | reviewed | stale | deprecated
source_url:
source_author:
source_date:
captured_date:
last_checked:
confidence:
reviewed_by_user: false
aliases: []
tags: []
related: []
supports: []
contradicts: []
---
Only include fields that make sense for the note type.
Link Rules
- Use the vault's existing link style when detectable.
- Prefer stable note names and aliases for concepts likely to recur.
- Link source notes to concept notes and concept notes back to source notes.
- Avoid link spam. A link should represent a useful relationship.
- Record uncertain links for review rather than pretending they are canonical.
Final Response
Report:
- Vault path touched.
- Files created or modified.
- Mode used.
- Health issues or review items found.
- Claims or notes needing user review.