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.

AGENTS.md

@@ -14,29 +14,31 @@ OpenCode should treat this project as a persistent context layer used to:
 The detailed operating rules live in:
 
 - `ai/AGENTS.md`
-- `ai/context/index.md`
-- `ai/context/project.md`
-- `ai/context/ios/index.md`
-- `ai/context/ios/current-practices.md`
-- `ai/context/ios/project-swift-guidance.md`
-- `ai/context/systems/index.md`
-- `ai/context/workstreams/index.md`
-- `ai/context/process/communication.md`
-- `ai/context/process/ai-to-ai-prompting.md`
-- `ai/context/people/manager.md`
-- `ai/context/people/index.md`
-- `ai/work-items/index.md`
-- `ai/state/current.md`
-- `ai/state/work-items.md`
-- `knowledge/workspace-model.md`
-- `knowledge/communication-rules.md`
+- `vault/00-start/start-here.md`
+- `vault/00-start/workspace-architecture.md`
+- `vault/01-current/current-work.md`
+- `vault/01-current/work-items.md`
+- `vault/03-context/project.md`
+- `vault/03-context/ios/index.md`
+- `vault/03-context/ios/current-practices.md`
+- `vault/03-context/ios/project-swift-guidance.md`
+- `vault/03-context/systems/index.md`
+- `vault/03-context/workstreams/index.md`
+- `vault/03-context/process/communication.md`
+- `vault/03-context/process/ai-to-ai-prompting.md`
+- `vault/03-context/process/workspace-model.md`
+- `vault/03-context/process/memory-promotion-rules.md`
+- `vault/04-people/manager.md`
+- `vault/04-people/index.md`
+- `vault/02-work-items/index.md`
 
 These are also loaded through `opencode.json`.
 
 ## Required Behavior
 
 - Assume the workspace may contain stale context until checked.
-- Before answering questions that depend on current work state, inspect `ai/state/current.md` and the latest relevant log under `ai/logs/`.
+- Treat `vault/` as the canonical clean memory for humans and AI. Legacy `ai/*` and `knowledge/*` paths are temporary compatibility fallback.
+- Before answering questions that depend on current work state, inspect `vault/01-current/current-work.md` and the latest relevant daily note under `vault/06-daily/`.
 - If `ai/inbox/mattermost-latest.md` exists, inspect it for fresher communication context before answering standup, status, or manager-message prompts.
 - 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 instead of relying on existing inbox context.
 - If automatic refresh is uncertain, use the explicit latest-message flow: run the Mattermost sync command, then answer from the refreshed inbox only.
@@ -44,12 +46,12 @@ These are also loaded through `opencode.json`.
 - If a sync command, extraction script, or inbox refresh fails, do not update logs, state, or context files from that failed attempt.
 - Treat sync failures as operational errors, not project context.
 - `mattermost-sync` should automatically promote high-confidence project facts without asking what to promote.
-- Prefer `ai/logs/` as the default destination for new Mattermost-derived facts.
-- Promote to `ai/state/current.md` only when the fact materially changes active work over the next few days.
-- Keep explicit Jira IDs and approved titles visible in `ai/work-items/` and summarize active items in `ai/state/work-items.md` when they are useful for future standups or manager updates.
-- Promote to `ai/context/project.md` only when the fact changes durable project understanding.
-- When a repeatedly mentioned person becomes relevant to project flow, create or update a file under `ai/context/people/`.
-- Keep role-to-person mapping explicit in `ai/context/people/manager.md` and the roster in `ai/context/people/index.md`.
+- Prefer `vault/06-daily/` as the default destination for new Mattermost-derived facts.
+- Promote to `vault/01-current/current-work.md` only when the fact materially changes active work over the next few days.
+- Keep explicit Jira IDs and approved titles visible in `vault/02-work-items/` and summarize active items in `vault/01-current/work-items.md` when they are useful for future standups or manager updates.
+- Promote to `vault/03-context/project.md` only when the fact changes durable project understanding.
+- When a repeatedly mentioned person becomes relevant to project flow, create or update a file under `vault/04-people/`.
+- Keep role-to-person mapping explicit in `vault/04-people/manager.md` and the roster in `vault/04-people/index.md`.
 - Never promote tooling chatter, sync status, or generic conversation noise.
 - Direct user prompts are also memory sources. Do not limit memory updates to explicit sync commands.
 - If a new prompt corrects prior understanding, update the canonical file directly instead of keeping both versions alive.
@@ -58,9 +60,9 @@ These are also loaded through `opencode.json`.
 - If a previous context file is now stale or inaccurate, update that file directly.
 - Prefer correcting canonical context over appending contradictory notes.
 - Keep changes concise and auditable.
-- When the topic is architectural or historical, prefer updating the relevant file under `ai/context/systems/`, `ai/context/workstreams/`, or `ai/context/process/` instead of overloading `ai/context/project.md`.
-- When the user asks Swift, SwiftUI, iOS architecture, testing, or debugging questions, use `ai/context/ios/` and the local OpenCode iOS skills before answering.
-- When the user asks for a prompt for another AI, GitHub Copilot, or the Fidelity development machine, use `ai/context/process/ai-to-ai-prompting.md` and generate a self-contained prompt.
+- When the topic is architectural or historical, prefer updating the relevant file under `vault/03-context/systems/`, `vault/03-context/workstreams/`, or `vault/03-context/process/` instead of overloading `vault/03-context/project.md`.
+- When the user asks Swift, SwiftUI, iOS architecture, testing, or debugging questions, use `vault/03-context/ios/` and the local OpenCode iOS skills before answering.
+- When the user asks for a prompt for another AI, GitHub Copilot, or the Fidelity development machine, use `vault/03-context/process/ai-to-ai-prompting.md` and generate a self-contained prompt.
 - If a Swift/iOS recommendation depends on current Apple APIs, Xcode behavior, or framework migration guidance, verify against official Apple or Swift documentation before making strong claims.
 
 ## Communication