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.

workspaces/fidelity/project-knowledge/04-people/erik-reynolds.md

@@ -0,0 +1,37 @@
+---
+type: person
+project: fidelity
+role: collaborator
+status: inactive
+updated: 2026-04-17
+tags:
+  - person
+  - fidelity
+---
+# Erik Reynolds
+
+## Role
+
+Historical Fidelity collaborator in XFlow-related discussions.
+
+- Previously worked for Fidelity but no longer does.
+
+---
+
+## Known Context
+
+- Appears in discussions about XFlow manager behavior, consumer-vs-framework boundaries, and migration constraints
+- Raises implementation and sizing concerns in architecture-heavy conversations
+- Often comments on where responsibility lies between XFlow and consuming teams
+- Deep archive signal suggests strong familiarity with XFlow and Apex internals, especially ownership boundaries and migration tradeoffs
+- Often challenged weak assumptions about architecture, sizing, and framework responsibilities
+- Useful source when deciding whether a problem belongs in XFlow, Apex, or the consumer app
+
+---
+
+## Guidance
+
+- Treat Erik as a relevant source when historical context touches XFlow ownership boundaries or migration difficulty
+- Treat Erik as a high-signal source for framework architecture and responsibility boundaries
+- Treat Erik as historical Fidelity context, not a current active stakeholder
+- If future context clarifies the formal role or team, update this file directly