Vault Metadata

Canonical reference for frontmatter schemas, metadata values, Dataview query patterns, and repository path conventions in the Teslasoft Obsidian vault.

When to Use

• Checking valid status/type/horizon values
• Writing or debugging Dataview queries
• Validating frontmatter fields for a note type
• Working with repository path (repoPath) fields
• Understanding what metadata drives Dashboard and queries

When NOT to Use

• Creating notes or understanding PARA structure (use vault-notes)
• Looking up template sections and Templater syntax (use vault-templates)

---

Frontmatter Schema Reference

Canonical schema for all note types. Fields marked (required) must be present; others are optional.

Note Type	Folder	type (required)	status	Other Key Fields
Goal	10_Goals/	goal	active | planning | completed	horizon: YYYY-Qn (required), created
Project	20_Projects/	project	active | planning | completed | on-hold	goal: "[[Goal]]" (required), repoPath, created
Area	30_Areas/	area	—	projects: [], resources: [], created
Resource	40_Resources/	ressource	—	category, repoPath, created
Collaboration	50_Collab/	collaboration	active | planning | paused | completed	partner, patreonURL, contactEmail, created
Research	60_Science/	research	exploring | active | concluded	created
Skill	70_Skills/	skill	—	level: novice | developing | proficient | expert | master, created
Inbox	00_Inbox/	—	—	captured: YYYY-MM-DD HH:mm, processed: false, tags: [inbox]
Archive	90_Archive/	archive	—	originalType, archivedDate, originalLocation, tags: [archived]
Policy	coordination/policies/	policy	active	policy_id, version, enforcement: BLOCK | WARN | LOG, scope: [], created
Prompt	.prompts/ dirs	—	—	purpose, description, skills: [], tools: [], agent, created

Note: ressource uses German spelling intentionally.

---

Status Values

Goals

• active - Currently pursuing
• planning - Not yet started
• completed - Achieved

Projects

• active - Currently working on
• planning - Not yet started
• completed - Finished
• on-hold - Paused temporarily

Collaborations

• active - Ongoing partnership
• planning - Being discussed
• paused - Temporarily inactive
• completed - Concluded

Research (Science)

• exploring - Initial investigation
• active - Active research
• concluded - Research complete

---

Type Values

• goal - For notes in 10_Goals/
• project - For notes in 20_Projects/
• ressource - For notes in 40_Resources/ (note German spelling)
• area - For notes in 30_Areas/
• collaboration - For notes in 50_Collab/
• research - For notes in 60_Science/
• skill - For notes in 70_Skills/
• archive - For notes in 90_Archive/
• policy - For governance policies

---

Horizon Values (Goals only)

Format: YYYY-Qn (e.g., 2026-Q1, 2026-Q2)

Used in Goals frontmatter and Dataview queries to filter by quarter.

---

Repository Path Integration

Purpose: Bridge between vault and external code repositories

Pattern: Absolute Windows paths in repoPath frontmatter field

Common Base Paths:

• D:\TeamProjects\Teslasoft\ - Teslasoft projects
• D:\TeamProjects\AwesomeNodes\ - AwesomeNodes projects
• D:\TeamProjects\GT-SWEATLORDS\ - Gaming community projects

When Working with Projects:

1. Check if repoPath exists in frontmatter
2. Reference it when discussing code/implementation
3. Never modify paths without explicit confirmation
4. Suggest adding repoPath if project has external repo

---

Dataview Query Patterns

Active Projects

LIST FROM "20_Projects"
WHERE type = "project" AND status = "active"
SORT file.mtime desc

Planning Projects

LIST FROM "20_Projects"
WHERE type = "project" AND status = "planning"

Goals by Quarter

LIST FROM "10_Goals"
WHERE horizon = "2026-Q1"
SORT file.name

Resources by Category

TABLE type, repoPath
FROM "40_Resources"
WHERE type = "ressource"

Custom Patterns

Dataview queries use frontmatter fields as filter criteria. Common patterns:

• FROM "folder" - Scope to PARA folder
• WHERE type = "value" - Filter by note type
• WHERE status = "value" - Filter by status
• SORT file.mtime desc - Sort by last modified
• TABLE field1, field2 - Tabular output with specific fields

---

Impact on Operations

Metadata changes can break:

• Dashboard queries - Dashboard.md uses Dataview filtered by type and status
• Goal-Project links - Changing goal field breaks relationship chain
• Backlinks - Removing [[]] links breaks Obsidian's backlink graph
• Dataview views - Changing type values will exclude notes from filtered views

Always check vault-notes Common Tasks for safe modification workflows.

---

Cross-References

• Note types and operations: Invoke vault-notes for PARA structure and common tasks
• Template specifications: Invoke vault-templates for full template key fields and sections

---

Metadata

author: Christian Kusmanow / Claude
version: 1.0.0
last_updated: 2026-02-09
source: Extracted from CLAUDE.md (Metadata Guidelines, Repository Path Integration, Dataview Query Patterns)
change_surface: Status/type values, Dataview patterns, frontmatter schema table
extension_points: Add new note types to schema table, add query patterns
changelog:
  - "1.0.0: Initial extraction from CLAUDE.md"