The Vault — where knowledge lives

The vault is an Obsidian vault (a folder of Markdown files, git-versioned) that acts as Pillar 1: the Blueprint — the permanent memory of the whole system. Atlas reads and writes it; humans browse it in Obsidian.

Structure

Ara/
├── Companies/<Company>.md            # one dossier per client
├── Projects/<Company>/<Project>.md   # one blueprint per build
├── Sources/<Company>/                # original client documents
├── Watchlist.md                      # movies / shows / games backlog
├── Buy_List.md                       # purchase wishlist
├── Career/                           # brag book etc.
└── _templates/                       # scaffolds for new files

Dossier = who the company is: profile, portfolio of builds, stakeholders and hierarchy, engagement status, and a hassle: 1-10 score (the client-quality metric). Blueprint = one build: objective, architecture, data schemas, progress log.

Conventions

• Filenames: spaces → underscores (Alba Group → Alba_Group.md).
• Every dossier/blueprint has YAML frontmatter: client, aliases, status, tags (tech stack).
• Facts live in exactly one place; everything else links to it.

The query tool: vq

.scripts/vq inside the vault — how agents (and you, in a terminal) query without reading whole files:

vq resolve 'acme'                      # which file is this company? (exit 1 = doesn't exist)
vq where status=discovery              # filter by frontmatter
vq where tags~powerbi hassle~8         # any frontmatter field works
vq get Companies/Acme.md --section 2   # read ONE section, not the whole note
vq new company 'Acme Corp'             # scaffold a dossier + folders, no duplicates possible
vq new project 'Leads Tracker' --company acme   # scaffold blueprint + auto-link Portfolio
vq check                               # linter: missing frontmatter, orphans, dead links
vq index --json                        # full catalog, machine-readable

The iron rule: vq resolve exit 1 is the only green light for creating a new file, and vq new is the only sanctioned way to create one — so duplicates can't happen.

Syncing

• A daily job auto-commits and pushes the vault at 21:00.
• Manual: Obsidian command palette → "Obsidian Git: Commit-and-sync", or plain git add -A && git commit && git push.
• Any AI tool opened in the vault folder self-onboards via AGENTS.md at the root.