The gap NODERIQ closes

There is a specific failure that shows up in almost every autonomous system I have looked at, and it is not the one people expect. The models are usually fine. The sensors are usually fine. What breaks is the handover: the moment a machine produces a recommendation and a person has to decide whether to act on it.

At that moment the person needs three things. What did the system observe. How confident is it, and on what basis. What would happen if it is wrong. In most deployed systems, at least one of those is unavailable, because the pipeline flattened it somewhere upstream. A probability distribution became a label. A confidence became a threshold. A chain of inference became a single number on a dashboard.

NODERIQ exists because of that flattening.

Recommendation is not authority

The design starts from a separation that sounds obvious and is routinely violated in practice. A system may recommend. A person authorises. Those are different operations with different evidentiary requirements, and collapsing them is how organisations end up with autonomy they cannot defend afterwards.

Keeping them separate has consequences all the way down the stack. If a human is going to authorise, the system has to preserve what the human needs in order to authorise responsibly. That means uncertainty has to survive the journey from sensor to screen. It means the evidence has to be small enough to cross a constrained link, because a contested environment does not give you bandwidth on request. It means ambiguity has to route somewhere, to someone accountable, with the supporting material attached rather than described.

So the operating loop reads: sense, qualify, share, coordinate, verify, escalate. Qualify is the step most architectures skip. It is the one that represents uncertainty rather than resolving it prematurely.

Where the core lives

The core is classical and edge-operable. That is a deliberate constraint rather than a limitation I am apologising for.

Edge-operable means the system remains useful when the link degrades, which is the condition it will actually operate in. Classical means the primary path uses computation that exists, is understood, and can be reasoned about under failure. Anything more exotic has to earn its place against that baseline.

This is where NODERIQ connects to the quantum research. The QANTIS work asks whether a quantum belief-update primitive can be trusted inside a classical decision loop. That is not a question about quantum supremacy. It is a question about whether a specific bounded component adds decision value once accuracy, latency, reliability and cost are all accounted for. Four evidence gates decide it:

G0, define. The workload has to be explicit, measurable, latency-tolerant and safe to run outside local control. If it is not, nothing else matters.

G1, simulate. The alternative method has to produce valid results against a strong classical reference. Not a weak one chosen to flatter it.

G2, preserve. Hardware execution has to preserve information, constraints and uncertainty. A method that gives a faster answer by discarding the uncertainty has not solved the problem, it has moved it.

G3, qualify. The complete path has to add decision value after everything is counted.

A method that fails a gate does not advance. That is the entire mechanism, and it is deliberately unglamorous.

Two surfaces, one core

The same core serves two operating contexts. NODERIQ Defense addresses multidomain autonomy for uncrewed platforms in contested environments, and went to NATO DIANA’s challenge track in June. NODERIQ-CRN covers civil resilient operations: infrastructure inspection, emergency logistics, field service, connected mobility.

The engineering is largely shared because the underlying problem is shared. What differs is the operating boundary. In defence the boundary is contest. In civil resilience it is safety and continuity. Both need a system that can say what it saw, how sure it was, and who authorised what followed.

What this is not

NODERIQ is an applied research and productisation programme. It is not a released product, a certified capability or a deployed system, and I am careful about that wording because the distinction matters in this domain more than most. Claiming operational validation you do not have is not merely embarrassing. In a defence context it is dangerous.

The honest position is that the architecture is worked out, the evidence gates are defined, the civil and defence surfaces are described, and the classical core is where the effort currently sits. The quantum pathway remains conditional. It will stay conditional until it passes G3, and it may never pass.

That last sentence is the one I would most like people to take seriously. A research programme that cannot describe the conditions under which it would abandon its most interesting idea is not a research programme.