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.

◐

Decisions, lessons, current plan, who owns what — in one Capsule.

⊘

Redacted handoff with scope-safe context. Boundaries enforced.

◈

Bootstrap Capsule with lessons-as-guardrails. Lazy chunks fetched on demand.

02 Stream + Atlas

What the project shipped, learned, and decided this week. Catch up in fifteen minutes.

The connected map. Click a file, see every decision and lesson it inherits.

03 First-week checklist

One link. Decisions, plan, open threads, redaction summary.

Click into the codebase view. See decisions next to the code they shaped.

Promote a question into a personal-scope lesson. Future-you will thank you.

Ask your AI what it remembers. Verify the project memory is live.

Open ContextStream Code and start working with context loaded.

At week's end, hand a Capsule back. The team's context grows with you.