Add daily logs and templates for Fidelity project

- Created daily log entries for April 13-16, 2026, capturing standup contexts, Mattermost syncs, and ongoing work items.
- Established a daily logs index for easy navigation of daily entries.
- Introduced templates for daily notes, decisions, meeting notes, people, systems, and work items to standardize documentation.
- Developed maps for AI workspace core, current work, Fidelity domain, and work items to enhance workspace navigation.
- Implemented base configurations for daily notes, decisions, people, systems, work items, and workstreams to streamline data management.
- Added a placeholder for attachments to facilitate file organization.

.opencode/agents/fidelity.md

@@ -12,33 +12,35 @@ Behavior rules:
 
 - Treat `core/` as the reusable project-independent operating model.
 - Treat `profiles/fidelity/profile.md` as the active Fidelity project profile.
-- Treat `README.md`, `ai/context/`, `ai/state/`, `knowledge/`, and `ai/logs/` as the persistent memory of the project.
+- Treat `vault/` as the canonical clean knowledge base for humans and AI.
+- Treat `README.md`, `ai/context/`, `ai/state/`, `knowledge/`, and `ai/logs/` as legacy compatibility memory until the vault migration is fully retired.
 - Before answering a prompt that depends on current state, verify the latest relevant files instead of relying only on conversation history.
 - If the prompt asks for the latest Mattermost message, the last message from Jeff/current manager, or what someone just said, force a Mattermost refresh before answering and do not rely on stale inbox context.
 - For any meaningful prompt, decide whether the interaction adds, corrects, or sharpens project memory.
 - When the user provides new durable information, update the right workspace files before or while answering.
-- When the user corrects how the workspace should behave, update the linked operational surface too: commands in `.opencode/commands/`, prompt templates in `prompts/`, agent rules in `ai/AGENTS.md` or `.opencode/agents/`, skills in `.opencode/skills/`, and knowledge rules in `knowledge/` when those files control the behavior.
+- When the user corrects how the workspace should behave, update the linked operational surface too: commands in `.opencode/commands/`, prompt templates in `prompts/`, agent rules in `ai/AGENTS.md` or `.opencode/agents/`, skills in `.opencode/skills/`, and vault process rules in `vault/03-context/process/` when those files control the behavior.
 - If existing context is stale, correct it directly instead of leaving conflicting versions.
 - Promote information carefully:
-  - daily facts go to `ai/logs/YYYY-MM-DD.md`
-  - current priorities go to `ai/state/current.md`
-  - active Jira-linked work goes to `ai/work-items/*.md`
-  - the active-work summary goes to `ai/state/work-items.md`
-  - durable project knowledge overview goes to `ai/context/project.md`
-  - system-specific durable knowledge goes to `ai/context/systems/`
-  - workstream-specific durable knowledge goes to `ai/context/workstreams/`
-  - process-specific durable knowledge goes to `ai/context/process/`
-  - confirmed team or manager communication preferences go to `ai/context/people/manager.md`
-  - role-to-person mapping and recurring stakeholders go to `ai/context/people/`
-  - confirmed decisions go to `ai/context/decisions/`
-- behavioral rules for how this workspace should respond go to the exact command, prompt, agent, skill, or knowledge file that enforces that behavior
+  - daily facts go to `vault/06-daily/YYYY-MM-DD.md`
+  - current priorities go to `vault/01-current/current-work.md`
+  - active Jira-linked work goes to `vault/02-work-items/*.md`
+  - the active-work summary goes to `vault/01-current/work-items.md`
+  - durable project knowledge overview goes to `vault/03-context/project.md`
+  - system-specific durable knowledge goes to `vault/03-context/systems/`
+  - workstream-specific durable knowledge goes to `vault/03-context/workstreams/`
+  - process-specific durable knowledge goes to `vault/03-context/process/`
+  - confirmed team or manager communication preferences go to `vault/04-people/manager.md`
+  - role-to-person mapping and recurring stakeholders go to `vault/04-people/`
+  - confirmed decisions go to `vault/05-decisions/`
+- behavioral rules for how this workspace should respond go to the exact command, prompt, agent, skill, or vault process file that enforces that behavior
 - Use generic `AIW_*` integration variables for new tooling and keep `FIDELITY_*` only as compatibility aliases.
 - Default to writing new same-day information to today's log unless a more durable destination is clearly better.
+- If a canonical vault note exists, update it first; update legacy `ai/` or `knowledge/` files only when needed for compatibility.
 - Update preexisting memory when a new prompt clarifies or corrects something already stored.
 - Do not wait for a dedicated sync command if the correct memory update is already obvious.
 - Do not leave behavior-only corrections only in daily logs. If a correction should affect future output, update the tool or instruction that produces that output.
 - Do not over-promote uncertain information. Keep uncertain items in the daily log.
 - When drafting communication, preserve technical meaning and improve clarity in natural US English.
-- When answering Swift/iOS programming questions, use the project-local iOS skills and `ai/context/ios/`.
-- When generating prompts for GitHub Copilot or another AI, use `ai/context/process/ai-to-ai-prompting.md` and the `copilot-prompt-engineering` skill.
+- When answering Swift/iOS programming questions, use the project-local iOS skills and `vault/03-context/ios/`.
+- When generating prompts for GitHub Copilot or another AI, use `vault/03-context/process/ai-to-ai-prompting.md` and the `copilot-prompt-engineering` skill.
 - If the answer depends on current Apple APIs or Xcode/iOS behavior, verify with official Apple or Swift documentation before presenting it as current best practice.