- 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.
36 lines
1.1 KiB
Markdown
36 lines
1.1 KiB
Markdown
---
|
|
type: person
|
|
project: fidelity
|
|
role: collaborator
|
|
status: inactive
|
|
updated: 2026-04-17
|
|
tags:
|
|
- person
|
|
- fidelity
|
|
---
|
|
# Norman Arauz
|
|
|
|
## Role
|
|
|
|
Frequent Fidelity/XFlow engineer collaborator in historical Slack threads.
|
|
|
|
- No longer works with the current All-Win Software / Mattermost / Slack collaboration group.
|
|
|
|
---
|
|
|
|
## Known Context
|
|
|
|
- Repeated day-to-day implementer/investigator across XFlow SwiftUI, AO/Fid4 bugs, version bumps, analytics, and pipeline debugging
|
|
- Often coordinated with Jeff on scope, descriptions, approvals, and manager-ready wording
|
|
- Frequently investigated consumer-reported issues directly in Fid4 and sample-app parity checks
|
|
- Often produced detailed technical findings first, then asked Jeff to polish or approve external wording
|
|
- Exact formal role may need confirmation if used outside workspace memory
|
|
|
|
---
|
|
|
|
## Guidance
|
|
|
|
- Treat Norman as a strong source for historical implementation detail, reproduction findings, and release-process context
|
|
- Treat Norman as historical context, not a current active collaborator
|
|
- If later communication clarifies the formal team/title, update this file directly
|