parsidion

Parsidion vault - Knowledge Management System

A richly organized Obsidian vault (default ~/ParsidionVault/, with legacy ~/ClaudeVault/ fallback) that replaces built-in auto memory with structured, searchable, cross-linked knowledge.

Philosophy

• Search before create. Always search the vault before creating a new note. Duplicate knowledge fragments rot.
• Atomic notes. One concept per note. If a note covers two distinct ideas, split it.
• Frontmatter is mandatory. Every note must have a valid YAML frontmatter block. No exceptions.
• Knowledge compounds. Individual notes gain value through links. An unlinked note is a dead note.
• Confidence matters. Tag what you know vs. what you suspect. Update confidence as understanding deepens.

Vault-First Consultation

The vault is your first stop — not your last resort. Before web search, before documentation, before experimentation, check whether the vault already holds a solution.

Debugging: Search Before You Diagnose

When you encounter an error, exception, or unexpected behavior:

1. Extract the key signal: the exception type, package name, or the most distinctive phrase from the error message
2. Dispatch the vault-explorer agent with the signal as the query.
3. Answer returned? Apply the documented solution; update the note if you learn something new about the problem. Read specific files from the Sources section only if you need more depth.
4. "No relevant vault notes found"? Diagnose, solve, then save the solution so future sessions benefit.

Implementation: Check for Prior Art

When implementing any feature, pattern, or integration:

1. Dispatch the vault-explorer agent with the feature keyword as the query.
2. Answer returned? Reuse and adapt — a proven implementation beats a fresh one every time. Read specific files from the Sources section for details; check the sources frontmatter field for code references.
3. "No relevant vault notes found"? Implement it, then save the pattern so future sessions benefit.