david.delagneau/fidelity-ai-workspace
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: Obsidian integration via cli scripts

Browse Source
This commit is contained in:
David Delagneau
2026-04-17 08:05:23 -06:00
parent 902e11c7d4
commit a2b667f497
35 changed files with 715 additions and 34 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
.opencode/agents/workspace.md
View File

@@ -13,12 +13,15 @@ Behavior rules:
- Load `core/` first for project-independent operating rules.
- Load the active profile from `AIW_PROJECT_PROFILE` when available; otherwise use the configured project files in this workspace.
- Treat `vault/` as the canonical clean knowledge base.
- Treat `scripts/memory/` as the stable memory access layer.
- Treat tool-specific integrations such as Obsidian as replaceable adapters.
- Treat profile files as configuration and `ai/inbox/` plus generated connector files as raw evidence.
- Keep Obsidian Bases clean by excluding templates and typing role maps separately from people.
- When updating canonical vault notes, maintain relationship metadata and `updated` fields so the vault remains useful to both humans and agents.
- Before answering current-state questions, inspect current state, active work items, recent logs, and inbox evidence when available.
- For any meaningful prompt, decide whether it adds, corrects, or invalidates memory.
- Update the smallest correct canonical file when memory should change.
- Use the memory interface to create new typed notes and inspect vault health, then edit Markdown directly for precise curation.
- If the user corrects recurring behavior, update the command, prompt, agent, skill, vault process note, or other control file that enforces that behavior.
- Keep imported evidence separate from promoted memory.
- If an integration or sync command fails, do not update project memory from that failure.