114 lines
2.4 KiB
Markdown
114 lines
2.4 KiB
Markdown
---
|
|
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
|
|
|
|
---
|
|
|
|
## Global Graph Defaults
|
|
|
|
The global graph is configured for onboarding and project navigation, not full filesystem inspection.
|
|
|
|
It intentionally hides generic technical filenames such as:
|
|
|
|
- `index`
|
|
- `README`
|
|
- `AGENTS`
|
|
- `SKILL`
|
|
|
|
Those files still exist and remain valid workspace files. They are hidden from the graph because Obsidian displays only the basename, which creates many indistinguishable nodes.
|
|
|
|
Use the file explorer or search when you need a specific technical file. Use the graph when you want to understand relationships between project concepts.
|
|
|
|
---
|
|
|
|
## When To Show Technical Files
|
|
|
|
Temporarily remove these filters from the graph search when debugging workspace internals:
|
|
|
|
```text
|
|
-file:index -file:README -file:AGENTS -file:SKILL
|
|
```
|
|
|
|
For normal onboarding, keep them hidden and navigate through the named maps.
|
|
|
|
---
|
|
|
|
## 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.
|