How l4pislazuli/cursor_obsidian_vault works
1. Repository purpose
This repo is not an application codebase; it is a template Obsidian vault for working with AI chat notes. It is designed to be cloned, personalized, and used as a combined chat workspace + long-term knowledge base.
2. Top-level architecture
The vault is split into a few clear zones: configuration (.cursor/, .obsidian/), content capture (chats/), synthesis (analysis/), personal metadata (profile/), and media attachments (assets/). That separation is the core architectural boundary.
3. AI-agent integration layer
.cursor/rules/ contains the operational rules used by Cursor Cloud Agent. These rules define behavior by file scope: a global vault policy, separate handling for temp chats, persistent chats, analysis notes, frontmatter conventions, and Git-related changes. In other words, the repository is partly a policy-driven workspace for AI agents.
4. Obsidian workspace layer
.obsidian/ holds vault settings for Obsidian, including the default note location and community plugin configuration. The repo expects Templater to be installed, with templates/ configured as the template source. This makes note creation a standardized workflow rather than ad hoc editing.
5. Content lifecycle: temp → persistent → archive
chats/temp/ is the short-lived intake area for transient conversations. Valuable notes are promoted into chats/persistent/ for long-term retention. Within persistent, _archive/ stores retired notes. This lifecycle is the main data flow for the vault.
6. Analytical layer
analysis/ is a separate synthesis space for cross-note analysis of persistent content. It is not just another note folder; it represents an aggregation and interpretation boundary above the raw chat notes. The README explicitly treats persistent notes as the source material for analysis notes.
7. Template system
templates/ contains the note skeletons used to keep metadata and structure consistent: one each for temp chats, persistent chats, and analysis notes. These templates enforce the note lifecycle by making the right frontmatter and layout easy to create repeatedly.
8. Personalization boundary
profile/user.example.md is the sample user profile, while profile/user.md is the private personal file excluded from Git. This is the repo’s main privacy boundary: the vault is public-template friendly, but user-specific details stay local and untracked.
9. Media and attachments
assets/ is a shared attachment bucket, typically for images or other files referenced from notes. The naming guidance in the README implies attachments are tied back to note context, supporting traceability across the vault.
10. Metadata conventions
All notes are expected to follow a shared frontmatter schema with fields like created, updated, tags, source, status, aliases, and related. Analysis notes additionally track sources_updated. This schema is important because it enables AI-agent actions, note promotion, and later cross-note analysis.
11. Operational and Git policy
The repo is meant for normal Git versioning, but with explicit guardrails: note content changes can be committed directly, while rule changes and folder restructuring are expected to go through branch/PR review. .gitignore excludes workspace artifacts and profile/user.md; .gitattributes enforces LF line endings for portability.
12. Overall flow for diagramming
A useful architecture diagram would show: Obsidian/Cursor users and agents create notes in temp using templates and rules; useful notes are promoted to persistent; persistent notes feed analysis; attachments live in assets; personal data stays in profile/user.md and out of Git; configuration lives in .obsidian and .cursor. The repo’s architecture is therefore a governed knowledge pipeline rather than a software execution system.
Main entry points: rules Cursor rules · templates Note templates · persistent Persistent notes · temp Temp chats
Components 19
Configuration
Workspace settings and agent policy files.
- Cursor rules · Scoped behavior rules for vault use, chat handling, frontmatter, and Git workflow.
.cursor/rules - Vault policy · Global rules for how the vault should be treated and edited.
.cursor/rules/vault-core.mdc - Temp chats · Guidance for transient chat notes in the intake area.
.cursor/rules/chat-temp.mdc - Persistent chats · Guidance for durable chat notes and promotion to long-term storage.
.cursor/rules/chat-persistent.mdc - Analysis workflow · Guidance for creating synthesis notes from persistent source material.
.cursor/rules/analysis-workflow.mdc - Frontmatter rules · Shared metadata conventions for note structure and fields.
.cursor/rules/obsidian-frontmatter.mdc - Git policy · Guardrails for commits, review boundaries, and repository changes.
.cursor/rules/git-workflow.mdc - Obsidian config · Vault settings and plugin configuration for the note workspace.
.obsidian - Template source · Obsidian template configuration pointing at the templates folder.
.obsidian/templates.json
Content lifecycle
Capture, retention, and archival note flow.
- Temp chats · Short-lived intake area for transient conversations.
chats/temp - Persistent notes · Long-term retained chat notes and source material for analysis.
chats/persistent - Archive · Retired persistent notes kept out of the active set.
chats/persistent/_archive
Synthesis
Cross-note analysis layer.
- Analysis notes · Cross-note interpretation and aggregation over persistent notes.
analysis
Personal data
User-specific profile metadata.
- Profile · Personal metadata area with public example and local-only user data conventions.
profile - Profile example · Sample user profile showing the expected personal metadata shape.
profile/user.example.md - Private profile · User-specific personal file kept private and excluded from Git.
Support files
Templates and attachments.
- Note templates · Skeletons for temp chats, persistent chats, and analysis notes.
templates - Attachments · Shared location for images and other referenced files.
assets
Other components
- Users & agents · Cursor and Obsidian users that create, promote, and analyze notes.
Connections 22
- Users & agents → Cursor rules: follows · Agents use scoped rules to decide how to edit and organize notes.
- Cursor rules → Vault policy: includes · Global vault behavior.
- Cursor rules → Temp chats: includes · Temp-chat handling.
- Cursor rules → Persistent chats: includes · Persistent-note handling.
- Cursor rules → Analysis workflow: includes · Analysis-note handling.
- Cursor rules → Frontmatter rules: includes · Frontmatter conventions.
- Cursor rules → Git policy: includes · Git and repo-change policy.
- Users & agents → Obsidian config: uses · Obsidian is the primary vault UI.
- Obsidian config → Template source: configures · Sets the template source location.
- Template source → Note templates: points to · Templates provide standard note skeletons.
- Note templates → Temp chats: creates · Temp note skeleton.
- Note templates → Persistent notes: creates · Persistent note skeleton.
- Note templates → Analysis notes: creates · Analysis note skeleton.
- Users & agents → Temp chats: captures · Transient conversations start in temp notes.
- Temp chats → Persistent notes: promotes to · Useful temp notes are retained long-term.
- Persistent notes → Archive: retires to · Old persistent notes move into archive.
- Persistent notes → Analysis notes: feeds · Persistent notes are the source material for analysis.
- Users & agents → Attachments: attaches · Shared media and files are stored centrally.
- Profile → Profile example: contains · Public example profile lives in the profile area.
- Profile → Private profile: contains · Local-only personal profile is kept alongside the example.
- Profile example → Private profile: mirrors · Example profile shows the shape of the private file.
- Git policy → Private profile: excludes · Private profile is kept out of Git.