93 lines
2.6 KiB
Markdown
93 lines
2.6 KiB
Markdown
---
|
|
type: onboarding
|
|
audience: new-member
|
|
tags:
|
|
- onboarding
|
|
- map
|
|
---
|
|
|
|
# New Member Onboarding
|
|
|
|
Use this guide when someone new needs to understand this workspace and the Fidelity project context quickly.
|
|
|
|
This repository is not the product codebase. It is the AI workspace used to preserve context, navigate project memory, and draft precise communication.
|
|
|
|
---
|
|
|
|
## First 30 Minutes
|
|
|
|
Read these in order:
|
|
|
|
1. [Obsidian Vault Map](obsidian-vault.md)
|
|
2. [Current Work Map](maps/current-work.md)
|
|
3. [Fidelity Domain Map](maps/fidelity-domain.md)
|
|
4. [Work Items Map](maps/work-items.md)
|
|
5. [People Map](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](../ai/context/project.md)
|
|
2. [XFlowSDK](../ai/context/systems/xflowsdk.md)
|
|
3. [Fid4](../ai/context/systems/fid4.md)
|
|
4. [REST Migration](../ai/context/workstreams/rest-migration.md)
|
|
5. [AO And Discourse](../ai/context/workstreams/ao-discourse.md)
|
|
6. [Communication Rules](communication-rules.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. [Operational Memory](../core/memory/operational-memory.md)
|
|
2. [Workspace Model](workspace-model.md)
|
|
3. [Agent Memory Rules](agent-memory-rules.md)
|
|
4. [Context Maintenance](../ai/context/process/context-maintenance.md)
|
|
5. [Tooling Map](maps/tooling.md)
|
|
|
|
Goal:
|
|
|
|
- understand how the AI workspace stays current
|
|
- know where to add new facts
|
|
- know when to update logs, state, work items, stable context, people, decisions, or tooling behavior
|
|
|
|
---
|
|
|
|
## Daily Workflow
|
|
|
|
1. Start from [Current Work Map](maps/current-work.md).
|
|
2. Check [Current Work](../ai/state/current.md).
|
|
3. Open the active work item from [Work Items Map](maps/work-items.md).
|
|
4. Review the latest relevant log from [Logs Index](../ai/logs/index.md).
|
|
5. Use [Communication Rules](communication-rules.md) before writing standups, Jira comments, or manager updates.
|
|
|
|
---
|
|
|
|
## Rules Of Thumb
|
|
|
|
- `ai/logs/` is evidence from a day.
|
|
- `ai/state/` is what matters now.
|
|
- `ai/work-items/` is canonical ticket memory.
|
|
- `ai/context/` is durable project knowledge.
|
|
- `ai/context/people/` is collaborator and role memory.
|
|
- `core/` is reusable workspace logic.
|
|
- `profiles/fidelity/` is Fidelity-specific configuration.
|
|
- `ai/inbox/` and generated files are evidence, not promoted memory.
|