June 16, 2026 · 8 min read · Sallyann Della Casa

Everyone Thinks a Context Graph Is About Your Data. It Is About Your Judgement.

The wall isn't missing data. It's missing decision traces. Your files hold your rules. Your people hold your judgement. And nobody ever wrote the judgement down.

A librarian holding a glowing thread that connects a vast dark library of data shelves into a constellation-like graph.

Key Takeaways

  • A context graph is a structured, queryable record of how decisions actually get made in your organisation: the exceptions, approvals, precedents, and reasoning that connect your data to action.
  • Most leaders think building a context graph means connecting AI to their files, wikis, CRMs, and drives. That is plumbing. Plumbing is the easy part.
  • The hard part is that the most valuable context in your organisation was never written down. It lives in the heads of your top 20 percent: the people who know when to break the rule, which policy actually applies, and why the exception was granted last quarter.
  • MIT research found 95 percent of enterprise GenAI pilots fail to deliver ROI. The pattern is consistent: companies gave AI access to their data and none of their judgement.
  • Foundation Capital calls context graphs AI's trillion-dollar opportunity because decision traces are the one asset that compounds. Models commoditise. Your organisation's accumulated judgement does not.
  • You cannot buy a context graph off the shelf. You have to capture it from the humans who hold it, while they are still in the building.

What Is a Context Graph?

A context graph is a structured, queryable record of decision traces: the exceptions, approvals, precedents, and reasoning that explain not just what happened in your organisation, but why it was allowed to happen.

Your data warehouse knows the customer got a 20 percent discount. A context graph knows a VP approved it because of three service incidents, under policy version 3.2, based on a similar exception from last quarter.

One is a fact. The other is judgement with a paper trail.

Foundation Capital, the venture firm that put this term on every CIO's desk, calls context graphs AI's trillion-dollar opportunity. Their line stopped me cold: "The wall isn't missing data. It's missing decision traces."

Read that again. The wall is not missing data.

Because here is what almost everyone gets wrong.

Why Everyone Gets Context Graphs Wrong

Ask ten executives what a context graph is and nine will tell you some version of: "It's connecting our AI to all our data. Our files, our Slack, our CRM, our drives. Give the agent access to everything and it will have context."

No. That is not context. That is access.

Access is a plumbing problem, and plumbing problems get solved. Every vendor on earth is racing to pipe your SharePoint into a model right now.

Context is a different animal entirely. Context is knowing that the official ARR definition exists AND knowing that finance quietly uses a different one for board reporting. Context is knowing the discount cap is 10 percent AND knowing exactly which three situations justify blowing past it. Context is knowing what the policy says AND knowing that Priya in legal is the only person who knows how it actually gets applied when a sovereign wealth fund is on the other side of the table.

Your files hold your rules. Your people hold your judgement.

And here is the uncomfortable truth: nobody ever wrote the judgement down.

Picture This: The Day Your Best Operator Leaves

You are a CEO. Your head of revenue operations, 22 years of experience, resigns on a Tuesday.

Wednesday morning, what walked out the door? Not your data. Every contract, every email, every dashboard is exactly where it was.

What walked out was the knowing. Which customers get the exception. Which "final" deadline is actually final. Which policy conflict gets resolved in favour of the customer and which gets resolved in favour of the auditors. The thousand tiny judgement calls that made the whole machine run so smoothly you never noticed the machine.

Now you hire an AI agent to do her job. You give it access to EVERYTHING. Every file, every system, every thread.

And it fails. Politely, confidently, expensively.

Because you gave it the library and not the librarian.

This is exactly what MIT's research on the GenAI divide found: 95 percent of enterprise GenAI pilots fail to deliver measurable ROI. Everyone reads that stat and blames the models. Wrong lens. Run it through Pareto instead. Roughly 20 percent of your people carry 80 percent of your organisation's judgement. The pilots failed because companies connected AI to 100 percent of their data and 0 percent of that 20 percent.

The Glue People Are the Graph

Look at where your organisation has quietly hired humans to sit BETWEEN systems. RevOps. DevOps. Security Ops. Deal desks. Programme management offices.

