Decisions
Why a choice was made: the trade-offs, the constraints and the alternatives you rejected. Cited and revisable.
01 / 06Knowledge Stream
Knowledge Stream keeps the project knowledge that usually gets lost: decisions, lessons, preferences, guardrails, docs, tasks and sessions. It stays current without the noise, and the people, tools and agents in your workspace read from the same feed.
Use Postgres row-level security for multi-tenant isolation.
Cited in auth.ts · session.md
Never run migrations on prod without a snapshot first.
Block direct writes to audit_log. Append only, through the service.
Pair session with Claude: refactored the billing webhook handler.
P95 latency drops 22% when context fetches of more than 3 items are batched.
README.md indexed. 3 new code references found.
Prefer pnpm over npm in this project. The lockfile is canonical.
01What gets captured
Most of what your project learns never reaches your AI. The Stream keeps the durable parts, the things future you, your teammates and your agents need, and curates them. Important items surface on their own, bursts of activity collapse into one digest, and Helpful or Dismiss on any item tunes what shows next. Everything else stays one tab away under All activity.
Why a choice was made: the trade-offs, the constraints and the alternatives you rejected. Cited and revisable.
What should not happen again. Hard-won corrections become guardrails the next session sees first.
How you and your team work. pnpm over npm, tabs over spaces. Small, durable and personal.
What agents should avoid: append-only tables, no direct prod migrations, no push without tests.
Indexed READMEs, runbooks, threat models, GitHub issues and PRs. Source-backed and traceable.
What you actually built today: turns, edits and references, linked back into the Atlas.
02From activity to reusable judgment
Row-level security for tenant isolation.
Snapshot before every prod migration.
The audit log is append-only, through the service.
GroundedEvery item is source-backed, scoped and reusable.
03Readable by agents
Through MCP, ContextStream Code or the API, every reusable fact carries its source, its scope and the decision graph it belongs to.
What should I know before editing auth/session.ts?
Row-level security replaces app-layer tenant checks.
Don’t hand-roll session expiry. Use the helper.
Never log raw session tokens, in dev or prod.
auth/README.md · auth/threat-model.md
04Team review and scope
Every Stream item is tagged with its scope. Personal preferences stay personal. Client work stays inside client boundaries. Agents only see what they should.
Your preferences, your shortcuts, your half-formed thoughts. Yours alone, even in a team workspace.
Decisions and lessons scoped to one codebase. Available to anyone with access, and to agents acting on it.
Knowledge across projects: preferred libraries, on-call runbooks, escalation lessons.
Redacted views for clients or contractors. The boundaries are enforced, not just documented.
An explicit subset: what an agent can read, what it must avoid and what it should cite back.
Some items expire. Sprint-scoped decisions leave the active scope when the sprint ends.
Continue reading
The Stream is what’s new. The Atlas is what’s connected. See how Stream items become a graph you can query.
Read moreBundle a slice of the Stream for one teammate, client or agent. Scoped, expiring and revocable.
Read moreConnect GitHub, Slack, Notion and Linear (beta), and project activity flows into the Stream.
Read moreFive minutes to your first reusable Stream item. No credit card to start.