david.delagneau
374991a568
- 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.
51 lines
1.7 KiB
Markdown
51 lines
1.7 KiB
Markdown
---
|
|
type: system
|
|
project: fidelity
|
|
status: active
|
|
workstreams: [rest-migration, ao-discourse, xflow-debugging, xflow-swiftui-migration, consumer-integration]
|
|
related: [fid4, xflowviewmaker, ftframeworks, cogstore, pdiap-14859, pdiap-15765, pdiap-15836, pdiap-15838]
|
|
updated: 2026-04-16
|
|
tags:
|
|
- system
|
|
- fidelity
|
|
---
|
|
# XFlowSDK
|
|
|
|
## Role
|
|
|
|
XFlowSDK is the backend-driven UI engine that renders Fidelity flows from service-provided configuration.
|
|
|
|
---
|
|
|
|
## Durable Context
|
|
|
|
- XFlow behavior depends on backend rules, entry point, and authentication state.
|
|
- SwiftUI migration work introduced recurring behavior questions that were not just visual; many were contract or lifecycle issues.
|
|
- Historical Slack patterns show recurring topics around:
|
|
- component type expansion in SwiftUI
|
|
- Next-button visibility rules
|
|
- markdown link handling and analytics
|
|
- modal presentation and dismissal sequencing
|
|
- consumer-vs-framework ownership boundaries
|
|
|
|
---
|
|
|
|
## Debugging Implications
|
|
|
|
- Do not treat XFlow output as static UI; backend configuration can change the result.
|
|
- When behavior differs across environments, check whether the issue is:
|
|
- service/configuration driven
|
|
- auth-state driven
|
|
- entry-point driven
|
|
- consumer-integration driven
|
|
- Some apparent XFlow regressions historically turned out to be consumer, pipeline, or environment issues.
|
|
|
|
---
|
|
|
|
## Historical Signals From Slack
|
|
|
|
- SwiftUI behavior repeatedly needed parity work beyond UIKit assumptions.
|
|
- Next-button visibility logic required using the full set of service parameters, not only label text.
|
|
- Modal, delegate, and lifecycle sequencing became recurring themes in pure SwiftUI environments.
|
|
- XFlow work often had to be validated through consumer repositories, not only inside the SDK.
|