flowing-abyss/obsidian-vault-skills/system-note

System Notes

Category. A high-level domain dashboard. Categories are created and edited only by the user. Never create, edit, rename or delete them.

Meta-note. A thematic hub or roadmap for in-depth research, anchored to a parent category.

Problem. A specific research question or conceptual challenge. Takes context and boundaries from its parent meta-note and category.

Hierarchy. A structural aggregator that sequences atomized notes into a linked narrative. Needs at least a parent category.

Commands

Run from the vault root: V="python3 .claude/_engine/vault.py"

The engine reads the vault manifests, fills fixed values, defaults, created and updated, and takes the note body scaffold from the type's template. It refuses invalid input, writes nothing, and says what to fix. Correct the input. Never work around an error by writing frontmatter by hand.

• Repeat --set key=value to build a list. Link fields take plain note names.
• Pass only what you know. Skip a field instead of guessing a value.
• Edit the note body directly. A hook validates every edit; without hooks run check.

The chain

Category -> Meta -> Problem -> Hierarchy. Always set category. A problem also needs meta. The engine refuses a write where the meta does not belong to the category or the problem to the meta; list valid names with values system/high/problem meta --given category="name".

If no existing category fits, stop and ask the user. Do not pick a loose match and do not propose creating one yourself.