david.delagneau/fidelity-ai-workspace
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
a1cec956abecb0d348a2aa5024970e531611063e
fidelity-ai-workspace/vault/00-start/obsidian-usage.md
david.delagneau 374991a568 Refactor workspace structure and documentation 
- Deleted obsolete files: obsidian-vault.md, onboarding.md, workspace-model.md
- Updated opencode.json to remove references to deleted files.
- Revised profile.md to clarify the status of legacy paths and communication evidence.
- Adjusted prompts to reflect new file paths and improve clarity.
- Enhanced daily logs with focus, work-items, and blockers properties.
- Updated work-item notes to include systems, workstreams, people, and related properties.
- Improved context maintenance guidelines to ensure accurate and durable project knowledge.
- Refined base filters to exclude template files and ensure only relevant notes are displayed.
- Updated daily templates to ensure proper formatting and consistency.
- Modified workflows to align with the new vault structure and improve context synchronization.
2026-04-16 16:28:30 -06:00

3.2 KiB
Raw Blame History

type, audience, tags
type audience tags
guide workspace-user
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:

Best Views

New Member View

Start with:

Daily Work View

Start with:

System Understanding View

Start with:

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
  • 08-bases
  • 09-templates

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:

-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 plus a folder exclusion for 09-templates/.
  • Templates may contain the final note type so newly created notes are useful immediately, but Bases must exclude the template folder so template files do not appear as data rows.
  • Role mapping files such as 04-people/manager.md should use type: role-map, not type: person.
  • Bookmarks should keep 00-start/start-here.md, 00-start/onboarding.md, current work, work items, people, and high-value Bases easy to open.
Reference in New Issue View Git Blame Copy Permalink