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.
25 lines
1.3 KiB
Markdown
25 lines
1.3 KiB
Markdown
---
|
|
type: daily
|
|
project: fidelity
|
|
date: 2026-04-13
|
|
updated: 2026-04-16
|
|
tags:
|
|
- daily
|
|
- fidelity
|
|
---
|
|
# 2026-04-13
|
|
|
|
## Standup Context
|
|
|
|
- Corrected the approved title for `PDIAP-14859` to `Spike - Research strategy to remove final UIKit wrapping from XFlowSDK and XFlowViewMaker without disrupting consumer implementation`.
|
|
- Manual clarification for Monday standup: reference Friday work rather than the prior calendar day.
|
|
- Friday update for `PDIAP-14859`: created a draft rollout document for removing UIKit in favor of a SwiftUI-only path, including feature-flag planning.
|
|
- Today update: publish the rollout document for `PDIAP-14859` and continue with `PDIAP-15838` `Remove Apollo for iOS`.
|
|
- Standups should include story titles, not only Jira IDs, when the title is available.
|
|
|
|
## Mattermost Sync
|
|
|
|
- `PDIAP-14859`: sent Jeff the rollout draft for review after updating it around the global feature flag, broad `XQ1` validation, and the consumer-facing rollout flow.
|
|
- Jeff replied that he will review the `PDIAP-14859` document this morning.
|
|
- For `PDIAP-15765`, Jeff approved sending the config clarification that `CheckIdentity` was already correct and that `TeenIdentityCheck` needed the `validations` root key plus `eighteenOrAbove` inside `validation-rules`; the message was sent with an expected validation snippet.
|