title
A short, retrieval-shaped statement of what you learned, phrased as an answer. This is what semantic search matches against.
The memory node is the basic unit of storage. A short, retrieval-shaped title is the anchor; the body carries the why, the trap and the rationale that gets handed back to the agent on a strong hit.
Writing good titles is the most important thing you can do. The title is the retrieval anchor — the specific, complete sentence someone would be looking for when they need this memory.
A short, retrieval-shaped statement of what you learned, phrased as an answer. This is what semantic search matches against.
The full context: the why, the trap, the workaround, the decision rationale. Injected into the agent's context on a STRONG hit.
One or more tags, like spring-boot or gotcha. Keywords create the edges that link a note to related ones.
Who or which agent wrote it (defaults to user@host), and an optional expiry after which the note is hidden and cleaned up.
What distinguishes TeamGraph from a plain vector search is the verify step. A low-confidence cosine hit does not become a STRONG response — it refuses to hallucinate a match.
Both semantic and lexical signals pass the gate. High confidence. Returns title and body — the agent can quote it.
Semantic passes but lexical is low. Returns title only; the body is null on purpose. Treat it as a hint, not a fact.
No candidate passes the gate. Returns a short fallback list of close neighbors so the caller doesn't have to widen the search.
TeamGraph does not store memories as isolated items — it connects them into a graph. Keyword and semantic edges are walked in both directions when you explore, regardless of which note was inserted first.
When a stored fix turns out wrong, the old note is superseded — moved out of results but kept in the database, with a traversable edge to its replacement. That is safer than deleting knowledge that changed.
ACTIVE and STALE notes are returned by queries (with their state reported); SUPERSEDED and RETIRED notes are left out but kept for audit and later restore.
Every note is private, team or shared. Private notes never leave your device — excluded from sync by construction, not policy.
A profile is a fully isolated memory space — its own database, daemon and config. Keep personal, work and per-project memory apart, and merge or export when you want to.
Good titles in, confident answers out — and a MISS instead of a guess when there's nothing good to say.