Files
fidelity-ai-workspace/workspaces/fidelity/project-knowledge/00-start/onboarding.md
david.delagneau 1ad707373a Add daily logs and templates for project fidelity
- Created daily log entries for May 13, 14, 18, 19, 20, and 21, capturing work done, findings, and next steps.
- Established a daily logs index for easy navigation of daily notes.
- Developed templates for daily logs, decisions, meeting notes, people, systems, and work items to standardize documentation.
- Introduced base files for filtering and displaying various types of project knowledge, including daily notes, decisions, people, systems, work items, and workstreams.
- Added maps for current work, fidelity apps, and fidelity domain to enhance project navigation and context.
2026-05-21 12:28:07 -06:00

94 lines
2.9 KiB
Markdown

---
type: onboarding
audience: new-member
project: fidelity
updated: 2026-04-17
tags:
- onboarding
- map
---
# New Member Onboarding
Use this guide when someone new needs to understand the Fidelity project context quickly.
This vault is project knowledge, not the product codebase and not the agent implementation manual.
---
## First 30 Minutes
Read these in order:
1. [Start Here](start-here.md)
2. [Current Work Map](../07-maps/current-work.md)
3. [Fidelity Domain Map](../07-maps/fidelity-domain.md)
4. [Work Items Map](../07-maps/work-items.md)
5. [People Map](../07-maps/people.md)
Goal:
- understand where current work lives
- identify active tickets
- understand the main systems and people
- avoid treating raw logs or inbox evidence as confirmed durable truth
---
## First 60 Minutes
Read:
1. [Project Context](../03-context/project.md)
2. [XFlowSDK](../03-context/systems/xflowsdk.md)
3. [Fid4](../03-context/systems/fid4.md)
4. [REST Migration](../03-context/workstreams/rest-migration.md)
5. [AO And Discourse](../03-context/workstreams/ao-discourse.md)
6. [Communication](../03-context/process/communication.md)
Goal:
- understand why auth state, entry point, and backend configuration matter
- distinguish external reports from regressions
- understand why communication precision is part of the engineering workflow
---
## First 120 Minutes
Read:
1. [Systems Index](../03-context/systems/index.md)
2. [Workstreams Index](../03-context/workstreams/index.md)
3. [iOS Context](../03-context/ios/index.md)
4. [Jira Story Rules](../03-context/process/jira-story-rules.md)
5. [Pull Requests](../03-context/process/pull-requests.md)
Goal:
- understand how Fidelity project knowledge is organized
- know where to find durable systems, workstreams, people, decisions, and active tickets
- know the communication standards expected for standups, Jira, PRs, and manager updates
---
## Daily Workflow
1. Start from [Current Work Map](../07-maps/current-work.md).
2. Check [Current Work](../01-current/current-work.md).
3. Open the active work item from [Work Items Map](../07-maps/work-items.md).
4. Review the latest relevant note from [Daily Notes Index](../06-daily/index.md).
5. Use [Communication](../03-context/process/communication.md) before writing standups, Jira comments, or manager updates.
---
## Rules Of Thumb
- `workspaces/fidelity/project-knowledge/06-daily/` is dated work evidence.
- `workspaces/fidelity/project-knowledge/01-current/` is what matters now.
- `workspaces/fidelity/project-knowledge/02-work-items/` is canonical ticket memory.
- `workspaces/fidelity/project-knowledge/03-context/` is durable project knowledge.
- `workspaces/fidelity/project-knowledge/04-people/` is collaborator and role memory.
- `workspaces/fidelity/project-knowledge/05-decisions/` is durable decision history.
- `workspaces/fidelity/inbox/` and generated files are raw evidence, not promoted memory.