You HAVE the data, but can you SEE it?

Investors

what am I actually exposed toTwo 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 demandConcentration, 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 spotThe 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 problemRisk 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 toFollow 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, counterpartiesAnyone 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.

A dashboard answers the question you already knew to ask. A model answers the one you didn't.

Your customers

one customer, not one record per systemWho 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 chartRoles, 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 ownSuppliers, 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 same parts

entities, not tablesA 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 relationshipsOwns, 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 biteWhat 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.

Map

look-through, all the way downDecompose 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 reconciliationExposure, 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 itStress one node and watch the effect propagate. Does the waterfall hold; is every leg permitted; is every claim proven. Contradictions surface instead of hiding.

A database stores rows. A blockchain stores events. Neither understands relationships, and relationships are where meaning lives.

Grounded, not guessed

every input carries a sourceAn 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 reachNo 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 modelsEvery 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.

Weights are not a record

absorbed, not organisedTrain 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 businessIf 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 filingNo 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.

Humans, businesses, governments, machines and AI agents don't get five different views of the world. They reason over the same one.

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 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.

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

Round Table, KXCO’s ontology engine, and the work of building the model with you, not a subscription to somebody else’s answer. It is available to funds, family offices and institutions, and it is deployed inside your estate rather than handed over as a download. 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. Investment teams can request the thirteen-page pack.

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.