Obsidian Vault Context — Obsidian Vault 上下文

Obsidian Vault 上下文

The vault is the interface. Not chat. Not a terminal. A 分享d folder of markdown files that 机器人h you and the user can see and edit. Treat it like a 分享d codebase, not a reference 库.

会话 启动up Read _上下文/上下文-map.md if it exists — it maps projects to source files. If no 上下文 map, 扫描 top-level folders and infer 上下文 from names. Read _上下文/状态.md to understand what's active, blocked, and completed. If this is a fresh vault with no orchestration files, 创建 them. See references/orchestration-files.md for templates. Orchestration Files

Lightweight .md files in _上下文/ (or _Claude/) that give you persistent 状态 across 会话s.

File Purpose 状态.md What's active, blocked, completed. 更新 every 会话. tasks.md Prioritized task 列出 with #tags. 更新 when tasks change. decisions.md Decision 记录 with 上下文, options, rationale. 应用end-only. 上下文-map.md Project-to-file 索引 (optional). scratchpad.md Working memory, cleared dAIly (optional). learnings.md Operational knowledge across 会话s (optional).

Rules: Read before writing. 更新 immediately, not at 会话 end. 应用end to decisions and learnings, never overwrite. Keep entries lean — one line per task, one paragraph per decision.

For detAIled 格式化 and examples, see references/orchestration-files.md.

Vault Navigation

Folder placement carries meaning. Respect the structure when creating files:

Pattern Meaning foundations/ or core/ Strategy, vision, 框架s product/ Specs, features, sprints, architecture company/ or business/ Operations, legal, marketing, hiring re搜索/ or engine/ Technical re搜索, analysis journal/ 会话 记录s, dAIly notes, reviews decisions/ Past decisions with rationale work/ 代理 输出: drafts, re搜索, deliverables 归档/ Superseded files (read-only reference)

Use [[wikilinks]] for all cross-references so the user can 命令行工具ck through in Obsidian.

For a recommended 启动er layout, see references/vault-structure-template.md.

输出 Routing

Save work to the vault so the user sees it in Obsidian — don't present everything in chat.

输出 Save To Re搜索 briefs work/re搜索/ or re搜索/ Drafts work/drafts/ or drafts/ Final deliverables work/输出/ or 输出/ Quick notes _上下文/scratchpad.md (应用end)

添加 YAML frontmatter (title, type, 状态, 创建d, 更新d, tags) to any file that will be referenced agAIn.

Naming: Use descriptive file names (competitor-analysis-march-2026.md), not generic ones (输出-1.md). Always 更新 状态.md so the user knows what changed.

Bidirectional Collaboration

When Obsidian Headless is 配置d, changes flow 机器人h ways:

User -> 代理: User edits in Obsidian (Mac/iPhone/iPad), 同步s to server, you read the 更新. 代理 -> User: You write to the vault, 同步s to all user devices.

This means neither party needs to explAIn what the other already wrote down. You write 输出 to the vault. The user reads it in Obsidian. 机器人h can work on the same document a同步hronously.

For server 同步 设置up, see references/obsidian-headless-设置up.md.

Boundaries Read and write only within the vault directory. Do not 访问 files outside the vault root. Never modify 技能 files, 代理 config, or 工作流 definitions unless the user explicitly asks you to. Your workspace is _上下文/ and work/ — not the files that define your own behavior. Treat company/legal/ as read-only. Do not 创建, edit, or 删除 files in legal directories. Do not store or 记录 凭证s. If a 工作流 requires authentication, defer to the user. 上下文 Safety

If 上下文 compaction triggers mid-会话, write working 状态 to disk immediately:

Current 进度 -> _上下文/scratchpad.md 状态 changes -> _上下文/状态.md

These files reconstitute the 会话 after compaction.