The Context Gap
Summary
In December 2025, Foundation Capital's essay "AI's Trillion-Dollar Opportunity: Context Graphs" proposed "context graphs" to address enterprise AI agents' failure due to missing "decision traces." This article contends that "context graphs" are a rebranding of established knowledge management principles, specifically process and procedural knowledge, which Western companies systematically eroded through decades of outsourcing. The author agrees with Foundation Capital's diagnosis of the "context gap"—the missing reasoning connecting inputs to outputs—but asserts that existing information science methods like formal ontologies, PROV-O, SKOS, and OWL already provide the toolkit. The essay details how the US shifted from an "engineering state" to a "lawyerly society," fostering Knowledge Process Outsourcing (KPO) and the loss of apprenticeship systems, contrasting this with China's accumulation of process knowledge in Shenzhen. This historical knowledge deficit now impedes effective AI deployment, contributing to a "gen AI paradox" where AI use lacks significant bottom-line impact.
Key takeaway
For Directors of AI/ML and AI Architects grappling with agentic AI failures, recognize that "context graphs" are a symptom, not a cure, for a deeper knowledge management deficit. Your focus should shift from acquiring new software to rebuilding foundational process knowledge infrastructure. Invest in knowledge engineers and formal semantic systems, and foster a culture that values documentation and apprenticeship, ensuring your AI systems are grounded in actual operational understanding, not just abstract data. This will mitigate the "gen AI paradox" and build durable competitive advantage.
Key insights
"Context graphs" are a market response to the self-inflicted wound of lost process knowledge due to decades of outsourcing.
Principles
- Outsourcing systematically erodes process knowledge and institutional memory.
- Process knowledge thrives in communities of practice and apprenticeship systems.
- Documentation and knowledge capture are integral to craft, not just compliance.
Method
Systematically capture, organize, and encode process knowledge using formal ontologies, taxonomies, and controlled vocabularies like PROV-O, SKOS, and OWL.
In practice
- Audit existing procedural knowledge against operational needs to identify gaps.
- Reinvest in knowledge engineers, information architects, and ontologists.
- Design AI systems for native knowledge capture, including prompt libraries.
Topics
- Knowledge Management
- Process Knowledge
- Context Graphs
- Outsourcing
- AI Agents
- Semantic Engineering
- Ontologies
Best for: AI Architect, Director of AI/ML, Consultant
Related on AIssential
Editorial summary, takeaway, and curation by AIssential. Original article published by Intentional Arrangement.