Entities

Entities are the nodes of the reasoning graph. They are the things Virgo reasons over, and the points that retrievers traverse to assemble an answer. New to the term? Start with the plain-language definition of the enterprise reasoning graph.

The graph links entities such as people, projects, decisions, constraints, artifacts, discussions, code changes, documents, meetings, and the learnings your agents produce.

Where entities come from

Entities are created during ingestion. As data arrives from a data source, Virgo pulls the useful entities out of it and connects them to the work they came from.

Entities that refer to the same thing collapse into one canonical node, so the same person or pull request is a single entity no matter how many sources mention it.

Entities and relationships

An entity on its own is just a node. Its value comes from how it connects: a decision links to the constraint that shaped it, the discussion where it was debated, and the code that implemented it. Those connections are relationships, and they are what let Virgo reason across work instead of returning a flat list.

Declaring entities for your source

When you write a connector, you declare which entities each record produces. See Data source entities for how to model them, and Entity relationships for how to connect them.

Related

• Chunks: how unstructured content attaches to entities.
• Retrievers: how entities are read back.