Neotoma

Inspector, Relationships & graph

Relationships are the typed edges that turn a flat list of entities into a navigable graph. Inspector exposes them as a flat list (good for filtering and audit) and as an interactive graph explorer (good for understanding context around a single entity).

Relationship list

The list at /relationships shows every typed edge, PART_OF, REFERS_TO, EMBEDS, SUPERSEDES, and any custom types, with source and target entity, the agent that created the edge, and the relationship's trust tier (it inherits the writer's). Filters: by relationship type, by source or target entity_type, and by agent.

inspector.neotoma.io/relationships?type=PART_OF
Relationships
6,907 edges across 12 types
PART_OF (4,210)REFERS_TO (1,884)EMBEDS (612)
SourceTypeTargetAgentCreated
msg · turn 4 (user)PART_OFconversation · Q2 reviewclaude-code12:30
msg · turn 4 (user)REFERS_TOtransaction · Vercelclaude-code12:30
receipt · vercel-2026-04EMBEDSfile_asset · vercel-2026-04.pdfclaude-code11:08
task · follow up SarahREFERS_TOcontact · Sarah Parkcursor-agent10:55
Typed edges with source, target, agent, and tier. Each edge is one row, immutable like observations.

Graph explorer

The Graph Explorer (/graph) renders a 1- or 2-hop neighborhood around a chosen entity, using @xyflow/react for layout. Nodes are coloured by entity_type; edges by relationship type. Useful examples: confirming that a refund linked to the right charge, that a calendar event linked to the correct attendees, or that an embedded file linked back to the right container row.

inspector.neotoma.io/graph?center=ent_4ad…&hops=2
Graph Explorer
Center: Subscription · Vercel · 2 hops · 14 nodes
PART_OFREFERS_TOEMBEDS
transactionreceiptagent_messagecontact · Verceltaskfile_assetemail_messagereminder
Drag to pan · scroll to zoom14 nodes · 19 edges
Force-directed neighborhood around a single entity. Click a node to recentre; right-click an edge to inspect the underlying relationship row.

Edge inspection

Right-clicking an edge opens its underlying relationship row: type, source, target, creator agent, trust tier, and any relationship-level metadata. Like observations, relationships are immutable; "removing" an edge is modeled with a separate SUPERSEDES link rather than a destructive delete.

Common workflows

  • Audit a turn, center the graph on an agent_message to see every entity it created or referenced, with PART_OF and REFERS_TO edges.
  • Find orphans, filter relationships by source or target type and look for entities with zero incoming edges to a conversation.
  • Trace a file, center on a file_asset and walk EMBEDS edges back to every container row that referenced it.

For the underlying API and edge semantics, see REST API.