page · results · architectural targets · NCE v2.4

No promises.
Targets.

These figures are the NCE architectural targets — built on 6 months of development and real-sector testing. Not yet production results, because there is no production yet. Said clearly.

/ detail · 4 metrics

Four figures. Four commitments.

Defined from the outset — measured and refined on each deployment.

12wks.
speed · time-to-value

From decision to first measurable results

Not 18 months of IT project. Twelve weeks to go from signed brief to first results on your real use case. Before/after measurement, executive committee presentation in week 12.

Method: project in 4 phases P0–P3 — defined deliverables at each stage
Scope: applicable from 500 documents · PDF, DOCX, XML, regulatory export formats
Commitment: GO/NO-GO presented at end of project · all deliverables retained whatever the decision
<5%
reliability · NCE target

Target error rate on regulatory corpus

RAG approaches plateau between 35 and 45% error on dense regulatory corpus. The KG + NCE architecture structurally targets the operational threshold of < 5% — through 14 reliability dimensions continuously measured.

Architecture: knowledge network + entity whitelist + fidelity validation
Protocol: sector golden tests · comparative evaluation vN vs vN−1
Reproducibility: every answer traces back to source paragraph · → see the NCE protocol
3days
deployment · go-live

From decision to a live NCE

No 18-month IT project before the first result. The NCE infrastructure — knowledge graph, vector engine, interface — is deployed in your infrastructure in 3 business days. Connection to your existing document sources included.

Deployed components: knowledge graph, vector engine, NCE interface — 100% within your perimeter
Infrastructure modes: physical, virtualised or accredited enclave (air-gap possible)
After deployment: document ingestion started in Phase 0 — first results in week 4
0leak
security · exposure

Data exposed outside your infrastructure

100% on-premise. No call to an external service. No cloud dependency. The engine, the network, the interface and the models all live within your perimeter — physical, virtualised or accredited enclave.

Architecture: all modules (engine, network, interface, models) within your perimeter
Verifiable: network capture report delivered with the solution — for CISO/DPO validation
External dependencies: none — air-gap operation possible
NCE v2.4 · Neural Context Engine

14 reliability dimensions. A rigorous evaluation protocol.

The < 5% score is the structural target of the NCE architecture — not a marketing promise. It is carried by 14 reliability dimensions continuously measured, an entity whitelist, out-of-domain refusal, and fidelity validation of every answer.

See the NCE architecture →
/ technical metrics · DQE pipeline · NCE v2.4
automated tests 859+ 0 regression · v2.4
extraction confidence 83–87 % average score · real corpus
qualification stages 18 DQE pipeline · 2 phases
extraction duplicates < 8 % rate · fresh corpus

Measured on real phytosanitary corpus (2023–2024) · formal qualification in progress

/ methodology · measurement

How results are measured

Sector golden tests

Reference question sets with expected answers, replayed at each NCE version on the same corpus. No cherry-picking — same scope, same evaluators.

NCE vN vs vN−1

Every version is compared to the previous one on the same questions. KPIs: average score, pipeline confidence, refusal rate, contradictions detected. No figures published without this protocol.

Auditable protocols

All test sets are documented. Provided under NDA for clients in evaluation. The measurement methodology is part of the delivery contract.

/ progression · jan → jun 2026

From field findings to today's targets

Six months of work. A single validation ground: real regulatory archives, in the phytosanitary domain. These targets don't come from generic benchmarks — they come from documents you know.

Jan
January 2026 · field findings

Inaccessible archives. Corporate memory walking out the door.

In regulated industries, years of critical decisions sit side by side with no link between them — studies, assessment reports, internal notes — scattered across formats and servers. Regulatory expertise lives in people's heads, not in systems. When the expert leaves, the memory leaves with them. That is the precise problem, documented in the field, that NCE is built to solve.

Feb
February 2026 · building the NCE engine

Zero compromise on confidentiality — built for the most demanding environments

Before a single line of code, one absolute rule: no regulatory data ever leaves the client's infrastructure. Ever. From these principles came the NCE engine — Neural Context Engine — designed to reason over your archives without ever exposing them, in a fully isolated environment with no external connection required. A non-negotiable requirement, dictated by the reality of the pharmaceutical, phytosanitary and nuclear industries.

Mar
March 2026 · NCE v1.0

NCE learns to read your archives — and to understand the connections between them

NCE ingests your documents in every existing format — and does more than index them. It rebuilds the connections between the information it finds: which study covers which substance, which decision applies to which use, which standard takes precedence over which. Tested from the outset on real phytosanitary archives (marketing authorisations, ANSES). No answer without an identified source.

Apr
April 2026 · NCE v2.0

An answer that cites its sources — and that knows when it doesn't know

NCE integrates the domain's official reference data as an anchor of truth. The reliability of each answer is assessed against 11 measured criteria — grounded in established scientific studies, not arbitrary parameters. If an answer goes beyond the limits of the corpus, NCE refuses to answer rather than invent. In a regulatory context, it is that refusal that lends credibility to everything else.

May
May 2026 · NCE v2.4 · current version

Every answer verified. Every source traceable. Ready for audit.

NCE automatically checks whether each answer is faithful to the source documents — and flags it explicitly. It retrieves information even if you use a different term from the original author's. The test procedures cover 778 scenarios on real corpora. This isn't presentation — it's the rigour of a system built to withstand inspection.

Jun
June 2026 · validation

Validation on real archives

The tests run on real document corpora to confirm the expected precision levels. Every measured gap sharpens the evaluation protocol — rigorous, documented work carried out in the field before any wider generalisation.

Jul
July 2026 · NCE v2.5

NCE challenges its own answers before passing them to you

NCE combines three complementary search modes across your corpus to cover every angle of a regulatory question. Each answer's reliability is measured against 14 distinct criteria — and the answer is held back if it fails any of them. The first version able to question its own answer before delivering it to you.

Aug
August 2026 · NCE v2.6

Advanced anomaly detection

NCE no longer just answers: it automatically spots and flags inconsistencies in your documents — a value out of range, outdated information, sources that contradict each other — with every alert justified and tied to its source. Where a conventional engine lets it through, NCE raises the flag.

Sep
September 2026 · NCE v2.7

A certified knowledge base

NCE only admits into its memory information that is verified and tied to a recognised source; the rest is set aside. Less noise, a sound base that every answer can rely on with confidence.

Q4
Q4 2026 · NCE v2.8

Multi-sector expansion and advanced multilingual mode

NCE opens up to other regulated sectors beyond phytosanitary, adapts the level of its answer to each user's role, and extends its command of languages with an advanced multilingual mode. Also on the horizon: autonomous investigations run across your corpus.

/ your results

Bring your case.
We quantify together.

No generic promises. 30-minute diagnostic: we assess what KnowWeave can do on YOUR data.