Add project-knowledge structure and templates

- Introduced new maps for navigating project knowledge, including "Current Work," "Fidelity Domain," "Fidelity Apps," "Work Items," and "People."
- Created base files for daily notes, decisions, people, systems, work items, and workstreams with defined properties and views.
- Developed templates for daily notes, decisions, meeting notes, persons, systems, work items, and workstreams to standardize documentation.
- Updated scripts and prompts to reflect the new project-knowledge directory structure.
- Removed outdated onboarding and start-here documents, consolidating relevant information into the new maps.
- Ensured all references in workflows and scripts point to the new project-knowledge paths.

core/integrations/obsidian-model.md

@@ -2,7 +2,7 @@
 
 ## Purpose
 
-Use Obsidian as a visual navigation and manual review layer over the same canonical Markdown memory that powers the AI workspace.
+Use Obsidian as a visual navigation and manual review layer over canonical project knowledge.
 
 Obsidian should not become a second memory store.
 
@@ -10,36 +10,38 @@ Obsidian should not become a second memory store.
 
 ## Recommended Vault
 
-Open the `vault/` folder as the Obsidian vault:
+Open the `project-knowledge/` folder as the Obsidian vault:
 
 ```text
-<workspace-root>/vault/
+<workspace-root>/project-knowledge/
 ```
 
 This keeps one source of truth:
 
-- OpenCode and agents maintain operational memory
+- OpenCode and agents maintain project knowledge in Markdown
 - Obsidian reads and edits the same Markdown files
 - Git tracks intentional memory and configuration changes
 - runtime evidence and generated artifacts stay outside the vault
+- agent operating rules live outside the vault in `agent-memory/`
 
 ---
 
 ## Source Of Truth
 
-Canonical human/AI memory lives in:
+Canonical project knowledge lives in:
 
-- `vault/00-start/`
-- `vault/01-current/`
-- `vault/02-work-items/`
-- `vault/03-context/`
-- `vault/04-people/`
-- `vault/05-decisions/`
-- `vault/06-daily/`
-- `vault/07-maps/`
+- `project-knowledge/00-start/`
+- `project-knowledge/01-current/`
+- `project-knowledge/02-work-items/`
+- `project-knowledge/03-context/`
+- `project-knowledge/04-people/`
+- `project-knowledge/05-decisions/`
+- `project-knowledge/06-daily/`
+- `project-knowledge/07-maps/`
 
 Technical runtime remains outside the vault:
 
+- `agent-memory/`
 - `.opencode/`
 - `scripts/`
 - `core/`
@@ -48,7 +50,7 @@ Technical runtime remains outside the vault:
 - `scripts/*/generated/`
 - archives and local virtual environments
 
-Communication evidence may exist under `ai/inbox/` or connector `generated/` folders, but promoted memory belongs in `vault/`.
+Communication evidence may exist under `ai/inbox/` or connector `generated/` folders, but promoted memory belongs in `project-knowledge/`.
 
 ---
 
@@ -56,21 +58,21 @@ Communication evidence may exist under `ai/inbox/` or connector `generated/` fol
 
 Version portable Obsidian configuration only when it improves the workspace for every clone:
 
-- `vault/.obsidian/app.json`
-- `vault/.obsidian/core-plugins.json`
-- `vault/.obsidian/graph.json`
-- `vault/.obsidian/appearance.json`
-- `vault/.obsidian/daily-notes.json`
-- `vault/.obsidian/templates.json`
-- `vault/.obsidian/bookmarks.json`
+- `project-knowledge/.obsidian/app.json`
+- `project-knowledge/.obsidian/core-plugins.json`
+- `project-knowledge/.obsidian/graph.json`
+- `project-knowledge/.obsidian/appearance.json`
+- `project-knowledge/.obsidian/daily-notes.json`
+- `project-knowledge/.obsidian/templates.json`
+- `project-knowledge/.obsidian/bookmarks.json`
 
 Do not version local runtime state:
 
-- `vault/.obsidian/workspace*.json`
-- `vault/.obsidian/workspace-mobile*.json`
-- `vault/.obsidian/plugins/`
-- `vault/.obsidian/snippets/`
-- `vault/.obsidian/cache/`
+- `project-knowledge/.obsidian/workspace*.json`
+- `project-knowledge/.obsidian/workspace-mobile*.json`
+- `project-knowledge/.obsidian/plugins/`
+- `project-knowledge/.obsidian/snippets/`
+- `project-knowledge/.obsidian/cache/`
 
 Recommended graph and search exclusions:
 
@@ -99,13 +101,13 @@ Use Obsidian wiki-links only for Obsidian-only notes when there is a clear navig
 
 ## Agent Rules
 
-The agent may update Obsidian navigation notes when they improve discoverability.
+The agent may update Obsidian navigation notes when they improve project discoverability.
 
 The agent should not treat Obsidian runtime layout changes as project context.
 
 If Obsidian metadata or properties are added, use them selectively for high-value notes such as work items, decisions, and index pages. Do not mass-convert existing files just to add metadata.
 
-Use map notes under `vault/07-maps/` as graph hubs. This keeps the graph navigable without forcing every file into Obsidian-specific wiki-link syntax.
+Use map notes under `project-knowledge/07-maps/` as graph hubs. This keeps the graph navigable without forcing every file into Obsidian-specific wiki-link syntax.
 
 ---
 
@@ -132,7 +134,7 @@ Use `scripts/obsidian/` only as the current Obsidian adapter:
 
 - `cli.sh` runs the official Obsidian CLI from the configured vault directory.
 - `uri.sh` generates encoded Obsidian URIs.
-- `open.sh <vault-relative-path>` opens a note through Obsidian URI.
+- `open.sh <project-knowledge-relative-path>` opens a note through Obsidian URI.
 - `daily.sh` opens the configured daily note through Obsidian URI.
 - `search.sh <query>` opens Obsidian search through Obsidian URI.