Files
fidelity-ai-workspace/vault/00-start/obsidian-usage.md
david.delagneau b82194bc55 Add daily logs and templates for Fidelity project
- Created daily log entries for April 13-16, 2026, capturing standup contexts, Mattermost syncs, and ongoing work items.
- Established a daily logs index for easy navigation of daily entries.
- Introduced templates for daily notes, decisions, meeting notes, people, systems, and work items to standardize documentation.
- Developed maps for AI workspace core, current work, Fidelity domain, and work items to enhance workspace navigation.
- Implemented base configurations for daily notes, decisions, people, systems, work items, and workstreams to streamline data management.
- Added a placeholder for attachments to facilitate file organization.
2026-04-16 16:01:19 -06:00

125 lines
2.8 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 the `vault/` folder as the Obsidian vault, not the repository root.
Open:
- [Obsidian Vault Map](start-here.md)
- [New Member Onboarding](onboarding.md)
- [Knowledge Maps](../07-maps/index.md)
---
## Best Views
### New Member View
Start with:
- [New Member Onboarding](onboarding.md)
- [Glossary](glossary.md)
- [Current Work Map](../07-maps/current-work.md)
- [Fidelity Domain Map](../07-maps/fidelity-domain.md)
### Daily Work View
Start with:
- [Current Work Map](../07-maps/current-work.md)
- [Work Items Map](../07-maps/work-items.md)
- [Logs Index](../06-daily/index.md)
### System Understanding View
Start with:
- [Fidelity Domain Map](../07-maps/fidelity-domain.md)
- [AI Workspace Core Map](../07-maps/ai-workspace-core.md)
- [Tooling Map](../07-maps/tooling.md)
---
## Graph Guidance
Use the graph to find clusters, not to infer truth.
High-value graph hubs:
- `start-here`
- `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.
---
## Daily Notes, Templates, And Bases
- Daily notes live under `06-daily/` and use `09-templates/daily.md`.
- Templates live under `09-templates/`.
- Bases live under `08-bases/` and use simple `type` properties.
- Bookmarks should keep `00-start/start-here.md`, `00-start/onboarding.md`, current work, work items, people, and high-value Bases easy to open.