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/memory-vault-model.md

@@ -1,4 +1,4 @@
-# Memory Vault Integration Model
+# Project Knowledge Memory Model
 
 ## Purpose
 
@@ -12,16 +12,16 @@ Obsidian is the current human-facing implementation, but the workspace should no
 
 ### Canonical Memory
 
-The source of truth is plain Markdown under `vault/`.
+The source of truth is plain Markdown under `project-knowledge/`.
 
 Agents should edit canonical notes directly when precision matters because direct edits produce auditable diffs.
 
 ### Memory Interface
 
-Use `scripts/memory/memory.sh` for vault-level operations:
+Use `scripts/memory/memory.sh` for project-knowledge operations:
 
 - `root` prints the configured memory root
-- `read <path>` reads a vault-relative note
+- `read <path>` reads a project-knowledge-relative note
 - `search <query> [folder]` searches memory
 - `create <type> <slug> [title]` creates a note in the canonical folder from the matching template
 - `base-query <base-name> [format]` queries a structured view when supported
@@ -37,9 +37,10 @@ If Obsidian CLI is unavailable or fails, `scripts/memory/memory.sh` falls back t
 
 ## Configuration
 
-- `AIW_MEMORY_VAULT_DIR`: canonical memory directory. Defaults to `<workspace-root>/vault`.
+- `AIW_PROJECT_KNOWLEDGE_DIR`: canonical project knowledge directory. Defaults to `<workspace-root>/project-knowledge`.
+- `AIW_MEMORY_VAULT_DIR`: transition alias for the canonical project knowledge directory.
 - `AIW_MEMORY_BACKEND`: `auto`, `files`, or `obsidian`. Defaults to `auto`.
-- `AIW_OBSIDIAN_VAULT_DIR`: Obsidian-specific vault override, still supported by the adapter.
+- `AIW_OBSIDIAN_VAULT_DIR`: Obsidian-specific transition alias, still supported by the adapter.
 - `AIW_OBSIDIAN_VAULT_NAME`: Obsidian URI vault name override for URI wrappers.
 
 Backend meanings:
@@ -54,15 +55,15 @@ Backend meanings:
 
 The memory interface owns type-to-folder routing:
 
-- `daily` -> `vault/06-daily/`
-- `work-item` -> `vault/02-work-items/`
-- `person` -> `vault/04-people/`
-- `decision` -> `vault/05-decisions/`
-- `system` -> `vault/03-context/systems/`
-- `workstream` -> `vault/03-context/workstreams/`
-- `meeting-note` -> `vault/06-daily/`
+- `daily` -> `project-knowledge/06-daily/`
+- `work-item` -> `project-knowledge/02-work-items/`
+- `person` -> `project-knowledge/04-people/`
+- `decision` -> `project-knowledge/05-decisions/`
+- `system` -> `project-knowledge/03-context/systems/`
+- `workstream` -> `project-knowledge/03-context/workstreams/`
+- `meeting-note` -> `project-knowledge/06-daily/`
 
-Templates live in `vault/09-templates/`.
+Templates live in `project-knowledge/09-templates/`.
 
 This gives agents an automatic destination for new notes without coupling the rule to Obsidian.
 
@@ -71,12 +72,12 @@ This gives agents an automatic destination for new notes without coupling the ru
 ## Agent Rules
 
 - Use the memory interface when creating new canonical notes from a known type.
-- Use the memory interface for broad search, Base queries, and vault health checks.
+- Use the memory interface for broad search, Base queries, and project knowledge health checks.
 - Prefer Obsidian CLI property operations for frontmatter/property edits when available, especially on existing notes that appear in Bases, because the CLI reduces YAML formatting drift.
 - Edit Markdown directly for precise memory curation, corrections, and content updates.
 - Do not treat Obsidian CLI failure as project context.
 - Do not require Obsidian to be running for core workspace operation.
-- Keep raw evidence outside `vault/`; promote only curated memory.
+- Keep raw evidence outside `project-knowledge/`; promote only curated memory.
 
 ---
 
@@ -88,6 +89,6 @@ When available, Obsidian CLI improves human-facing memory workflows:
 - `create path=... template=...` creates notes from templates.
 - `base:query` reads Bases as structured views.
 - `properties` and `property:*` inspect or update metadata.
-- `unresolved`, `orphans`, `links`, `backlinks`, and `tags` support vault health checks.
+- `unresolved`, `orphans`, `links`, `backlinks`, and `tags` support Obsidian/project knowledge health checks.
 
 These are optional enhancements. The canonical memory remains Markdown.