# The KXCO Ontology The ontology is the shared, verifiable model of reality every KXCO capability stands on. It is the core of the company, not a side project. Canonical HTML: https://kxco.ai/ontology Last modified: 2026-09-14 --- Skip to content Infrastructure for the Human and AI Economy # You HAVE the data, but can you SEE it? The risk you never saw and the opportunity you never spotted are the same failure. What you own, who stands behind it and what moves when it does all live in the relationships between records , and neither a database nor a ledger keeps those. KXCO builds that missing layer: a working digital twin your people, your regulators and your machines all reason over. See it on public data → Bring us your question → "it's backed, trust us" → backing proven · holder identified · record kept · permission live Live graph · public data as at 11 Sep 2026 edge asml → tsmc predicate is the sole EUV supplier to magnitude 100% of EUV · ~$400m/machine group physical / compute supply basis primary · confidence high valid from 2026 source techtimes.com One relationship, as the engine stores it. Every edge carries its own source, basis, confidence and the date it was true, which is the difference between a knowledge base and a diagram. Open any of them yourself. 6 Seed names 393 Entities resolved 853 Relationships mapped 100% Public data Live · public data only We pointed this engine at the AI sector using nothing but public sources. It resolved six names into 393 entities and 853 relationships, 815 of them carrying a source you can open . The public map draws the 380 that currently sit on a live relationship; the rest are resolved and typed, waiting on a claim. Down to the nine chokepoints the whole sector rests on and the one company at the root of them. That is what public sources alone allow. On your own assets, from the inside, the engine does not infer, it proves. See it on public data → What is judgment here, and what is sourced Every claim in this graph carries a source. The weighting applied over those claims is Shayne Heffernan's : which entities sit upstream, which are single points of failure, which findings rank as critical, and how far each claim's evidence is trusted. Those are judgments, they are where most of the analytical value sits, and they are accredited rather than presented as facts . Where a reading of the graph is ours rather than a source's it is marked derived and carries no source URL, because inventing one would be the failure this map exists to prevent. Of 869 relationships, 815 carry a source you can open and 49 are marked derived . Why you need this ## Different seats. One missing layer. Everyone in a market is asking a version of the same question. What is this really, who stands behind it, what does it rest on, and what happens to me if that moves. Nobody is short of data. Everyone is short of the shape of it, so today that question gets answered by hand, out of documents that were never built to connect. Investors what am I actually exposed to Two holdings can look unrelated and depend on the same supplier, the same lender or the same jurisdiction. The exposure nobody can see is the one that reprices everything at the same time. Funds and asset managers look-through on demand Concentration, coverage, mandate fit and jurisdiction mix fall out of the model instead of out of a quarterly reconstruction. The same question, asked at any hour, returns the same answer. Public companies your own ecosystem is the blind spot The supplier behind your supplier. The customer who is also your competitor's largest customer. The single dependency that nobody wrote down because no one team could see both ends of it. Regulators and supervisors systemic risk is a relationship problem Risk does not concentrate inside one filing, it concentrates between them. A shared model shows where it actually gathers, with every claim carrying the source it came from and the date it was true. Banks and lenders who am I really lending to Follow the guarantees, the parent, the pledge and the pledge on the pledge. Collateral is only ever as good as the chain behind it, and that chain is a graph, not a document. Everyone else in the market auditors, exchanges, insurers, counterparties Anyone whose job is to establish that something is what it claims to be is doing graph work right now, with phone calls and PDFs. The work does not change. The evidence stops being manual. What data misses ## Not in the rows. In the relationships. Every fact below was already public. None of it was visible in any single filing, report or dashboard, because none of those hold the shape of the whole. We pointed the engine at the AI sector using public sources only. These are the things it found that nobody had a column for. 01 Six household names, one root. Follow the dependencies down and six of the largest companies in the world converge on a single firm in Veldhoven that makes the lithography machine every leading-edge AI chip is printed on. It sits behind a Taiwanese fab, behind an American chipmaker, behind the names everyone actually watches. No filing states this. The graph does. 02 Sixteen loops where the investor is also the customer. Capital goes out, revenue comes back, and each leg looks perfectly ordinary on its own line. Only the graph closes the circle and shows you how much of the sector's growth is buying its own supply. 03 Nine chokepoints wearing a diversified disguise. Read the rows and the sector looks broad and competitive. Traverse the relationships and the same handful of suppliers sits underneath all of it, which is a concentration no single balance sheet reports because no single balance sheet can see it. A dashboard answers the question you already knew to ask. A model answers the one you didn't. Open the engine and check all three → Across the organisation ## One model. The whole ecosystem. The value compounds when this stops being a project inside one department. Point one model at your customers, your people and everything you depend on, and the questions that used to need a working group and three weeks become a traversal. Your customers one customer, not one record per system Who introduced them, what they hold, who they pay, who pays them, what they are exposed to. Where your own book is concentrated becomes a property of the model rather than a study someone commissions. Your people authority, not an org chart Roles, delegation, approval limits and access sit inside the model. Who can commit the firm to what, on whose behalf, and what they touched. Key-person dependency becomes visible instead of anecdotal. Your ecosystem including the parts you do not own Suppliers, partners, distributors, lenders and their dependencies. The concentration you inherit from other people's suppliers is real exposure, and it is missing from every dashboard you currently own. Risk and opportunity are the same question, asked in two directions. The digital twin ## A twin, not a diagram. Engineers do not run tests on a picture of a jet engine. They run them on a model that behaves like the engine. The ontology is that, for a sector, an institution, a counterparty or a single instrument. Not a diagram of the subject. A working copy you can question, stress and watch respond. The same parts entities, not tables A person, a company, an agent, an asset, an obligation and an authority each exist once, defined once, and are referenced everywhere rather than rebuilt inside every system that needs them. The same wiring typed relationships Owns, controls, supplies, guarantees, is permitted by. Every connection carries its own type and direction, so the structure is something you can traverse instead of something you have to remember. The same rules constraints that bite What has to hold for a claim to stand is part of the model, not a note in a policy document. Break one and the twin tells you, which is how a contradiction surfaces before it becomes a loss. And the same clock. Every claim in the twin carries a source and the date it was true, so you can tell what holds now from what held last quarter and from what was never checked at all. A twin of a sector, built from public data. A twin of your own institution, built from the inside. Complexity, made legible ## Map the models no one else can. The dangerous instrument was never the complex one, it was the opaque one. Complexity is only composition: claims on claims on assets. An ontology keeps every relationship explicit, so you can hold the whole structure and still look straight through it, to what it truly rests on. A twin of a tokenised fund, decomposed · hover or tab to look through to the real asset underneath Every claim traces to something real and provable. Hover a node to follow the look-through. ### The look-through, described A tokenised fund decomposes into a Senior tranche, a Mezzanine tranche and an RWA sleeve. The Senior tranche rests on a Reserve (reserve, proven). The Mezzanine rests on a Loan pool (obligors identified). The RWA sleeve rests on Property (custodian and provenance) and a Bond (valuation sourced). Map look-through, all the way down Decompose any instrument into its full dependency graph, every claim, counterparty and piece of collateral, down to the reserve or real asset it rests on. Computable, not spreadsheet archaeology. Report a query, not a reconciliation Exposure, coverage, concentration, regulatory treatment and jurisdiction mix all fall out of traversing the graph, on demand, instead of a month of chasing the same numbers between teams. Understand reason over it, don't just store it Stress one node and watch the effect propagate. Does the waterfall hold; is every leg permitted; is every claim proven. Contradictions surface instead of hiding. Why now ## Six shifts, at once. None of this was true a few years ago. Together they broke the way the world keeps track of itself. 01 AI stopped advising and started acting. Agents now move money, sign documents and take decisions directly, a new kind of actor the world has no record type for. 02 Value became programmable. Money, assets and contracts are software now, a stablecoin, a central-bank currency, a tokenised building, each one a claim that has to be checkable. 03 Identity fragmented. A person, a company or an agent is a different, disconnected record in a hundred systems that never agree on who is who. 04 Regulation went real-time. What is permitted, by whom, and where is no longer paperwork after the fact, it is a live question asked on every transaction. 05 Trust stopped scaling. You can no longer meet, or vet, everyone you transact with, let alone every machine acting on their behalf. 06 And our records got better at facts than at meaning. Systems became excellent at recording that something happened, and no better at understanding what it was, or how it connects to everything else. A database stores rows. A blockchain stores events. Neither understands relationships , and relationships are where meaning lives. Why the machines need one ## All that intelligence. No ground truth. A language model is reasoning power with no anchor. Point it at a business and it will produce confident, well-written answers nobody can act on, because nothing in the system separates a checked fact from a plausible sentence. The ontology is what turns that reasoning into work. It is the difference between software that can talk about a business and software that can operate inside one . Grounded, not guessed every input carries a source An answer built on the ontology traces back to the claim, the source and the date it was true. Where the evidence runs out, the gap shows up as a gap instead of being written over with something that reads well. An agent needs more than a brain reasoning is not reach No agent can act on paragraphs. It acts on entities, relationships and permissions it can read and write. Without that layer it has judgment and no hands, and every action it takes is a guess about a world it cannot actually see. The alternative is not none a hundred private models Every team already carries its own idea of what a customer, an exposure or an obligation is. None of them are written down and no two answer the same question the same way. One shared model is not extra structure. It replaces the hundred you are already running on. Knowledge sovereignty ## Keep your edge. Maintain your sovereignty. A model is a commodity: someone else's weights, on someone else's hardware, on someone else's release schedule. That is a perfectly good arrangement for the reasoning. It is a terrible one for the thing being reasoned over. Your edge is what you know that nobody else does, and it stops being an edge the moment a third party holds it. KXCO delivers knowledge sovereignty. AI does not. Weights are not a record absorbed, not organised Train a model on your business and it has swallowed your knowledge rather than structured it. You cannot cite a weight, correct one fact inside it, or take a customer back out of it. Ask the same question after a version change and the answer can move, with nothing to point at and no way to tell whether you or the model was wrong. Whoever holds the interface holds the asset a vendor between you and your own business If the only way to ask what you own, who you owe and what you are exposed to is a supplier's model, that supplier sits in the middle of your own understanding. Their pricing, their retention policy, their availability, their roadmap. Keep the knowledge as data you hold and the model drops back to being a component you can replace. Evidence, not recall "the model said so" is not a filing No supervisor, auditor, board or counterparty accepts a confident summary. They accept a claim with a source and a date attached, and the ability to check it without trusting the party presenting it. That is what an ontology holds. It is not something weights can produce, however fluent they sound. Models will come and go. Your understanding of your own business has to outlive them. So the model stays outside the knowledge, and the knowledge stays sourced, dated, portable and readable by whichever model you choose to point at it. Swap the reasoning whenever something better arrives. You should never have to migrate the truth. The model ## Four primitives. One system. At the core of the ontology sit four roles, not four buzzwords: quantum, AI, blockchain and the regulator. Nothing becomes real until all four agree on it at once. That rule is shown by default below; hover or tab any node to trace how the pieces depend on one another. Each product is an edge between two primitives · hover or tab a node to trace it ■ Four-agreement rule: on Primitive Live / active relationship Where a token becomes real ### The ontology graph, described Trust (Quantum) secures Issuance. Judgment (AI) interprets Issuance. Record (Blockchain) remembers Issuance. Permission (Regulation) permits Issuance. Issuance is where a token becomes real, only when all four primitives agree at once. Verify is the edge between Judgment and Trust. Sign is the edge between Trust and Record, anchoring documents to the record. The wallet is the edge between Record and Trust. PQC Host and Bastion bind to Trust, made infrastructure. The stack ## Everything else is an application. KXCO is not a blockchain, a wallet or a signing tool, and it is not a model either. It is the layer those things run on. The ontology is the intelligence layer , the shared model everything above reasons over, and everything below makes provable. Between judgment and the world sits one governed step , which decides whether a proposal is allowed to become a real, recorded action. Applications What people and institutions actually use Surface AI Agents Autonomous users of everything below, a first-class actor, not a bystander Actors Authority Decides whether a proposal is allowed to become a recorded action: typed, precondition-gated, previewed, approved by name Governs The Ontology The shared model of reality, meaning, relationships, reasoning Intelligence Identity Who and what everything is, person, company, agent, asset Who Signatures Proof a claim was actually made, by the party who made it Proof Permissions What is allowed, by whom, and where, checked live Allowed Post-Quantum Cryptography Trust that survives the machines that will break today's signatures Unforgeable Blockchain The shared, tamper-evident record anyone can check Record Infrastructure The network and machines it all runs on Ground Humans, businesses, governments, machines and AI agents don't get five different views of the world. They reason over the same one. The issuance domain ## Every token is a typed claim. And a claim everyone can now check. Each kind carries the same four edges, issuer permissioned, holder identified, backing proven, lifecycle recorded, that used to be a promise in a PDF. Stablecoin a claim on a reserve reserve, proven, not asserted redemption right, on record issuer, permissioned attestation, live CBDC a sovereign liability central-bank issuer legal-tender status jurisdiction & policy controls provable for decades, not years RWA token a claim on a real asset underlying asset & legal wrapper named custodian provenance chain valuation source The axioms ## What is always true. The four-agreement rule. Nothing is real until trust, judgment, record and permission all hold at once. KXCO is the software layer, never the operator. The licensed institution holds the licence and the custody. KXCO holds neither. Trust is forward-only. Verification begins at go-live. Provenance is never backdated. Off-chain proof, on-chain anchor. The chain remembers. The proof is checked independently. The regulator is a primitive, not an obstacle. Permission is designed in, kept live, cited and current. Under scrutiny ## How it holds up under scrutiny. The questions that decide whether a model of reality is real infrastructure or just a diagram, answered plainly. Where it runs Inside your estate, not ours. KXCO builds the software and licensed institutions deploy and run it, under their own brand, licence and controls. The reasoning points at your own inference endpoint , so the weights stay in your estate too. The argument on this page would be hollow if the engine sat on somebody else’s hardware. What happens to your data It stays data you hold. The ontology is a model you own, sourced, dated and portable, not a corpus absorbed into somebody’s weights. KXCO takes custody of nothing. That is the whole point of keeping the model outside the knowledge: you can swap the reasoning and you should never have to migrate the truth. What you are actually buying Software and the work of building the model with you, not a subscription to somebody else’s answer. It can be co-branded, white-labelled or deployed under your own name, the same way the rest of the platform is. The public map on this page was built the same way yours would be, from sources you can open. Where to start With the question you cannot currently answer about your own business. Bring that, and whatever data you already hold, and the first pass is scoped around answering it rather than around installing something. On public sources the engine infers. On your own assets, from the inside, it proves. How the ontology is constructed It is a shared schema of the entities that matter economically, identity, authority, assets, events, proof and history, and the relationships between them. Each entity is defined once and referenced everywhere rather than rebuilt inside every system. Where a claim has to be permanent, its proof is signed and anchored to Armature L1, KXCO's post-quantum record, so anyone can check it later without asking us. How information becomes trusted Nothing is trusted because KXCO says so. Every claim is cryptographically signed and recorded, so any party can check it independently. The signatures are post-quantum, NIST FIPS 203 / 204 / 205, so those proofs still hold decades from now. An action being taken and its effect being true are treated as two different claims: an effect is not recorded as real until it has been read back and matched against what was claimed, closing the gap where automated systems quietly go wrong. Third-party extension The ontology is a base others build on, not a closed product. Institutions and developers define their own entity types and relationships against the shared model, so their systems interoperate by default instead of through one-off integrations. AI agent interaction Agents act under a verifiable identity and delegated authority, reading structured facts and writing signed actions. Every agent action carries proof of who authorised it and exactly what changed, so autonomy stays accountable. Before any action takes effect it is checked against its own preconditions and shown as a preview of exactly what will change, and authority delegated to an agent can only ever narrow, never widen, however far down the chain it is passed. For the actions where a mistake is expensive, the party who decided and the operator who carries it out can be required to be two different parties. Network effects Every new participant, asset and record makes the shared model more complete and more useful to everyone already on it. Because entities reference one another, value compounds as the graph grows, the more of reality that is modelled, the more that can be verified and acted upon. Switching costs Identity, history and proofs accumulate in the ontology and stay independently verifiable and portable, the record is not locked in a vendor silo. The real cost of leaving is re-establishing verified relationships elsewhere, which grows with the depth of history a party has built. Go deeper in the engineering blog: how AI agents act on the ontology , and why BlackRock's quantum warning makes a shared, post-quantum model urgent . KXCO does not ask you to trust the issuer's claim, or the issuer's reading of the law. It provides the machinery to prove the first , and one shared model, sourced and dated, to reason about the second. See it on public data → See the products → Bring us your question → --- This Markdown mirrors https://kxco.ai/ontology. The HTML page is canonical. Site index for AI clients: https://kxco.ai/llms.txt Copyright (c) 2026 Knightsbridge Group and KXCO. All rights reserved. Read it, retrieve it, answer questions from it, and quote it with attribution and a link to the source URL: that is what it is published for, and no permission is needed. Not permitted without written permission: copying, mirroring or republishing it, using it to build a competing product, or reverse engineering any KXCO product from it. Those are terms of use at https://kxco.ai/terms and rights under copyright and database law. Full notice: https://kxco.ai/llms.txt