feat: Add Obsidian vault configuration and documentation for navigation and memory management

This commit is contained in:
2026-04-16 12:12:31 -06:00
parent 53eb9dbc36
commit 1ab9472055
27 changed files with 1016 additions and 0 deletions

View File

@@ -115,11 +115,20 @@ Reference material for:
- XFlow behavior
- communication rules
- Fidelity-specific debugging heuristics
- Obsidian vault navigation
### /scripts
Helpers for future automation around context generation and communication drafting.
### /.obsidian
Optional Obsidian vault configuration.
Open the repository root as the vault. Obsidian should navigate and edit the same Markdown files used by OpenCode; it should not duplicate memory into a separate store.
Portable vault configuration can be versioned, while local layout and plugin runtime files are ignored.
---
## Daily Usage
@@ -252,6 +261,30 @@ The older `FIDELITY_*` variables remain supported for compatibility with this pr
---
## Obsidian Vault
This repository can be opened directly as an Obsidian vault.
Recommended entry point:
- `knowledge/obsidian-vault.md`
- `knowledge/onboarding.md` for new members
- `knowledge/glossary.md` for terminology
- `knowledge/obsidian-usage.md` for navigation rules
Use Obsidian for:
- visual navigation
- graph/backlink review
- manual review of work items, people, decisions, and logs
- lightweight editing of the same Markdown memory files
Do not use Obsidian as a second memory database. The source of truth remains the versioned Markdown files in this repository.
Ignored Obsidian runtime files include workspace layout, plugin cache, snippets, and local plugin installs.
---
## Creating Another Project
1. Copy `profiles/example/` to `profiles/<project>/`.