Code and decisions
Every file carries the decisions, trade-offs and lessons that shaped it. No more working out why from scratch.
02 / 06Knowledge Atlas
Project history, mapped into agent-ready context.
The Stream is what’s new. The Atlas is what’s connected. Knowledge Atlas links decisions, lessons, code, docs, tasks, sessions and project history into a graph you can query, so agents find the right context, not just the most recent.
DecisionLessonGuardrailTaskDocSessionCode
01Connected, not stored
Decisions and lessons live next to the code, docs, sessions and tasks they affect.
Many memory tools store snippets. The Atlas stores relationships, so when an agent reads auth/session.ts, it also sees the decision that shaped it, the lesson that constrains it and the open task that depends on it.
Lessons and guardrails
A lesson becomes a guardrail on the code it protects. The same fact, in two roles.
Docs and sessions
Indexed READMEs and runbooks attach to the sessions that actually used them.
02Right context, not most recent
An agent asks. The Atlas answers with the right slice.
The answer follows relationships from the file to what shaped it, three hops at most, and cites each node it returns.
Agent query
What should I know before editing auth/session.ts?
Traversal · 3 hops · 7 nodes · 11 edges
- Decision
Use Postgres row-level security for tenant isolation.
- Lesson
Don’t hand-roll session expiry. Use the helper.
- Guardrail
Never log raw session tokens.
- Doc
auth/threat-model.md
- Open task
Rotate signing keys before launch.
03Two views, one context graph
Code graph. Knowledge graph. Same Atlas.
Files, concepts, decisions and lessons share one graph. Switch the view; what it describes stays the same.
Code view
Files, symbols, call sites and ownership.
Import, reference and ownership graphs derived from the source. Sanitised, never stored.
Knowledge view
Decisions, lessons, sessions and threads.
Knowledge connected by who learned it, where it was used and which code it protects.
04From graph to agent
Every surface reads the same Atlas.
MCP traversal
MCP-compatible tools query the Atlas and get scoped, source-backed answers.
ContextStream Code
The first-party CLI checks the Atlas before every edit and shows related context inline.
Capsules
A Capsule is a slice of the Atlas, already traversed. Scoped, expiring and revocable.
Continue reading
Where the Atlas connects.
Give every tool the project context it should already have.
Start with one decision. The graph grows from there.