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.

ai/AGENTS.md

@@ -8,6 +8,8 @@ This workspace is used to maintain context, organize communication, and draft ac
 
 The reusable operating model lives in `core/`. Fidelity is the active project profile in `profiles/fidelity/`.
 
+The canonical clean knowledge base now lives in `vault/`. Legacy `ai/` and `knowledge/` paths remain as compatibility references during migration.
+
 ---
 
 ## Primary Responsibilities
@@ -63,29 +65,30 @@ When drafting messages for a manager or stakeholder:
 ## Context Maintenance
 
 - Treat workspace files as persistent memory, not just reference notes
+- Treat `vault/` as canonical memory when a vault equivalent exists
 - Treat `core/` as project-independent workspace logic and keep Fidelity-specific facts in profile/context files
 - Treat Obsidian as an optional navigation layer over the same Markdown files, not as a separate source of truth
-- Do not treat `.obsidian/workspace*.json`, plugin caches, or local Obsidian layout changes as project memory
+- Do not treat `vault/.obsidian/workspace*.json`, plugin caches, or local Obsidian layout changes as project memory
 - Prefer generic `AIW_*` integration variables for new tooling while preserving `FIDELITY_*` fallbacks for compatibility
-- Before answering prompts about current work, verify `ai/state/current.md` and the latest relevant log in `ai/logs/`
-- Before answering architecture, process, or historical questions, check the relevant file under `ai/context/systems/`, `ai/context/workstreams/`, or `ai/context/process/`
-- Before answering Swift, SwiftUI, iOS architecture, testing, or debugging questions, check `ai/context/ios/` and use the project-local iOS skills when available
-- Before generating a prompt for another AI or GitHub Copilot, check `ai/context/process/ai-to-ai-prompting.md` and make the prompt self-contained
+- Before answering prompts about current work, verify `vault/01-current/current-work.md` and the latest relevant daily note in `vault/06-daily/`
+- Before answering architecture, process, or historical questions, check the relevant file under `vault/03-context/systems/`, `vault/03-context/workstreams/`, or `vault/03-context/process/`
+- Before answering Swift, SwiftUI, iOS architecture, testing, or debugging questions, check `vault/03-context/ios/` and use the project-local iOS skills when available
+- Before generating a prompt for another AI or GitHub Copilot, check `vault/03-context/process/ai-to-ai-prompting.md` and make the prompt self-contained
 - If `ai/inbox/mattermost-latest.md` exists, check it before answering prompts about current status, standups, or supervisor communication
 - If the user asks for the latest/last/recent Mattermost message, the latest message from Jeff/current manager, or what someone just said, synchronize Mattermost first and then answer from the refreshed inbox
 - If automatic refresh is uncertain, use the explicit latest-message flow: run the Mattermost sync command, then answer from refreshed output only
 - Treat all meaningful user prompts as potential memory updates, not only explicit sync commands
 - Treat meaningful user corrections about workspace behavior as tool-maintenance inputs, not only as notes. If a correction affects a command, prompt, agent, skill, or knowledge rule, update that linked file directly.
-- If a Mattermost sync or other context-ingestion step fails, do not update `ai/logs/`, `ai/state/`, or stable context files based on that failure
+- If a Mattermost sync or other context-ingestion step fails, do not update `vault/06-daily/`, `vault/01-current/`, or stable context files based on that failure
 - Do not record missing dependencies, failed sync attempts, or missing inbox files as project facts unless the user explicitly asks to track the operational issue
 - Auto-promote Mattermost content when it is clearly project-relevant, explicit, and high-confidence
 - Auto-promote direct user-provided project facts when they are clearly project-relevant, explicit, and useful for future sessions
-- Default promotion target is today's log
-- Promote to `ai/state/current.md` only when the fact changes the active work window
-- Maintain `ai/work-items/` as the canonical memory for active Jira-linked work and keep `ai/state/work-items.md` as the quick summary layer
-- Promote to `ai/context/project.md` only when the fact is durable beyond the current work window
-- Use `ai/context/project.md` as the overview only; put system-specific, workstream-specific, and process-specific durable context in the corresponding subdirectory
-- Maintain `ai/context/people/` when repeated names, roles, or stakeholder relationships become useful for future sessions
+- Default promotion target is `vault/06-daily/YYYY-MM-DD.md`
+- Promote to `vault/01-current/current-work.md` only when the fact changes the active work window
+- Maintain `vault/02-work-items/` as the canonical memory for active Jira-linked work and keep `vault/01-current/work-items.md` as the quick summary layer
+- Promote to `vault/03-context/project.md` only when the fact is durable beyond the current work window
+- Use `vault/03-context/project.md` as the overview only; put system-specific, workstream-specific, and process-specific durable context in the corresponding subdirectory
+- Maintain `vault/04-people/` when repeated names, roles, or stakeholder relationships become useful for future sessions
 - Update existing memory when the new information is a correction, clarification, or refinement of something already stored
 - Prefer updating stable project context over appending generic operational summaries
 - Do not leave reusable behavior rules only in daily logs. Promote them to the prompt, command, agent, skill, or process file that controls future behavior.
@@ -95,18 +98,18 @@ When drafting messages for a manager or stakeholder:
 - Do not ask the user what should be promoted after a successful sync unless multiple conflicting interpretations are equally plausible
 - When the user shares relevant new information, update today's log if the information belongs to the daily record
 - When the user corrects or changes stable context, update the canonical file directly:
-  - `ai/state/current.md` for current focus or active concerns
-  - `ai/context/project.md` for durable project knowledge
-  - `ai/context/people/manager.md` for communication preferences
-  - `ai/context/people/index.md` for active roster mapping
-  - `ai/context/people/<person>.md` for person-specific context
-  - `ai/context/decisions/*.md` for confirmed decisions
+  - `vault/01-current/current-work.md` for current focus or active concerns
+  - `vault/03-context/project.md` for durable project knowledge
+  - `vault/04-people/manager.md` for communication preferences
+  - `vault/04-people/index.md` for active roster mapping
+  - `vault/04-people/<person>.md` for person-specific context
+  - `vault/05-decisions/*.md` for confirmed decisions
 - If the new fact changes how this workspace should operate, update the linked tool surface as well:
   - `.opencode/commands/*.md` for slash-command behavior
   - `prompts/*.md` for reusable output templates
   - `.opencode/agents/*.md` and `ai/AGENTS.md` for default agent behavior
   - `.opencode/skills/*/SKILL.md` for specialized workflows
-  - `knowledge/*.md` or `ai/context/process/*.md` for durable process rules
+  - `vault/00-start/*.md` or `vault/03-context/process/*.md` for durable process rules
 - Prefer updating stale context over leaving conflicting statements in different files
 - If context is still uncertain, record it in the daily log rather than promoting it to a stable context file