Files
fidelity-ai-workspace/vault/02-work-items/index.md
david.delagneau b82194bc55 Add daily logs and templates for Fidelity project
- 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.
2026-04-16 16:01:19 -06:00

1.5 KiB

type, project, updated, tags
type project updated tags
work-item-index fidelity 2026-04-16
work-item
map

Work Item Index

Goal

Provide a quick view of active and recently relevant Jira-linked work while keeping the full detail in one file per ticket.


Active

  • pdiap-14859.md PDIAP-14859 Spike - Research strategy to remove final UIKit wrapping from XFlowSDK and XFlowViewMaker without disrupting consumer implementation spike wrap-up work around dual UIKit/SwiftUI support, dynamic UIHostingController removal, consumer rollout planning, and linking the final result documents.

  • pdiap-15838.md PDIAP-15838 next story to work on; approved scope removes Apollo and GraphQL-specific iOS transport code while leaving REST.

  • pdiap-15836.md PDIAP-15836 approved follow-up story for dismissal delegate lifecycle sequencing in pure SwiftUI; comes after PDIAP-15838.

Active / Reopened

  • pdiap-15765.md PDIAP-15765 authenticated-only DOB issue in HybridYouthAccountOpening / TeenIdentityCheck; reopened around the iOS-only handling gap while the separate cross-platform HybridBrokerageAccountOpening / JointIdentityCheck scenario stays out of scope.

Usage

  • Read this file first for active ticket context.
  • Open the specific ticket file when you need exact scope, sequencing, or communication wording.
  • Update the per-ticket file first when ticket context changes materially.