david.delagneau
dbc1894e27
- Introduced new maps for navigating project knowledge, including "Current Work," "Fidelity Domain," "Fidelity Apps," "Work Items," and "People." - Created base files for daily notes, decisions, people, systems, work items, and workstreams with defined properties and views. - Developed templates for daily notes, decisions, meeting notes, persons, systems, work items, and workstreams to standardize documentation. - Updated scripts and prompts to reflect the new project-knowledge directory structure. - Removed outdated onboarding and start-here documents, consolidating relevant information into the new maps. - Ensured all references in workflows and scripts point to the new project-knowledge paths.
1.4 KiB
1.4 KiB
type, project, date, focus, work-items, blockers, updated, tags
| type | project | date | focus | work-items | blockers | updated | tags | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| daily | fidelity | 2026-04-13 |
|
|
2026-04-16 |
|
2026-04-13
Standup Context
- Corrected the approved title for
PDIAP-14859toSpike - 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-14859and continue withPDIAP-15838Remove 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, broadXQ1validation, and the consumer-facing rollout flow.- Jeff replied that he will review the
PDIAP-14859document this morning. - For
PDIAP-15765, Jeff approved sending the config clarification thatCheckIdentitywas already correct and thatTeenIdentityCheckneeded thevalidationsroot key pluseighteenOrAboveinsidevalidation-rules; the message was sent with an expected validation snippet.