obsidian-project-vault

A shared Obsidian vault uses a canonical folder structure and a three-layer model—source, thinking, and durable—to organize project knowledge. This structure supports cross-human and cross-agent collaboration by enforcing standards for frontmatter, area hubs, and reference notes.

The three-layer vault model separates notes into source materials, thinking notes, and durable knowledge. Durable folders include 30 Designs, 40 Requirements, 50 Decisions, 60 Reference, and 70 Project Areas, ensuring long-term reliability for cross-person handoffs.

Process intake material by following the intake-workflow guidelines to review raw inputs, then promote validated knowledge into durable folders. This ensures only finalized project knowledge is retained for cross-person handoffs and agent coordination.

Yes, an Obsidian vault supports cross-human and cross-agent collaboration by enforcing note-type rules, frontmatter standards, and area hubs. These provide a shared workspace where both humans and agents can reliably read and write durable project notes.

The best way to structure an Obsidian vault for handoffs is using a canonical folder structure with area hubs and reference notes. Applying frontmatter standards and note-type rules ensures knowledge remains durable and accessible across team members and agents.

Automation scripts are optional but available to help initialize and operate a shared Obsidian project vault. The vault functions with the standard folder structure and workflow guidelines, while scripts provide additional support for scaffolding and auditing vault contents.