Files

T

Andy Dixon 99a89ba847 feat: add the relationship graph with extraction, corrections and explorer

Phase 11. Entities are mind-scoped nodes with canonical matching,
aliases and deterministic kind guessing (hostnames and hyphenated ids
are systems, capitalised names people, file suffixes documents).
Relationships carry a relation from the shared vocabulary, confidence,
source, reinforcement count and the event that produced them; links tie
entities to memories, beliefs, events, goals and predictions.

The perceive and attend handlers upsert the entities a message or
observation mentions and record co-mention edges cited to the event, so
the graph grows only from what was actually seen. Operators can merge
("these are the same": edges and links move, the old name becomes an
alias, the old id still resolves), record that two entities are
different, correct kinds and add typed edges; every correction is an
operator action and a corrections row.

The explorer renders a bounded subgraph on a canvas with a small
force-directed layout in plain JavaScript, with kind filters, focus on
a neighbourhood and a side panel per entity. API, entity page, CLI and
docs/graph.md.

2026-06-29 19:28:55 +01:00

2.2 KiB

Raw Blame History

Relationship graph

Each mind keeps its own entity graph (entities, entity_relationships, entity_links), mind-scoped like everything else.

Entities

Kinds: person, system, project, document, concept, repository, organisation, place, other. Names are canonicalised (lower-cased, trimmed) for matching; aliases accumulate through merges. Every mention bumps mention_count and last_seen.

Extraction is deterministic and conservative: hostnames (atlas.local), hyphenated identifiers (server-09, web-api-prod), letter-digit names and capitalised words become entities; plain lower-case nouns do not. The perceive prompt may add entities with kinds when a model is configured. Operators can correct the kind and description of any entity.

Relationships

Edges carry a relation from the shared vocabulary (related_to, discussed_with, caused_by, supports, contradicts, depends_on, belongs_to, observed_during, derived_from, similar_to, follows), a confidence, a source, a count of reinforcements and the event that produced them. Co-mention in one message yields discussed_with (speaker → entity) and related_to (entity ↔ entity) at low confidence; repeats raise the count. Operators can add typed edges with higher confidence.

entity_links record which memories, beliefs, events, goals and predictions involve an entity, so the entity page answers "where has this come up".

Corrections

These are the same: Merge re-points edges and links to the survivor, adds the loser's name as an alias, and keeps the loser row with merged_into so old references still resolve. An operator_action event and an entities_same correction are recorded.
These are different: an entities_different correction and event are recorded; it documents the operator's judgement and is visible to later extraction.

Explorer

/minds/{mind}/graph renders a bounded subgraph (node cap, kind filter, optional focus entity with its neighbourhood) on a canvas with a small force-directed layout written in plain JavaScript. Clicking a node loads its panel (edges, links, corrections); double-clicking focuses on it. The API endpoint GET /api/v1/minds/{mind}/graph returns the same nodes and edges as JSON.

2.2 KiB Raw Blame History