Under — permissioned memory
Files, drawings, sheets, mail and selected facts become citable pieces with a map of relations and a trail of versions. If you could not open it, the core will not perform it as an answer. Similarity is not a right.
Nexus Business Intelligence
One core. Products are how it develops.
Anyone can bolt a chat window onto an ERP in a quarter. Nobody can bolt on memory of what an organisation already owns, a refusal the caller cannot argue with, and a write that waits for a responsible person to Confirm. That circuit is the asset. Products are the hosts it runs in.
Read this as a core
Hosts keep the books. The core sits under them as memory — and above them as agency.
Nexus Business, Nexus Industrial and the products that follow are hosts of the same core. Each host keeps its own system of record — invoices, batches, cases. The core does not steal the books.
Change the host, keep the contract. That is how one technology becomes a family instead of a pile of copilots.
The job classic BI never took
People still stitch meaning in their heads. That stitching walks out of the building when they leave.
Classic BI answers what happened inside a warehouse of numbers. Search finds a word in a file. Apps record rows. Meanwhile the only place where a drawing, a supplier mail, a cost sheet and a promised date become one decision is somebody’s memory — and that person retires, resigns, or is simply on holiday the week it matters.
The next decade is not won by prettier charts. It is won by closing the circuit suite vendors left open: ingest what was never online, retrieve it under the same rights as opening the file, explain why something deserves attention, and only then propose a write that a responsible person Confirms.
The core, in three moves
Memory with rights. Attention with a spine. Action under identity.
Beside — typed signals
Detectors raise what, how severe, how confident, on what evidence, what to do next. If the caller must not see that domain, the product withholds. That refusal is a feature a DPO can explain.
Above — Confirm as law
Copilots work as the signed-in person, not as a service account named AI. Reads stay inside the caller’s rights. Writes wait for Confirm. A deputy may research; it may not commit.
How the core thinks
Models draft. They never become a second source of truth.
A question is never steered by “if they said invoice, open finance.” The core gives the model tools. Tools query tenant data and enforce role and visibility. Invented tables are not a feature.
Retrieve is a keep-set, not a lottery: find related pieces, situate them among neighbour records, then keep only what the same permission check would allow in the product. Over-fetch, then refuse. Citations point back at the live file.
Hybrid AI as policy
Local where thought must stay close. Frontier where language still needs a stronger mind.
Planning, turning files into memory, reading a page, hearing a recording — those can stay on your own metal, inside the building, on the plant network. Frontier models stay useful for messy language and open-ended action, and they are reached through a gate you can see. Full-local is available when a board demands it.
You change placement, not product. Hybrid is not a SKU you buy twice; it is a policy an executive can state in one sentence and a procurement team can verify.
Agents, without a second philosophy
A squad of copilots that know the company — and still wait for you.
Work, Drive, CRM, Finance, Quality, AI Act, Insights and Administration are not eight AI products with eight roadmaps. They are one mind with a different union of tools, loaded progressively: a small sharp set per question, more only when the question earns it.
Every run leaves the same three facts behind — who asked, which mind answered, what it cost. AI becomes a managed centre of cost with an owner, instead of a silent robot holding a password to production.
Knowledge Engine
Ingest what was never crawled. Retrieve only what you could open.
Most of a company’s knowledge is not online. Specifications, CAD, cost sheets, decisions trapped in mail, ERP and portals the plant still pretends are “the system.”
The Knowledge Engine is the memory plane of the core: additive ingest, a living graph, citations to the live record. Knowledge and Intelligence are independently switchable — they share identity and policy, not a fused AI database.
The portable contract
Four packs change. The loop does not.
Ontology pack
Name the world the organisation actually uses — customer, asset, batch, course — not only project and invoice.
Connectors
Files, APIs, tables, mail, drawings. The core does not require every source to live inside one product.
Policy pack
Identity, roles, exclusions. The engine reuses the host’s access control; it does not invent a parallel security model.
Detector pack
What “deserves attention” means in this world. The signal object stays the same: score, confidence, evidence, next step.
What a wrapper does not have
- Permissioned memory — denied subjects stay out by default.
- Action under identity — your rights, not a shared robot password.
- Confirm as law — no important write without a person on the record.
- Signals with evidence — attention is owned, not displayed.
- A visible cost of thought — tokens, model, who asked.
- Hybrid placement as policy — not a new product per cloud.
Hosts, not restarts
The same core in the office and on the plant.
Nexus Industrial
The same core on the plant: CAM to the mill, replenishment to the dock, downtime to the visor, kilowatts, quality and finite capacity — one memory, one Confirm.
Nexus Business
The workplace for work, documents, commercial, finance, quality and AI governance — with Confirm on every write.