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.2 KiB
1.2 KiB
type, project, status, systems, work-items, related, updated, tags
| type | project | status | systems | work-items | related | updated | tags | |||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| workstream | fidelity | active |
|
|
|
2026-04-16 |
|
Flow And Page References
Goal
Keep recurring flow names, page names, and shorthand references aligned so debugging notes and external updates do not drift into ambiguous wording.
Current Mappings
-
HybridYouthAccountOpening- This is the real flow identifier when David refers to the Youth flow in recent AO validation discussions.
- The relevant page in this flow is
TeenIdentityCheck.
-
HybridBrokerageAccountOpening- This is the separate authenticated flow discussed alongside the Youth issue.
- The relevant page in this flow is
JointIdentityCheck.
Usage
- When drafting updates, prefer the real flow identifier if there is any risk that shorthand like
Youth floworHybridBrokeragecould be misunderstood. - When a shorthand is still useful for readability, keep the real flow ID available somewhere in the same session context.
- Capture additional stable flow/page mappings here when they come up repeatedly in debugging, standups, Jira comments, or consumer communication.