Architecture

How KXCO fits together

Everything KXCO ships stands on the same cryptography, and every decision about whether a signature counts is taken in one place. This is the estate on one page: what is free, what is licensed, and what each piece is actually for.

KXCO architecture: free post-quantum packages feed the licensed Command control plane, which governs the licensed products On the left, four free open-source npm packages: kxco-post-quantum provides the primitives, eslint-plugin fails a build that uses a raw primitive, kxco-pq-hsm holds keys on a token, and kxco-pq-scan finds the RSA and ECDSA already in your estate. In the centre, KXCO Command, the licensed control plane for admission, revocation and evidence. On the right, the licensed products it governs: Armature L1, KXCO Treasury, KXCO Sentinel, and Round Table, which is the engine that produces an ontology. KXCO ARCHITECTURE One cryptographic core. One control plane. Every product downstream. FREE · OPEN SOURCE · npm LICENSED PROVIDES_PRIMITIVES FAILS_BUILD_ON_MISUSE HOLDS_KEYS_ON_TOKEN ADMITS GOVERNS_KEYS SCOPES_AGENTS ISSUES_EVIDENCE PRODUCES FINDS_WHAT_YOU_ALREADY_HAVE Your existing estate RSA · ECDSA · mostly transitive, mostly unrecorded kxco-post-quantum ML-DSA · ML-KEM SLH-DSA eslint-plugin no raw primitives kxco-pq-hsm PKCS#11 on-token kxco-pq-scan CycloneDX CBOM KXCO Command licensed control plane admission · revocation · evidence Armature L1 ML-DSA-65 from block 0 KXCO Treasury economic operating system KXCO Sentinel quantum-resistant cloud Round Table the engine Ontology the output The free packages are the primitive, the guardrail and the discovery. Command is the decision: whether a signature is accepted, by whom, under what mandate, and with what proof. kxco.ai · sixteen packages on npm, Apache-2.0 · Command and the products are licensed

Every green circle is a free install. The black circle is the only thing in the picture that makes a decision.

The left

Free, and deliberately so

Sixteen packages on npm under Apache-2.0. They give you the primitives, a lint rule that fails your build if someone reaches for a raw one, a hardware boundary for keys, and a scanner that reads your lockfiles and tells you what RSA and ECDSA you are already carrying.

Nothing here calls home and nothing here needs us. You can audit the lot before you trust any of it, which is the point of shipping it this way.

The middle

The decision, in one place

Cryptography tells you a signature is mathematically valid. It cannot tell you whether it should count. Command is where that second question is answered.

That is the licensed part, because it is the part that carries the consequence.

The right

Products, downstream

Armature L1 has used ML-DSA-65 since block zero. Treasury runs the economic operating system. Sentinel scopes what an AI agent is allowed to do. Each one asks Command the same question and gets an answer it can prove later.

They are separable. You can license one without the others, and each still stands on the same core.

The Round Table sits at the centre. An ontology is what it keeps.

The ontology is the output you can see, and it has its own page. Round Table is the engine that produces it. The engine is not available publicly, and there is no free tier and no waiting list. We do not publish our own graph, our own data or our own method: knowledge sovereignty is the product, and we are not going to be the exception to it.

What is public is a demonstration. The live showcase runs on public data only. What the engine finds in your own books stays between you and it.

See the packages The five things you can do Developer docs