THE SHARED TEAM GRAPH

From your memory to the team's.

On its own, an agent's memory is personal — what one agent learned. TeamGraph lets a whole team's agents share one memory: every fix, gotcha and decision, pooled and kept in sync, so a problem solved once on any machine is answered everywhere.

teamgraph view · exploration ONE SHARED GRAPH
An exploration in the TeamGraph viewer lighting up the notes related to one memory
Bind and go · syncs both ways · reconciles when you reconnect
CONFLICT-FREE MERGE

Apply changes in any order. Converge anyway.

Sync is a CRDT with strong eventual consistency. Apply the incoming change set in any order, or twice, and every replica arrives at the same graph — no central lock, no merge conflicts to resolve by hand.

Nodes & edges union

Existence is a grow-only set. Two people recording the same insight independently end up with one node, not a conflict.

grow-only set

State is last-writer-wins

Each note's state and scope resolve by a hybrid logical clock, so the most recent decision wins deterministically on every replica.

hybrid logical clock

Weights take the max

Edge weights merge by maximum, so a stronger observed relationship from any replica is the one that survives.

max-merge

Authors accumulate

Recorded independently by two people, a note ends with both authors and both sources after merge, so you can see who else has relied on it.

grow-only
The same insight is one note. Every note is identified by a BLAKE3 hash of its content — title, body and keywords — so the same thing written by two people deduplicates to a single node across the whole team.
SAFE BY DESIGN

Shared, without the sharp edges.

Vectors respect the model

Every vector carries the id of the embedding space that produced it, and TeamGraph only compares vectors within the same space — a local-model vector and a shared-model vector are never mixed.

Tombstones converge

Retiring a note hides it everywhere but keeps the row, so the deletion propagates — and a later restore can bring it back.

Offline-friendly

Keep working with no connection. When you reconnect, your notes reconcile both ways against the shared graph.

PRIVACY & OPT-OUT

Sharing is the default.
Reversible at every level.

Every note is private, team or shared. Private notes are excluded from sync by construction, not by policy — so opting out is a guarantee, not a setting you have to trust.

PER-NOTE

Mark it private

Mark any note private and it never leaves your device, no matter what the rest of the team is sharing.

PULL-ONLY

Take without giving

Take the team's notes without pushing any of your own — one-way sync when that's what you want.

PAUSE

One switch, both ways

Halt all sync, inbound and outbound, with a single switch when you need to go dark.

DEFAULT SCOPE

Choose the starting line

Decide whether new notes start out team or private, so the safe default is the one you picked.

Project statusThe content identity, CRDT merge and scopes above are the rules a pulled change set is applied under, working today for local merge. Binding to a remote shared graph and syncing over the wire is the active work toward 1.0.
SOLVED ONCE, ANSWERED EVERYWHERE

Pool what your team already knows.

Bind to a shared graph, keep what's private private, and let a fix on one machine answer everywhere.