david.delagneau
b82194bc55
- Created daily log entries for April 13-16, 2026, capturing standup contexts, Mattermost syncs, and ongoing work items. - Established a daily logs index for easy navigation of daily entries. - Introduced templates for daily notes, decisions, meeting notes, people, systems, and work items to standardize documentation. - Developed maps for AI workspace core, current work, Fidelity domain, and work items to enhance workspace navigation. - Implemented base configurations for daily notes, decisions, people, systems, work items, and workstreams to streamline data management. - Added a placeholder for attachments to facilitate file organization.
40 lines
1.4 KiB
Markdown
40 lines
1.4 KiB
Markdown
---
|
|
type: system
|
|
project: fidelity
|
|
status: active
|
|
updated: 2026-04-16
|
|
tags:
|
|
- system
|
|
- fidelity
|
|
---
|
|
# Fid4
|
|
|
|
## Role
|
|
|
|
Fid4 is the main Fidelity consumer iOS app and the most important environment for validating real integration behavior.
|
|
|
|
---
|
|
|
|
## Durable Context
|
|
|
|
- Fid4 is the newer flagship-style app and is heavily SwiftUI-based.
|
|
- Validation in Fid4 often reveals issues that do not appear in XFlowSDK isolation or sample apps.
|
|
- Historical Slack context shows that some tickets were incorrectly scoped until behavior was checked in Fid4 or flagship.
|
|
- Real consumer testing in Fid4 matters for modal presentation, validation messaging, and backend-driven flow behavior.
|
|
|
|
---
|
|
|
|
## Validation Implications
|
|
|
|
- If an issue depends on real flow behavior, do not assume XFlow-only validation is sufficient.
|
|
- When a story touches presentation, entry points, or consumer behavior, check whether Fid4 is required to confirm scope.
|
|
- Build or startup instability in Fid4 can slow validation and should be treated as a practical investigation constraint.
|
|
|
|
---
|
|
|
|
## Historical Signals From Slack
|
|
|
|
- Fid4 was repeatedly referenced as the right place to verify SwiftUI/XFlow bugs before finalizing scope.
|
|
- Historical work included modal-on-modal presentation issues, goal/date validation behavior, and consumer-facing eventing questions.
|
|
- Some XFlow tickets needed rework because the original spike or story had not been validated in flagship/Fid4.
|