38 lines
1.3 KiB
Markdown
38 lines
1.3 KiB
Markdown
---
|
|
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
|