Files

david.delagneau 374991a568 Refactor workspace structure and documentation

- Deleted obsolete files: obsidian-vault.md, onboarding.md, workspace-model.md
- Updated opencode.json to remove references to deleted files.
- Revised profile.md to clarify the status of legacy paths and communication evidence.
- Adjusted prompts to reflect new file paths and improve clarity.
- Enhanced daily logs with focus, work-items, and blockers properties.
- Updated work-item notes to include systems, workstreams, people, and related properties.
- Improved context maintenance guidelines to ensure accurate and durable project knowledge.
- Refined base filters to exclude template files and ensure only relevant notes are displayed.
- Updated daily templates to ensure proper formatting and consistency.
- Modified workflows to align with the new vault structure and improve context synchronization.

2026-04-16 16:28:30 -06:00

1.6 KiB

Raw Blame History

type, project, status, workstreams, related, updated, tags

type

project

status

workstreams

updated

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.

1.6 KiB Raw Blame History