Nodes & edges union
Existence is a grow-only set. Two people recording the same insight independently end up with one node, not a conflict.
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.
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.
Existence is a grow-only set. Two people recording the same insight independently end up with one node, not a conflict.
Each note's state and scope resolve by a hybrid logical clock, so the most recent decision wins deterministically on every replica.
Edge weights merge by maximum, so a stronger observed relationship from any replica is the one that survives.
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.
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.
Retiring a note hides it everywhere but keeps the row, so the deletion propagates — and a later restore can bring it back.
Keep working with no connection. When you reconnect, your notes reconcile both ways against the shared graph.
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.
Mark any note private and it never leaves your device, no matter what the rest of the team is sharing.
Take the team's notes without pushing any of your own — one-way sync when that's what you want.
Halt all sync, inbound and outbound, with a single switch when you need to go dark.
Decide whether new notes start out team or private, so the safe default is the one you picked.
Bind to a shared graph, keep what's private private, and let a fix on one machine answer everywhere.