Every organization building on shared meaning today inherits a quiet dependency: the knowledge structures beneath its data belong to someone else. Data can be exported. Ontologies cannot. They are shipped as borrowed catalogs inside commercial platforms, seed schemas a customer can use, extend, and depend on, but never take with them. When the contract ends, the data comes out in tables. The knowledge stays behind.
This was the original market failure. A new one is now being layered on top of it.
In May 2026, Anthropic, Blackstone, Hellman & Friedman, and Goldman Sachs announced a $1.5 billion joint venture to deliver enterprise AI transformation services. OpenAI matched it the same week with TPG and Bain Capital. Palantir Technologies validated the pattern at over $325 billion in market capitalization. The model provider, the engineering capacity, and the deployment relationship now sit inside one external entity. The pitch undercuts the strategy houses on slides and the systems integrators on code. The financial sponsors supply the capital and the first clients from their portfolio companies.
The trade press calls it consulting rebuilt from the model up. The press releases call it additional operating capability for the ecosystem. Both readings miss the structural shift. Vertical integration of model provider with implementer with deployment relationship compresses what were previously four dimensions of governance sovereignty (semantic, enforcement, access, container) into one counterparty. We name a fifth that the joint-venture pattern makes unavoidable: provenance independence. Without it, the other four can be reasserted on paper but not reconstructed in evidence.
This is the procurement event most CDOs will not recognize until eighteen months in. The transformation contract is not what it appears to be. It is a transfer of the operational graph at enterprise scale, executed across private equity portfolios at speed.
Speed has a price. The price is sovereignty.
The cold-start tax was always real. Every new knowledge-graph deployment paid it, one customer at a time. That tax is steepest in the domains where getting meaning wrong costs the most: in healthcare and life sciences, where it is measured in patients; in energy and process industries, where it is measured in safety; in manufacturing, claims, and regulatory, where it compounds into exposure that no remediation budget can absorb. Independent reviews put the failure rate of knowledge-graph projects above 70%, with enterprise-scale implementations reaching $10 to $20 million and three years before self-sufficiency.
The cold start is the lever the rebundled providers now pull. An organization that cannot start its own ontology accepts whatever ontology arrives bundled. The ontology that arrives bundled is owned by the counterparty. The two market failures interlock: the cold start created the demand for borrowed meaning; the rebundling captures it.
We believe both failures are market failures, not technical ones. Ontology is where reusable domain meaning lives: the concepts, the relationships, the decisions about what counts as the same thing. Data is what an ontology lets you do. Losing the ontology is losing the work. Renting the ontology under a procurement contract that compresses four going on five sovereignty dimensions is losing the work twice.
We are starting in healthcare and life sciences because the cost there is measured in patients. The architecture transfers.
For four decades, enterprise software taught its users that the cost of automation is the user. Oracle, SAP, PeopleSoft, SAS, and the platforms that followed shipped on the assumption that the database was the artifact and the human at the keyboard was a shape that would have to bend to fit. Users learned the screens. They translated their mental model into the system's vocabulary. They reconstructed by hand what the system would not connect, and they did it every day, in every shift, in every audit, in every regulatory inspection. We have a name for this: digital archaeology. It is the toll the operator pays so the database can keep its assumptions.
Knowledge graphs are the first chance enterprise software has had to repay that debt. An ontology that begins with the operator's mental model, what a clinical research coordinator carries in their head when they walk into a site, what a process engineer carries when they read a batch record, closes the gap that no UX layer alone has ever closed. This is why TOP starts with OOUX, the Object-Oriented UX methodology. The objects in our reference graphs are the objects the operator already names, not the objects a standards body found convenient.
We believe AI's purpose is to be a human exoskeleton, not a human replacement. A pulley system for cognition. The thing that lets a clinical scientist who is exhausted from chasing eight signed delegation logs find the ninth in a quarter-second instead of a quarter-day. The thing that tells an auditor the chain is intact before they have to walk it. The thing that lets a process engineer compare a deviation against three prior matching deviations without standing up an entire data warehouse to do it. AI without grounding hallucinates. Grounding is what turns a pattern-matcher into an exoskeleton. The reference graph is the grounding.
For the practitioners who make this work, the ontologists, the information architects, the data engineers who have spent careers arguing for their seat at the table, TOP changes the day-one job. The first conversation in a knowledge-graph project is no longer a defense of the discipline. The reference graph already exists. The cross-walks already work. The operator-grade meaning is already there. The practitioner walks in adding value to an institutional asset, not justifying the existence of one. That value compounds with every subsequent contribution, attributed and traceable. Their customers stop being researchers of the past and become architects of the future.
This is what we mean by sovereign meaning. Not just that an organization owns its ontology. That the humans inside the organization, the operators and the practitioners both, get back the cognitive load that decades of mismatched systems have been silently extracting.
We have come to value:
The items on the right have value. The items on the left are what we are building.
The founding reference asset is an object-oriented map of clinical research, built using OOUX, the Object-Oriented UX methodology. It names the entities, relationships, and attributes that clinical-research work actually turns on (sponsor, study, site, participant, visit, investigational product, oversight body, event), in a form that can be rendered as a knowledge graph, extended by the community, and consumed by any platform.
This is the first reference graph. It exists so that no one starting work in this domain has to begin from a vendor's seed. It is our proof that we ship, not just argue. The next reference graphs already in the queue: in healthcare and life sciences, CMC, drug discovery, regulatory, commercial, claims, and healthcare delivery; in energy and process industries, the analogues to ISO 15926 and CFIHOS; in manufacturing, batch processing and supply chain. Each ships under its own working group with its own domain-native vocabulary, importing the same TOP commons.
We are building toward a knowledge graph of knowledge graphs, a federation where reference graphs from different domains remain their own artifacts, governed by their own communities, but can be discovered, cross-walked, and queried through a shared interface.
The proposed substrate is NGSI-LD, an open standard for context-aware, linked-data exchange. It is the candidate because it treats entities as first-class, speaks JSON-LD natively, and federates without requiring a central authority. We will validate it by using it.
v0.1 was deliberately unsigned. The document had to come first. v0.2 stands open for endorsement.
What we ship next, the second reference graph, the governance charter, the contributor process, will be shaped by the people who show up to this draft and mark it up. If you believe knowledge is the work and data is only what the work enables, read this and argue with it. Where we are wrong, say so. Where we are vague, push.
We are not asking for followers. We are asking for the first edits.