vault-explain

The Obsidian vault quality methodology works by organizing checks across defined dimensions and enforcing rules through a Stop hook architecture. It uses specific exit codes to gate workflows, ensuring vaults meet structural standards before operations complete.

Frontmatter is required in an Obsidian vault quality check because it provides essential metadata for dimension analysis. The methodology uses frontmatter to validate document structure and ensure notes conform to the configured workflow standards.

You configure workflows for an Obsidian vault by referencing the workflow catalog and methodology framework documents. These define the available hooks and checks, allowing you to map quality dimensions to specific vault operations.

The Stop hook architecture in Obsidian vault checks intercepts operations to validate vault quality against configured dimensions. It returns specific exit codes to block or allow actions based on whether the vault passes the quality gate.

Yes, you can use vault hooks to audit an existing Obsidian vault. The methodology framework and analysis checklist guide you through interpreting hook exit codes and dimension checks to identify structural issues.

The methodology is limited to explaining vault quality dimensions and hook architecture without modifying any vaults. It provides explanatory references for auditing and designing workflows but does not execute changes or fix structural errors directly.