Vault Conventions

Folders

Folder	Holds
root	00 Home only
01 Company	Frontier Engineering itself: about, links, tech stack, course platform
02 Program	Charter, questions, decisions, roadmap, scale model, agreements
03 Curriculum	HVE hub + teaching plan, product tracks, personas, assessment
04 Delivery	Environment, workshop playbook, instructors
05 Reference	Facts from outside sources (dated): HVE research, benchmarks, certs
06 Meetings	YYYY-MM-DD Topic meeting notes
90 Attachments	Images/PDFs (set as attachment folder)
99 Templates	Note templates (set as Templates folder)

Folders are coarse buckets; links and tags do the real organizing. Obsidian links by note name, so moving a note between folders never breaks links.

Links

• Link liberally with [[Note Name]]; use aliases ([[Github Copilot|Copilot]]) for readable prose
• Link to a specific question with block refs: [[Questions#^q-001|^q-001]] (never to a question’s wording, which changes)
• Every note links back up to a hub (MOC) — no orphans
• Note names are unique, Title Case, no dates except meetings

Properties (frontmatter)

Every note has: type, status, tags, created, updated. Add aliases for alternate names, source for reference notes.

Tags (nested)

• type/ — moc, charter, plan, log, concept, track, module, playbook, reference, meeting, decision, org, platform
• area/ — program, curriculum, delivery, commercial, certification, labs
• product/ — github-copilot, foundry, fabric, hve
• project/frontier-ai-cert
• Status lives in the status property (draft · active · in-progress · needs-verification · done), not tags

Content versioning

Microsoft products and HVE change monthly. Every module records verified: YYYY-MM-DD and the product/HVE version it was tested against. Re-verify before each cohort.

Recommended settings

• Settings → Files & links → Default location for new attachments → 90 Attachments; Use Wikilinks on; Automatically update internal links on
• Settings → Core plugins → Templates → folder 99 Templates
• Settings → Files & links → New link format → Shortest path when possible
• Optional: Bases (core) or Dataview for tables of modules/questions by property