What is a context graph?
A context graph connects the information needed to understand a situation and decide what to do. For a customer account, that could include its contract, open support issues, recent activity and earlier decisions. The connections help people and AI see the full picture.
Illustrative example: A customer's contract has a renewal date. A support case concerns that account. An unresolved rollout issue may explain why the renewal deserves attention. Connecting those three records helps a team investigate. It does not prove the customer will leave.
What does the graph connect?
A graph connects things through named relationships. In this example, the contract belongs to the account and the support case concerns the same account. The links matter because the answer depends on seeing those records together. A person should also be able to check where each record came from, when it was current and whether they are allowed to see it.
The same customer may have different identifiers in the CRM and support system. Test that they refer to one account before joining them. If the match is disputed, keep the uncertainty visible and ask an owner to resolve it. Do not let a guessed match drive a customer action.
A useful record also separates what was known when a decision was made from what arrived later. A support case opened after a renewal decision may help evaluate that decision, but it should not appear as if the team knew about it beforehand.
How does a company build one?
Start with one question and the few records needed to answer it. Agree what each field means and who maintains it. “Active account” might mean the contract is signed in one system and the customer is using the service in another. Preserve both meanings until the team decides which one the task requires.
Nodes Connector can connect permitted systems and help draft mappings from their documentation. The mappings, identity links and required actions still need tests in the customer's environment. A renamed field or revoked permission should stop affected work and reach an owner. The integration guide shows how to test those cases.
When is a graph more useful than simple search?
A current policy paragraph may need only permission-aware document search. A question that combines a contract, support history and earlier decisions needs reliable links across records. Search and a graph can work together: retrieval finds the relevant text, and the links show how it relates to this account and decision. A graph label does not guarantee a good answer; source quality, retrieval, model choice and task design still matter.
For a talent example, an approved ATS candidate record, HRIS performance record and relevant CRM activity may be connected when the identity match and permission are valid. That can reveal historical associations worth testing. It cannot by itself show why a person performed well. The applied talent guide shows a more detailed design.
How is it different from a knowledge graph?
The terms overlap. A knowledge graph connects things and facts. A context graph often emphasizes the circumstances around a decision: what was known, which rule applied, who judged the evidence and what happened afterward. A knowledge graph can store that information too. Judge either design by the records, links, dates, permissions and correction path it actually preserves. The knowledge-graph guide explains the distinction with a supplier example.
How can a reviewer check the answer?
Ask the system to show the original records and the links used to reach its conclusion. Check a clean case and a disputed match. Correct one source and see whether the next answer changes while the earlier decision remains reconstructable. A source path makes the recommendation inspectable; it does not prove the reasoning was sound.
A Decision Trace connects the evidence with a recommendation, human judgment, authorized action and later result. Keep the later result separate from the information available before acting. A favorable outcome alone does not prove the earlier choice caused it or that the same response should be reused.
Nodes Engine creates the company's context graph, uses it to investigate questions, compares options and carries out approved work within current permissions. Nodes AI FDE helps configure and test the solution. The company retains its context graph, Decision Traces and outcome history when models change; any replacement still needs evaluation.
The public production reference is one Fortune 500 insurance carrier. A separate Decision Traces study analyzed a historical cohort of 10,765 agents. The live hiring application has scored 900,000+ candidates since January 2025. Those hiring facts do not measure every graph use or the carrier's licensing and educational workflows.
For a practical start, choose one owned question and test a correct answer, a disputed link and a restricted record before adding actions.
Saad Bin Shafiq is the founder of Nodes, serving data-sensitive enterprises.