Package com.tnsai.intelligence.rag.graph
Adapters implement
GraphStoreProvider and register it
through ServiceLoader. The provider exposes query seeds
and outgoing neighbors through
GraphStore; it does not implement
traversal or ranking.
InMemoryGraphStoreProvider
is the bundled FILE-corpus adapter. It claims Roles that have FILE
knowledge sources, extracts entities and relations with chunk provenance,
and is a framework default so an explicit consumer adapter wins.
Neo4jGraphStoreProvider is
optional: it claims a Role only when tnsai.graph.neo4j.uri is set
and org.neo4j.driver is on the runtime classpath. The driver is
never a tnsai-core or required intelligence dependency.
When tnsai-tools is on the classpath,
KnowledgeToolsGraphStoreProvider
claims Roles that have no FILE sources (or whose fence names
knowledge-tools) and serves live KnowledgeTools triples.
That bag is not the FILE knowledge graph. Without the tools artifact the
provider leaves the Role unclaimed. When any other non-default provider
also claims the Role, bundled defaults are dropped.
Provider selection is annotation configuration, not request data: a Role
annotated @Search(strategy = GRAPH) with no registered provider,
or with more than one provider claiming it, fails at action dispatch through
GraphCapabilityException. That
error is raised before the @Search.onFailure guard, so no policy
can downgrade it to an empty result or a stale cache entry. Only failures a
provider raises while traversing are routed through onFailure.
- Since:
- 0.13.0
-
ClassDescriptionBinding-time FILE chunks available to the in-memory graph provider.One ingested FILE chunk.Complete source-configuration and lifecycle identity for one binding.Exact-owner lifecycle handle for one registered corpus.Builds graph nodes and edges from ingested FILE chunks.Signals that graph retrieval was requested but no unambiguous graph capability is available for the Role.Vendor-neutral graph data access contract used by graph retrieval.A directed graph edge.An outgoing edge paired with its destination node.A graph node that can become a retrieved document.A scored query seed.Service-provider contract for graph database and graph corpus adapters.Graph binding request.Zero-config in-process
GraphStorefor development and FILE ingest.Bundled FILE-corpus graph adapter.Built-in graph adapter for liveKnowledgeToolstriples.GraphStoreover a Neo4j property graph.Minimal Cypher execution seam.Optional Neo4jGraphStoreProvider.