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.
42 lines
1.3 KiB
Markdown
42 lines
1.3 KiB
Markdown
---
|
|
type: system
|
|
project: fidelity
|
|
status: active
|
|
updated: 2026-04-16
|
|
tags:
|
|
- system
|
|
- fidelity
|
|
---
|
|
# FTFrameworks
|
|
|
|
## Role
|
|
|
|
FTFrameworks contains consumer-side feature modules such as FTAccountOpen, FTTransfer, and related libraries that mediate how XFlow changes reach Fid4.
|
|
|
|
---
|
|
|
|
## Durable Context
|
|
|
|
- FTFrameworks is often part of the real validation and release chain, not just a downstream detail.
|
|
- Historical Slack context shows pinned FT module versions repeatedly blocking adoption of newer XFlow or XFlowViewMaker changes in Fid4.
|
|
- Changes to XFlow often needed corresponding FTAccountOpen or FTTransfer updates before end-to-end testing was realistic.
|
|
|
|
---
|
|
|
|
## Validation And Release Implications
|
|
|
|
- If Fid4 does not reflect the expected XFlow fix, check FT module versions before concluding the SDK change failed.
|
|
- Version movement can require a chain such as:
|
|
- XFlowSDK
|
|
- XFlowViewMaker
|
|
- FTAccountOpen / FTTransfer
|
|
- Fid4
|
|
- Test failures or publishing issues in FT modules can delay consumer validation even when the core XFlow change is ready.
|
|
|
|
---
|
|
|
|
## Historical Signals From Slack
|
|
|
|
- FTAccountOpen and FTTransfer were repeatedly mentioned in version bump and release coordination work.
|
|
- Historical messages also tied FTFrameworks to FTAuth and MFA-related stories, showing that dependency understanding matters when sizing or scoping work.
|