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.

profiles/example/profile.md

@@ -20,6 +20,7 @@ Non-sensitive example profile showing how a new project can reuse the workspace
 - Historical archive: optional
 - Recommended generic variables:
   - `AIW_PROJECT_PROFILE=example`
+  - `AIW_PROJECT_KNOWLEDGE_DIR=<optional custom project knowledge path>`
   - `AIW_CHANNEL_PREFIX=example`
   - `AIW_MATTERMOST_SYNC_CMD=<optional>`
   - `AIW_SLACK_EXPORT_PATH=<optional>`
@@ -28,8 +29,8 @@ Non-sensitive example profile showing how a new project can reuse the workspace
 
 ## Work System
 
-- Use `vault/02-work-items/` for active units of work
-- Use `vault/01-current/work-items.md` for the active summary
+- Use `project-knowledge/02-work-items/` for active units of work
+- Use `project-knowledge/01-current/work-items.md` for the active summary
 - Use any ticket ID format relevant to the project
 - Keep approved titles or explicit task names visible for recurring updates
 
@@ -37,9 +38,9 @@ Non-sensitive example profile showing how a new project can reuse the workspace
 
 ## Context
 
-Project-specific durable context should live under `vault/03-context/`.
+Project-specific durable context should live under `project-knowledge/03-context/`.
 
-People, decisions, daily notes, maps, and templates should live under the corresponding `vault/` folders.
+People, decisions, daily notes, maps, and templates should live under the corresponding `project-knowledge/` folders.
 
 Do not place company secrets, raw exports, credentials, or private communication transcripts in the profile.
 

profiles/fidelity/profile.md

@@ -32,6 +32,7 @@ Compatibility environment variables:
 
 Generic variables should be preferred for new setup:
 
+- `AIW_PROJECT_KNOWLEDGE_DIR`
 - `AIW_MATTERMOST_SYNC_CMD`
 - `AIW_MATTERMOST_SYNC_INTERVAL_MINUTES`
 - `AIW_SLACK_EXPORT_PATH`
@@ -43,16 +44,16 @@ Generic variables should be preferred for new setup:
 ## Work System
 
 - Work items are Jira-linked when available
-- Active ticket memory lives in `vault/02-work-items/`
-- Compact active summary lives in `vault/01-current/work-items.md`
+- Active ticket memory lives in `project-knowledge/02-work-items/`
+- Compact active summary lives in `project-knowledge/01-current/work-items.md`
 - Jira IDs and approved titles should remain visible for standups and manager updates
 
 ---
 
 ## Stakeholders
 
-- Current manager mapping lives in `vault/04-people/manager.md`
-- Person-specific collaboration context lives in `vault/04-people/`
+- Current manager mapping lives in `project-knowledge/04-people/manager.md`
+- Person-specific collaboration context lives in `project-knowledge/04-people/`
 - Manager-facing messages should be concise, explicit, and natural professional US English
 
 ---
@@ -61,14 +62,14 @@ Generic variables should be preferred for new setup:
 
 Core Fidelity context remains in:
 
-- `vault/03-context/project.md`
-- `vault/03-context/systems/`
-- `vault/03-context/workstreams/`
-- `vault/03-context/ios/`
-- `vault/03-context/process/`
-- `vault/05-decisions/`
+- `project-knowledge/03-context/project.md`
+- `project-knowledge/03-context/systems/`
+- `project-knowledge/03-context/workstreams/`
+- `project-knowledge/03-context/ios/`
+- `project-knowledge/03-context/process/`
+- `project-knowledge/05-decisions/`
 
-Raw communication evidence remains outside the vault under `ai/inbox/` and generated connector folders.
+Raw communication evidence remains outside the project knowledge vault under `ai/inbox/` and generated connector folders.
 
 Memory access should go through the project-agnostic `scripts/memory/` interface for note creation, search, Base queries, and health checks. Obsidian is the current visual and CLI adapter, not a Fidelity-specific dependency.