- Introduced new maps for navigating project knowledge, including "Current Work," "Fidelity Domain," "Fidelity Apps," "Work Items," and "People." - Created base files for daily notes, decisions, people, systems, work items, and workstreams with defined properties and views. - Developed templates for daily notes, decisions, meeting notes, persons, systems, work items, and workstreams to standardize documentation. - Updated scripts and prompts to reflect the new project-knowledge directory structure. - Removed outdated onboarding and start-here documents, consolidating relevant information into the new maps. - Ensured all references in workflows and scripts point to the new project-knowledge paths.
1.3 KiB
1.3 KiB
type, project, role, status, updated, tags
| type | project | role | status | updated | tags | ||
|---|---|---|---|---|---|---|---|
| person | fidelity | collaborator | inactive | 2026-04-17 |
|
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