Why do those roles exist? Because no system on earth records cross-functional reasoning. So you hired people to be the reasoning. One founder in the Foundation Capital orbit said it perfectly: new engineers spend months learning tribal knowledge, and nobody documented it.

Those glue people ARE your context graph. They are just running on biology instead of infrastructure, and biology retires, resigns, and burns out.

So the real question for every board this year is not "which AI vendor do we pick?" It is this: how do we get the judgement out of our best people's heads and into a form our systems can actually use, before those people leave?

That is the trillion-dollar question hiding inside the trillion-dollar opportunity.

Stop Reading. Do This Now.

Take out a pen. I mean it.

Write down the five decisions your organisation made this quarter that required someone to override, bend, or reinterpret an official policy.

Now answer honestly: is the reasoning behind ANY of those five decisions recorded anywhere a system could find it? Not the outcome. The reasoning.

If the answer is no, you do not have a context graph. You have a context leak. Every week, judgement is being exercised in Slack threads, hallway conversations, and one VP's excellent instincts, and none of it is being captured as an asset.

Your competitors' models will be identical to yours within 18 months. Models commoditise. The only proprietary AI asset you will own is your accumulated, structured, queryable judgement. Decision traces compound. Start compounding.

How Do You Actually Build One? Start With the Humans.

Here is where I will tell you plainly what we do, because it is the reason I care about this topic.

At GLEAC, we built our entire company on a bet that is now becoming obvious: the humans AI can't replace are the ones with taste, judgement, and wisdom. Contrarians, outliers, deep operators. We have 500+ of them across 50+ domains in 90 countries, and we deploy them as flocks into organisations: advisory to C-suites and Boards, AI workflow design with your teams, breaking silos and fixing culture.

The Judgement Corpus is our working implementation of a human context graph: a structured, queryable map of who knows what, in which context, under which constraints, with which judgement. We time-capsule the expertise of deep operators through our 100-Day AI Accelerator, so their decision traces become infrastructure instead of folklore.

We do not operate as consultants. We operate as your extended team who leaves your people and organisation better than we found it. Think of us as your human edge, and the context graph as the place where that edge gets stored.

You can start the conversation at lovelyhumans.ai or read how we deploy advisory flocks into organisations.

Frequently Asked Questions

What is a context graph in AI?

A context graph is a structured, queryable record of an organisation's decision traces: the exceptions, approvals, precedents, and reasoning that connect data to action. It captures why decisions were allowed to happen, not just what happened. The term was popularised by Foundation Capital in late 2025 and has since been adopted across enterprise AI.

How is a context graph different from a knowledge graph?

A knowledge graph maps entities and relationships: this customer, that contract, this product. A context graph maps decisions and reasoning: this exception was approved by that VP under this policy because of that precedent. Knowledge graphs describe your world. Context graphs describe your judgement operating inside it.

Why do AI agents fail without a context graph?

Because agents face the same judgement calls humans navigate daily: conflicting policies, exceptions, unwritten precedents. With data access alone, an agent knows the rules but not how your organisation actually applies them. That gap is why MIT found 95 percent of enterprise GenAI pilots fail to deliver ROI.

What is a human context graph?

A human context graph is a structured, queryable map of who knows what, in which context, under which constraints, with which judgement. It turns isolated human expertise into AI-addressable knowledge. The Judgement Corpus is GLEAC's working implementation, built from the decision-making patterns of 500+ domain experts.

How does an organisation start building a context graph?

Start with the humans, not the software. Identify the 20 percent of your people who carry the organisation's judgement, audit the decisions where policy was bent or reinterpreted this quarter, and begin capturing the reasoning behind those decisions as structured records. GLEAC deploys flocks of domain experts to run exactly this process inside organisations, starting with the Top 20% Diagnostic.

Your Move

Your data is safe. Your judgement is leaking.

Go do the five-decisions exercise. Then come back and tell me what you found, because I will bet you dinner the reasoning lived in somebody's head and nowhere else.

If curious, tell me what is true.

Sallyann Della Casa, Founder and CEO, GLEAC / Lovely Humans