Add daily logs and templates for project fidelity

- Created daily log entries for May 13, 14, 18, 19, 20, and 21, capturing work done, findings, and next steps.
- Established a daily logs index for easy navigation of daily notes.
- Developed templates for daily logs, decisions, meeting notes, people, systems, and work items to standardize documentation.
- Introduced base files for filtering and displaying various types of project knowledge, including daily notes, decisions, people, systems, work items, and workstreams.
- Added maps for current work, fidelity apps, and fidelity domain to enhance project navigation and context.
This commit is contained in:
2026-05-21 12:28:07 -06:00
parent 7cbb49134a
commit 1ad707373a
203 changed files with 449 additions and 434 deletions

View File

@@ -0,0 +1,54 @@
---
type: daily
project: fidelity
date: 2026-05-01
status: active
focus: [ao-discourse, xflow-debugging]
work-items: [pdiap-16167]
blockers: []
tags:
- daily
- fidelity
updated: 2026-05-04
---
# 2026-05-01
## Focus
- Verify and document the root cause for the FTTransfer AccountLink web-view reload issue.
---
## Work Done
- Prepared the root-cause report for the FTTransfer AccountLink issue.
- Verified that XFlow eventing does not appear to be the direct cause of the reload.
- Verified that the issue persists when rolling back `XFlowSDK` to `v0.1.0`, which predates REST and modern architecture changes.
- Identified a minimal presentation-anchor change that resolves the alert auto-dismiss and web-view reload behavior.
---
## Findings
- Current evidence points to a consumer SwiftUI presentation-layer issue rather than recent XFlowSDK or XFlowViewMaker changes.
- The rollback-to-`XFlowSDK v0.1.0` finding should be included in the report because it helps separate the issue from recent XFlow changes.
---
## Communication
- Jeff asked David to put the findings into a Confluence report, share it with Zachary, and comment it on the story.
- Jeff specifically asked David to include the XFlowSDK version / rollback evidence in the report.
---
## Next Steps
- Finalize and share the root-cause report with the rollback evidence and minimal fix note.
---
## Blockers
- None currently.