Concepts

Records and declared links

A memory record carries useful context such as a decision, constraint, preference, or handoff. A declared relationship explains how two records belong together. The relationship is part of the memory model; a visual proximity on a graph is not a new relationship.

• Records should have a clear kind and a bounded, useful summary.
• Relationships should identify their source, target, and meaning.
• Sensitive records and links require server-owned visibility policy.
• A browser filter or graph position never grants access.

Organizations, projects, and domains

An organization owns one or more projects. A project is the workspace an agent connects to: every MCP sign-in resolves to exactly one organization and project, and that project's graph is the only one the agent and the console can read. OAuth scopes such as memory:read are permissions, not separate stores of data.

A domain is a short category label on every memory node, such as product or infrastructure, taken from the project's own vocabulary. Kinds (for example decision or fact) and relationship types are vocabulary too. Agents can list or add vocabulary with the vocab tool and can filter recall and search by domain. A small, stable set of domains keeps those filters and the console's graph regions predictable.

Export or delete memory

Today you export and delete memory through your connected agent; the console is read-only.

• Archive a node: ask your agent to forget it. The forget tool archives by default.
• Delete a node permanently: ask your agent to forget it with hard deletion. This cannot be undone.
• Export: ask your agent to run the export tool. It returns the project's graph as JSON with secrets redacted, up to 256 KiB per call and within your plan's daily export limit.

One authorized dataset, several views

The console presents the same bounded authorized memory through a readable table, a two-dimensional relationship view, and an optional three-dimensional exploration view. The table remains the dependable fallback; 3D is an exploration aid, not a prerequisite for reading memory.

Authorized data versus local layout

The customer console reads bounded stats, node metadata, and declared relationships only after a durable OAuth session resolves the active token-derived workspace. The browser receives no bearer token. Dragging, pinning, filtering, camera position, and force layout remain local view state and never create or change GraphMem relationships.