Files
fidelity-ai-workspace/vault/03-context/workstreams/flow-page-references.md
david.delagneau 374991a568 Refactor workspace structure and documentation
- Deleted obsolete files: obsidian-vault.md, onboarding.md, workspace-model.md
- Updated opencode.json to remove references to deleted files.
- Revised profile.md to clarify the status of legacy paths and communication evidence.
- Adjusted prompts to reflect new file paths and improve clarity.
- Enhanced daily logs with focus, work-items, and blockers properties.
- Updated work-item notes to include systems, workstreams, people, and related properties.
- Improved context maintenance guidelines to ensure accurate and durable project knowledge.
- Refined base filters to exclude template files and ensure only relevant notes are displayed.
- Updated daily templates to ensure proper formatting and consistency.
- Modified workflows to align with the new vault structure and improve context synchronization.
2026-04-16 16:28:30 -06:00

38 lines
1.2 KiB
Markdown

---
type: workstream
project: fidelity
status: active
systems: [xflowsdk, cogstore]
work-items: [pdiap-15765]
related: [ao-discourse, xflow-debugging]
updated: 2026-04-16
tags:
- workstream
- fidelity
---
# 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.