Inspect graph relationships and evidence

Click path

Open Знания and search for an entity by name.
Select a catalog entry or graph node to open its details.
Select a relationship and inspect the claim and exact source excerpt.
Use Развернуть or double-click a node for neighbors. Filter by relationship or date.
Distinguish verified entries from proposals. Предложения contains entries still awaiting review.
Use Спросить память for the selected memory; use Поиск знаний for accumulated blocks.

**Knowledge graph**
2026-10-15 · Actual interface in the built-in Demo mode.

Verify and recover

A claim must have a source, state and context. Demo changes disappear on reload. An empty graph does not mean empty memory: unlinked records can appear in knowledge search. Use Подключить IAM.Mind and your environment’s API/access details for a live connection; its token stays in window memory.

Understand the memory layers

Episodes, facts, procedures and preferences are different stored record types. Normal agent capture creates an episode; it does not automatically transform that record through every other type. Cross-session retrieval from Codex, Claude, Cursor and DSH searches text across permitted history and returns original records. It attaches relevant consolidated KG facts with their complete supporting source addresses. When a compatible text profile is configured, DG/CA3/CA1 helps rank a bounded candidate set while retaining each record’s provenance.

A similarity link helps explore related records but does not verify a claim. KG entities and assertions carry evidence: extraction results start as proposals, and verified status requires a separate review. Consolidation requires several reviewed independent sources; one note does not become a confirmed general fact.

Model extraction requires separate consent to model processing and a configured service. Permission to capture history does not enable it automatically. The server configures the text profile for ordinary agent requests. Neural scores assist retrieval and do not replace claim review. If that profile is unavailable, the response uses textual sources; a missing neural result does not mean empty memory.

What the agent receives

Use a normal work request with the project name. The agent receives original records and related corroborated facts together; no separate graph-tool request is needed for this enrichment. Each fact retains all independent source addresses. When the response budget shortens a preview, the agent can read the source continuation; an excerpt does not imply that the remaining content is absent.

Retrieval test reports do not replace the original recipe. State explicitly when your question concerns memory testing itself. An empty consolidated-fact list means no suitable corroboration was attached to the selected records, not that the full history contains no records or relationships.

When you forget a source

Explicitly forgetting a source removes that record and its dependent relationships from retrieval and graph views, including historical date filters. If a recommendation graph referenced the entity, its dependent recommendations are removed with the evidence. The immutable publication receipt remains in version history but no longer returns the removed recommendation. This does not retract answers already copied into another chat’s history.