26 lines
1.0 KiB
Markdown
26 lines
1.0 KiB
Markdown
# 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 flow` or `HybridBrokerage` could 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.
|