EA Connected Vault Setup

Create a light navigation layer, not a new taxonomy or a content rewrite. Preserve every note's text, existing properties, filenames, folders, templates, query blocks, and links unless the requested linking requires a small additive edit.

Scope and safety

• Work only on the user-designated corpus. Exclude configuration, templates, attachments, generated/cache folders, daily logs, and existing database/query files unless the user includes them.
• Search filenames, aliases, frontmatter keys, links, and existing root/MOC notes before creating anything. Reuse a clearly matching root rather than duplicating it.
• Use the exact, capitalized property names Parents and Related. Both are YAML/Markdown lists of wikilinks, even when they initially contain one item. Do not replace populated values; merge without changing their existing representation or casing.
• In this initial setup, give each child exactly one Parents entry: its cluster root. Do not introduce multiple root assignments.
• Do not infer a topical relationship from name similarity alone. Leave uncertain notes in a deliberately named holding root (for example, Unsorted concepts) and flag them.
• This operation changes many files. First produce an inventory and proposed clustering; obtain confirmation before writing. After approval, apply only additive, minimal diffs and report every created/changed file.

1. Inventory and cluster proposal