TrustGraph’s Orchestrator

Most agent frameworks make you pick one workflow up front, the way a restaurant makes you order before you know how hungry you are. TrustGraph says its new orchestrator asks a language model to choose the workflow at run time, so one request can get a simple path while another gets a planner or a supervisor pattern. (x.com) That choice matters because “agent” is not one thing. A one-step lookup, a multi-step plan, and a team of sub-agents are three different ways to solve a problem, and TrustGraph’s own docs already describe the platform as supporting single-agent and multi-agent systems rather than one fixed style. (docs.trustgraph.ai) TrustGraph sits in a part of the market that is trying to turn language models from answer engines into work engines. Its docs describe the product as an open-source agent intelligence platform that combines knowledge graphs with vector embeddings so agents can use connected facts instead of isolated text chunks. (docs.trustgraph.ai) A knowledge graph is a map of facts and relationships. Instead of storing “Acme bought Beta” as a loose sentence in a pile of documents, the system stores Acme, Beta, and the acquisition link as connected pieces that software can query directly. (docs.trustgraph.ai) The hard part is not only finding facts. The hard part is showing where each fact came from after an agent has searched documents, called tools, and stitched together an answer across several steps. TrustGraph has been pushing that “show your work” angle for months in its explainability docs. (docs.trustgraph.ai) Those docs split the trail into three layers: the core knowledge graph, a source graph for extraction provenance, and a retrieval graph for query-time reasoning traces. In plain English, that means one place stores the facts, one place stores where the facts came from, and one place stores how the system used them in a specific run. (docs.trustgraph.ai) The new orchestrator adds another layer to that story by attaching Resource Description Framework provenance to orchestration runs. Resource Description Framework is the World Wide Web standard for storing facts as subject-predicate-object triples, and TrustGraph’s own guides explain that it can also attach metadata to facts, like who asserted them, when, and with what confidence. (x.com) (trustgraph.ai) That is the difference between “the agent answered” and “the agent answered after choosing a supervisor pattern, then calling these tools, then using these sources.” If that record is complete, a team can inspect a bad run the way an engineer inspects a flight recorder instead of guessing what happened from the final sentence alone. (docs.trustgraph.ai) (x.com) TrustGraph also says the release ships with more than 96 tests aimed at making orchestration decisions auditable and reproducible. That is a pointed claim in a field where many agent demos look good once and then behave differently when the prompt, tool latency, or model version shifts. (x.com) The bigger bet is that orchestration itself should be treated like data, not magic. TrustGraph’s GitHub repository already includes dedicated test strategy files, test cases, and a large test directory, and this release extends that engineering posture to the question of why one agent pattern was chosen over another. (github.com)