david.delagneau
dbc1894e27
- 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.
2.8 KiB
type, project, updated, tags
| type | project | updated | tags | ||
|---|---|---|---|---|---|
| people-index | fidelity | 2026-04-17 |
|
People Index
Active Roles
- Manager: jeff-dewitte.md
Known People
-
jeff-dewitte.md Current direct manager for the active Fidelity project; repeated communication gatekeeper and scope shaper in historical XFlow work.
-
norman-arauz.md Former collaborator in historical Slack threads; primary implementer/investigator across SwiftUI, AO/Fid4 bugs, and release work, but no longer works with the current All-Win Software / Mattermost / Slack group.
-
david-delagneau.md Repeated historical collaborator on pipeline, CI/CD, and Sparta/SwiftUI proof-of-concept work, especially around Jenkins, reporting, and framework setup.
-
bruce-meeks.md Repeated XFlow collaborator who often reviewed PRs, covered iOS work during absences, and later shifted primarily toward Android.
-
jason-mandozzi.md Repeated collaborator tied to XFlowViewMaker, FTPlanning/Fid4 integration, release support, and major architectural transitions.
-
aylwing-olivas.md Repeated historical collaborator who surfaces architectural concerns, SwiftUI constraints, and cross-team dependency risks.
-
erik-reynolds.md Historical collaborator focused on XFlow manager behavior, integration boundaries, migration effort sizing, and framework responsibility boundaries; previously worked for Fidelity but no longer does.
-
gurram-santosh.md AO-related contact who often validates fixes or confirms whether issues still reproduce in consumer environments.
-
raj-sundararaj.md Repeated collaborator involved in AO issue triage, release coordination, and backlog/story management around XFlow work.
-
quy-mai.md Scrum/contact point who repeatedly managed backlog state, points, and closure expectations for Fidelity work.
-
tim-longfield.md FTPlanning-side contact relevant when issues crossed from XFlow into consumer-framework ownership.
-
derian-cordoba.md Historical collaborator in pipeline and documentation work, especially around CI/CD support and operational notes; no longer works with the current All-Win Software / Mattermost / Slack group.
-
tauf.md Taufiqur Ashrafy, often referred to as Tauf; CI/Jenkins support contact who helps with release-pipeline troubleshooting and related publication issues.
Usage
When a person appears repeatedly in project communication, create or update their file here so the agent can reuse:
- name
- role
- relationship to the project
- communication expectations
- important context about how they influence work