2.6 KiB
2.6 KiB
type, audience, tags
| type | audience | tags | ||
|---|---|---|---|---|
| onboarding | new-member |
|
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:
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:
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:
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
- Start from Current Work Map.
- Check Current Work.
- Open the active work item from Work Items Map.
- Review the latest relevant log from Logs Index.
- Use Communication Rules 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.