05 / 05Use case · onboarding
Onboarding should start with what the project already knows.
Package decisions, lessons, docs, tasks, current plan, code understanding, and team wisdom into reusable onboarding context.
01 Three onboardings
Same package shape. Three audiences.
◐
New teammate
Decisions, lessons, current plan, who owns what — in one Capsule.
⊘
Client
Redacted handoff with scope-safe context. Boundaries enforced.
◈
Agent
Bootstrap Capsule with lessons-as-guardrails. Lazy chunks fetched on demand.
02 Stream + Atlas
Recent history meets connected history.
03 First-week checklist
Day-one context, not week-three context.
01
Open the onboarding Capsule
One link. Decisions, plan, open threads, redaction summary.
02
Walk the Atlas
Click into the codebase view. See decisions next to the code they shaped.
03
Capture your first lesson
Promote a question into a personal-scope lesson. Future-you will thank you.
04
Run a recall
Ask your AI what it remembers. Verify the project memory is live.
05
Pair on a session
Open ContextStream Code and start working with context loaded.
06
Emit a handoff
At week's end, hand a Capsule back. The team's context grows with you.