feat: Add Obsidian vault configuration and documentation for navigation and memory management
This commit is contained in:
@@ -64,6 +64,8 @@ When drafting messages for a manager or stakeholder:
|
||||
|
||||
- Treat workspace files as persistent memory, not just reference notes
|
||||
- Treat `core/` as project-independent workspace logic and keep Fidelity-specific facts in profile/context files
|
||||
- Treat Obsidian as an optional navigation layer over the same Markdown files, not as a separate source of truth
|
||||
- Do not treat `.obsidian/workspace*.json`, plugin caches, or local Obsidian layout changes as project memory
|
||||
- Prefer generic `AIW_*` integration variables for new tooling while preserving `FIDELITY_*` fallbacks for compatibility
|
||||
- Before answering prompts about current work, verify `ai/state/current.md` and the latest relevant log in `ai/logs/`
|
||||
- Before answering architecture, process, or historical questions, check the relevant file under `ai/context/systems/`, `ai/context/workstreams/`, or `ai/context/process/`
|
||||
|
||||
Reference in New Issue
Block a user