trustgraph/tests
cybermaggedon ddd4bd7790
Deliver explainability triples inline in retrieval response stream (#763)
Provenance triples are now included directly in explain messages from
GraphRAG, DocumentRAG, and Agent services, eliminating the need for
follow-up knowledge graph queries to retrieve explainability details.

Each explain message in the response stream now carries:
- explain_id: root URI for this provenance step (unchanged)
- explain_graph: named graph where triples are stored (unchanged)
- explain_triples: the actual provenance triples for this step (new)

Changes across the stack:
- Schema: added explain_triples field to GraphRagResponse,
  DocumentRagResponse, and AgentResponse
- Services: all explain message call sites pass triples through
  (graph_rag, document_rag, agent react, agent orchestrator)
- Translators: encode explain_triples via TripleTranslator for
  gateway wire format
- Python SDK: ProvenanceEvent now includes parsed ExplainEntity
  and raw triples; expanded event_type detection
- CLI: invoke_graph_rag, invoke_agent, invoke_document_rag use
  inline entity when available, fall back to graph query
- Tech specs updated

Additional explainability test
2026-04-07 12:19:05 +01:00
..
contract Pub/sub abstraction: decouple from Pulsar (#751) 2026-04-01 20:16:53 +01:00
integration Split Analysis into Analysis+ToolUse and Observation, add message_id (#747) 2026-03-31 17:51:22 +01:00
unit Deliver explainability triples inline in retrieval response stream (#763) 2026-04-07 12:19:05 +01:00
utils Streaming rag responses (#568) 2025-11-26 19:47:39 +00:00
__init__.py Test suite executed from CI pipeline (#433) 2025-07-14 14:57:44 +01:00
conftest.py Fix test async warnings (#601) 2026-01-06 22:09:34 +00:00
pytest.ini Entity-centric graph (#633) 2026-02-16 13:26:43 +00:00
requirements.txt Test suite executed from CI pipeline (#433) 2025-07-14 14:57:44 +01:00