Ask
Codebase Q&A
Answers grounded in the live codebase, architecture decisions, and PR history, cited to the file and line.
Onboarding
New engineers spend months learning what the codebase already knows.
Ramp time is a context problem, not a talent problem.
Cosmos gives every engineer the organization’s full context from day one. Ask anything about the codebase in Slack or the IDE, get answers grounded in the real architecture and its history, and ship a first PR in days instead of months.
cosmos / onboarding · #eng-helpDay 2
Jordan · joined Monday
Where do we enforce tenant isolation for exports? I need to add a new export type.
Cosmos
Isolation is enforced in the export gateway, not per export type. Every handler goes through requireTenantScope() before the queue. Add your type in the registry and the gateway covers it. ADR-031 explains why it moved out of the handlers after the 2024 incident.
services/export/gateway.ts:142docs/adr/031-tenant-scoping.mdPR #3120
Can you scaffold the registry entry and tests for a CSV audit export?
Scaffolded · first PR opened · day 2
Meet Cosmos
Ramp in days, not quarters.
The Context Engine already understands your architecture, history, and conventions. Cosmos puts that understanding in front of every new engineer: cited answers, current docs, and a first ticket shipped with an expert alongside.
What changes for your team
Days
To a first merged PR for new engineers
6 mo
Industry median ramp time Cosmos replaces
24/7
An expert on the codebase, always available
0
Tribal knowledge lost when someone leaves
From first question to first merged PR.
Cosmos carries a new engineer through the whole ramp. Codebase Q&A answers with citations, living documentation stays current as the code changes, first tickets ship with an expert doing the heavy lifting, and the team’s conventions are taught in context. Mentors stay for the parts that need a human.
Ramp lifecycleone engineer, week one
Ask
Codebase Q&A
Answers grounded in the live codebase, architecture decisions, and PR history, cited to the file and line.
Learn
Living Documentation
READMEs, runbooks, and architecture docs that Cosmos regenerates as the code changes, so day one reads like the truth.
Ship
First Tickets
Well-scoped starter tickets shipped with Cosmos doing the heavy lifting and the new engineer steering and learning.
Grow
Team Conventions
The team's patterns, review standards, and definition of done, taught in context as the work happens.
Mentor
Mentors spend their time on design and growth, not repeating the same walkthrough.
Productive in days · context retained
Organizational Memory
Tribal knowledge captured · Survives departures · Grows with every question
Fig 1 · Ramp lifecycle
Where ramp time actually goes
Context in systems, not heads.
Most onboarding is a queue of interruptions: the new engineer waits on the people who hold the context, and the people who hold the context stop shipping. Cosmos moves that context into a system both can draw on.
Heads
How ramp works today
- Shadowing calendars and stale wikis
- Answers gated on whoever wrote the code
- Knowledge walks out the door with attrition
Systems
Ramp on Cosmos
- Ask the codebase directly, answers cited
- Docs regenerate as the code changes
- Every answer compounds in shared memory
- Mentors mentor instead of re-explaining
Slack
GitHub
Notion
ConfluenceRBAC · Visibility scopesHighly customizable to how your team learns.
Talk to Cosmos Advisor to shape the ramp: which repos and docs feed the answers, what new hires can see and do in their first weeks, and which starter tickets the team delegates. Visibility follows your RBAC from day one.
Works in the IDE too, with audit logs and SIEM out of the box.