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

@@ -0,0 +1,84 @@
---
type: guide
audience: workspace-user
tags:
- onboarding
- obsidian
---
# Obsidian Usage Guide
Use Obsidian to navigate and review workspace memory. Do not use it as a separate memory database.
---
## Recommended Start
Open:
- [Obsidian Vault Map](obsidian-vault.md)
- [New Member Onboarding](onboarding.md)
- [Knowledge Maps](maps/index.md)
---
## Best Views
### New Member View
Start with:
- [New Member Onboarding](onboarding.md)
- [Glossary](glossary.md)
- [Current Work Map](maps/current-work.md)
- [Fidelity Domain Map](maps/fidelity-domain.md)
### Daily Work View
Start with:
- [Current Work Map](maps/current-work.md)
- [Work Items Map](maps/work-items.md)
- [Logs Index](../ai/logs/index.md)
### System Understanding View
Start with:
- [Fidelity Domain Map](maps/fidelity-domain.md)
- [AI Workspace Core Map](maps/ai-workspace-core.md)
- [Tooling Map](maps/tooling.md)
---
## Graph Guidance
Use the graph to find clusters, not to infer truth.
High-value graph hubs:
- `obsidian-vault`
- `onboarding`
- `current-work`
- `fidelity-domain`
- `work-items`
- `people`
- `tooling`
- `ai-workspace-core`
If a node is isolated, it may still be valid. It may be:
- a daily log
- raw evidence
- a command/prompt file
- a file that needs to be linked from a map
---
## Editing Rules
- Edit canonical memory files when the fact is clear.
- Prefer updating existing notes over adding duplicate summaries.
- Do not edit generated files as durable memory.
- Do not treat inbox files as confirmed truth.
- Use maps to improve navigation, not to store detailed facts.