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.

vault/00-start/obsidian-usage.md

@@ -87,6 +87,8 @@ It intentionally hides generic technical filenames such as:
 - `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.
 
@@ -120,5 +122,7 @@ For normal onboarding, keep them hidden and navigate through the named maps.
 
 - 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.
+- 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.

vault/00-start/workspace-architecture.md

@@ -50,8 +50,8 @@ Runtime and generated files can be used as evidence, but durable project facts s
 
 ---
 
-## Migration Rule
+## Memory Rule
 
-Legacy `ai/context`, `ai/state`, `ai/work-items`, `ai/logs`, and `knowledge` files may still exist for compatibility.
+Promoted memory lives in `vault/`.
 
-When a `vault/` equivalent exists, update `vault/` first.
+Raw inbox and generated connector evidence stays outside the vault until the agent promotes durable facts.