Verificate Hybrid Intelligence combines capable open models with cited knowledge, governed decision logic, and controlled inference — so organisations can build AI that is useful, explainable, sovereign, and continuously improvable.
A large language model is a model of the internet's text. It reasons fluently — but it does not know your entities, cannot cite your records, and should not own your operational decisions. Hybrid Intelligence separates the three jobs so each is done by the layer built for it: general reasoning, cited knowledge, and governed policy.
Language generation and general reasoning — a capable open model you rent or run, never the owner of your facts or your decisions.
Facts stored as entity–attribute–value records with source, provenance, licence and time attached — retrievable, updateable, and citable down to the record.
Repeatable domain decision logic and constraints, trained on your data and outcomes — deterministic, auditable, and separate from the language layer.
Controlled serving on infrastructure you choose, with a confidence score for routing — deliver, confirm, escalate, or block.
Quality control at risky AI/agent delivery transitions — the same hard gate that protects AI-written software.
“Hybrid LLM”, “EAV”, “knowledge graph” and “Decision Transformer” are the architecture terms inside this solution. The separation is the point: facts live in a governed substrate, decisions live in a governed policy layer, and the language model narrates — it does not decide. This does not make hallucination impossible; it makes every claim and every decision traceable to a layer you control.
We begin with a baseline of publicly available information in your domain — law, regulation, guidance, literature — extracted once into the cited knowledge substrate.
Your own records are ingested into your private Verificate database — self-hosted or hosted by us — through the same AI ingestion pipeline, with provenance and licence attached to every record.
The result is a custom Hybrid Inference system that powers agents and AI applications across your organisation — every answer grounded and referenced, and anything that cannot be verified against your record is flagged, never served as fact.
Retrieval-augmented generation is a legitimate technique: relevant snippets are pasted into the prompt and a general model writes an answer. The precise difference is what is not there: a governed record of which fact drove which answer, a licence and provenance trail, and a decision layer that behaves the same way twice.
Ask the same context-injection system the same question twice and you often get a different answer — probability models sample words. For policy, credit, compliance, or student support, that is hard to run a process on.
A RAG system may have looked at a document, but the answer rarely records which policy, clause, or record drove the outcome. Reconstructing a chat is not reading a decision record.
LLM advisory agents tend to over-act: in our published study a zero-shot frontier agent recommended intervention 43 percentage points more often than the correct institutional policy. A policy trained on the institution's own data did not.
| Context injection — RAG | Hybrid Intelligence | |
|---|---|---|
| Where facts live | In the prompt window, at question time | In a cited, versioned knowledge substrate |
| Provenance & licence | Rarely recorded per answer | Attached to every record, cited per answer |
| Who decides | The general language model | A governed policy layer — the LLM narrates |
| Same input tomorrow | Often a different answer | Same decision — deterministic policy layer |
| Audit trail | Chat log; weak link to policy | Per-decision lineage — what records drove it |
| Where it runs | Often a public API | Your environment — sovereign by design |
Kevin is the live evidence instance of this architecture: an Australian sovereign-knowledge system built as a cited EAV graph over public Australian law — judgments, legislation, citations and outcomes — with provenance carried on every record. Under a preregistered Australian adaptation of Stanford's RegLab hallucination protocol (112 graph-verifiable questions, 42 false-premise traps), Kevin produced zero fabricated citations and a 0.0% response-level hallucination rate (upper 95% bound 3.3%), against 22.3% for the identical base model without the architecture — and 11.6% even with best-practice anti-hallucination prompting. The benchmark pack is published CC BY for independent re-running. M Try the workbench.
The video instance of Hybrid Inference: live broadcast frames are signed and indexed as they air, questions are answered only from that signed record, and the system declines rather than guesses when no matching footage exists. Every answer links to the clip so you verify by watching. Open the live demo.
OmniTX applies the layered architecture in a biomedical/genomics setting: cited domain knowledge and governed decision logic over an open reasoning model. Published as architecture evidence only — availability and results statements follow the claim-substantiation process on the Legal page.
A zero-shot frontier agent recommended action 43 percentage points more often than the correct institutional policy; a Decision Transformer trained on the institution's own data did not (EAV-DT study, OULAD). M
The trained policy produces the same action for the same complete state — an architectural property, measured at 0% flip rate. M
On a real 251k-case procurement log (BPI-2019), the continually retrained policy beat a frozen one (p≈0.009); a label-permutation placebo collapsed the gain ~389×. M
Sources: EAV-DT paper (arXiv:2606.29280) · CORTEX paper (arXiv:2602.17691) · Research & reproduction
Answers that must cite the governing record — policy, legislation, contracts — with licence and provenance attached.
Domain corpora where a fluent guess is worse than no answer, and every claim needs a source.
Jurisdiction-first knowledge bases served on infrastructure you control, under licences you can honour.
Operational decisions owned by a governed, deterministic policy layer — with the language model narrating, not deciding.
Bring a knowledge domain or a decision process. We'll map it to the layers — model, knowledge substrate, policy, serving, gate — and show you what governed AI looks like on your own infrastructure.