Add daily logs and templates for project fidelity

- Created daily log entries for May 13, 14, 18, 19, 20, and 21, capturing work done, findings, and next steps.
- Established a daily logs index for easy navigation of daily notes.
- Developed templates for daily logs, decisions, meeting notes, people, systems, and work items to standardize documentation.
- Introduced base files for filtering and displaying various types of project knowledge, including daily notes, decisions, people, systems, work items, and workstreams.
- Added maps for current work, fidelity apps, and fidelity domain to enhance project navigation and context.

profiles/fidelity/profile.md

@@ -20,7 +20,7 @@ It keeps Fidelity-specific context, integrations, commands, and skills separate
 ## Communication Sources
 
 - Live communication: Mattermost
-- Preferred local Mattermost evidence source: proxy mirror under `ai/inbox/mattermost-mirror/` when present; legacy `ai/inbox/mattermost-latest.md` and `scripts/mattermost/generated/` are fallback evidence.
+- Preferred local Mattermost evidence source: proxy mirror under `workspaces/fidelity/inbox/mattermost-mirror/` when present; legacy `workspaces/fidelity/inbox/mattermost-latest.md` and `scripts/mattermost/generated/` are fallback evidence.
 - Historical archive: Slack export
 - Preferred channel naming: readable channel names instead of raw IDs
 - Current high-signal channel: `fidelity-preguntas`
@@ -47,16 +47,16 @@ Generic variables should be preferred for new setup:
 ## Work System
 
 - Work items are Jira-linked when available
-- Active ticket memory lives in `project-knowledge/02-work-items/`
-- Compact active summary lives in `project-knowledge/01-current/work-items.md`
+- Active ticket memory lives in `workspaces/fidelity/project-knowledge/02-work-items/`
+- Compact active summary lives in `workspaces/fidelity/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 `project-knowledge/04-people/manager.md`
-- Person-specific collaboration context lives in `project-knowledge/04-people/`
+- Current manager mapping lives in `workspaces/fidelity/project-knowledge/04-people/manager.md`
+- Person-specific collaboration context lives in `workspaces/fidelity/project-knowledge/04-people/`
 - Manager-facing messages should be concise, explicit, and natural professional US English
 
 ---
@@ -65,14 +65,14 @@ Generic variables should be preferred for new setup:
 
 Core Fidelity context remains in:
 
-- `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/`
+- `workspaces/fidelity/project-knowledge/03-context/project.md`
+- `workspaces/fidelity/project-knowledge/03-context/systems/`
+- `workspaces/fidelity/project-knowledge/03-context/workstreams/`
+- `workspaces/fidelity/project-knowledge/03-context/ios/`
+- `workspaces/fidelity/project-knowledge/03-context/process/`
+- `workspaces/fidelity/project-knowledge/05-decisions/`
 
-Raw communication evidence remains outside the project knowledge vault under `ai/inbox/` and generated connector folders.
+Raw communication evidence remains outside the project knowledge vault under `workspaces/fidelity/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.
 

profiles/fidelity/workspace.json

@@ -1,8 +1,8 @@
 {
   "profile": "fidelity",
   "display_name": "Fidelity",
-  "description": "Current Fidelity AI Workspace profile. Paths intentionally point to the existing root-level vault and inbox until the data migration phase.",
-  "knowledge_dir": "project-knowledge",
-  "inbox_dir": "ai/inbox",
+  "description": "Current Fidelity AI Workspace profile with isolated profile-owned data paths.",
+  "knowledge_dir": "workspaces/fidelity/project-knowledge",
+  "inbox_dir": "workspaces/fidelity/inbox",
   "index_dir": ".aiw/indexes/fidelity"
 }