obsidian-system-notes

Structure knowledge hierarchy in Obsidian by creating thematic hubs as meta-notes under base/_meta-notes, linking them to corresponding problems and hierarchies with strict frontmatter fields and naming conventions to ensure vault-wide discoverability.

Organize research questions in Obsidian by creating problem notes under base/_problems and linking each to a specific meta-note thematic hub. This decomposes broad topics into structured sub-questions following defined category relationships.

No, categories in Obsidian are strictly human-managed and never created automatically. The system enforces this by prohibiting new category creation during the workflow, ensuring you manually maintain the category, meta-note, and problem relationship chain.

Group related notes in Obsidian by creating hierarchy aggregators under base/_hierarchy that attach to categories, meta-notes, or problems. These aggregation points enforce structured linking and maintain consistent relationships across the knowledge base.

System notes in Obsidian should follow lowercase, unique naming rules without dates or pronouns. These conventions apply to meta-notes, problems, and hierarchies alike, ensuring safe linking and structural consistency across the vault.

Obsidian system notes fail to link correctly when the defined chain between category, meta-note, and problem is broken. The system enforces safe linking by discovering existing notes dynamically and prohibiting new category creation to maintain relationship integrity.