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.

vault/03-context/project.md

@@ -0,0 +1,72 @@
+---
+type: project-context
+project: fidelity
+updated: 2026-04-16
+tags:
+  - fidelity
+  - context
+---
+# Project Context - Fidelity
+
+## Overview
+
+This workspace supports daily iOS engineering work for Fidelity.
+
+The product work happens outside this repository, usually from another machine. This repository exists to preserve context, track communication, and help AI generate accurate output for standups, Mattermost messages, Jira notes, and supervisor updates.
+
+---
+
+## Fidelity Ecosystem
+
+- Fid4 is the main consumer iOS app
+- XFlowSDK powers backend-driven UI flows
+- XFlowViewMaker is an adapter layer under evaluation for removal
+- FTFrameworks contains feature modules such as FTAccountOpen and FTTransfer
+- Cogstore is the configuration publishing/version-tracking platform used to inspect which flow-definition versions are live in QA or Production
+
+---
+
+## Stable Context Map
+
+- Core systems live under:
+  - `vault/03-context/systems/`
+- Durable workstreams live under:
+  - `vault/03-context/workstreams/`
+- Stable communication and maintenance rules live under:
+  - `vault/03-context/process/`
+- Named people and role mapping live under:
+  - `vault/04-people/`
+
+The Slack archive has already been curated into those files so the agent does not need to rediscover the same patterns from raw history every session.
+
+---
+
+## Current Priorities
+
+- REST migration is replacing GraphQL over time, but REST is still behind a feature flag
+- AO and Discourse issues require careful classification because many are incomplete, external, or auth-dependent
+- XFlow debugging remains dynamic because behavior changes by entry point, authentication state, backend configuration, and consumer integration
+- Consumer validation often depends on Fid4, FT modules, and version propagation, not just SDK behavior
+
+---
+
+## Workspace Use
+
+This machine is used to:
+
+- maintain current project context
+- record findings from work performed elsewhere
+- capture communication that changes technical understanding
+- prepare polished updates for the current manager or stakeholder
+- generate standups with better context coverage
+
+This means the context files should hold durable engineering knowledge, while `vault/06-daily/` and `vault/01-current/` hold the moving day-to-day view.
+
+---
+
+## First Files To Read
+
+- `vault/03-context/index.md`
+- `vault/03-context/workstreams/index.md`
+- `vault/03-context/process/communication.md`
+- `vault/04-people/index.md`