Digital Targeting Web
Volt4 Reconciliation

The DTW programme requires an API management service as an element of its integration layer — applying the Exploitable-by-Design pattern to the sense/decide/effect mission thread. This page maps every assessed requirement against Volt4 features.

10/10
Technical criteria
6/6
Challenge themes
7/7
EbD principles
4/4
Strategic objectives
Programme intent

Targeting Vision

Enhance the UK's warfighting capability by 2030 by creating the ability to sense, understand, decide, effect and assess at a pace that overwhelms adversaries.

Scale Objective

Increase targeting scale, pace, precision and accuracy — with a ×10 capability uplift by 2027 and ×30 by 2030.

What the DTW Is

"An adaptive, secure and evolving set of digital services that unite users, systems, and platforms to enable targeting accuracy, precision, speed, and resilience across all domains." Delivered NATO-first, aligned to DTW-RA v0.3 and AJP-3.9.

Cycle 0 Challenge

Develop an API management service as an element of the DTW integration layer, taking the Exploitable-by-Design pattern and applying it to the targeting mission thread including sense/decide/effect integration.

Strategic objectives
SO1

Accelerate speed, scale & effectiveness

Integrate AI into the targeting process with human oversight. Faster sense → decide → effect cycles.

SO2

Trusted, NATO-compliant data

Data-centric security as default; confidence-scored provenance; NIST-aligned; quantum-safe key options; STANAG 4774/4778 binding in development.

SO3

NATO-first, agile, enterprise governance

Declared, auditable distributed policy as governance. Standards-based interoperability with cross-organisation federation.

SO4

Resilient in contested environments

Bearer-agnostic, offline-resilient, no central chokepoint, tamper-evident telemetry, edge-deployable under degraded conditions.

Technical criteria — Cycle 0 assessed requirements

Submissions are assessed against ten criteria. All ten are fully addressed by Volt4.

R1
Resilience of the API management layer/gateway
Synapse signed-event model gives automatic redundancy via synchronisation + provable integrity; Volt Registry makes redundant gateways deployable/discoverable; gRPC/REST/Wires transports.
R2
Resilient integration in low-bandwidth/intermittent network environments
Synapse multi-document sync optimised per bandwidth; NIST-compliant policy adapts data to comms and swaps bearers; resilient when disconnected with no loss of security. Demonstrated under DSTL OFEME; deploying for NATO IC Cyber Resilience by Design.
R3
Security of the API management layer/gateway
Dynamic distributed policy enforcement anchored with strong identity (PKI); data-centric security (signed W3C VCs); E2E encryption; quantum-safe key options.
R4
Secure monitoring and telemetry
Multi-dimensional telemetry through Synapse; integrity + provenance built into the data-centric-security model; air-gapped transports; access mediated by policy + optional attribute-based encryption.
R5
Federation of access/authorisation across organisational boundaries
Fully distributed W3C DID identity + distributed policy definition/enforcement — supported as standard; trust attributes negotiated between parties.
R6
Wide range of API types beyond REST or SOAP
Out of the box: REST, WebSocket, gRPC, Wires, Synapse. New protocols added as Cortex agents (BAE combat system: AIS, ADS-B, InteACT, FedNet, OMG OARIS/ALMAS/TEX).
R7
Securely integrate third-party services without a mature API
Cortex Agents surface arbitrary data or local system calls as APIs within Volt, including legacy and proprietary systems.
R8
Local and cloud deployability
C++ native (<100 MB), multi-OS; deployed on public/private cloud and edge (drones, cameras, battleships). More compact installs possible.
R9
Ease of use for developers, including API discoverability
Discovery API + declared (signed) data on Synapse; Volt Registry; fully documented and open with many live deployments.
R10
Alignment to Exploitable-by-Design
Signed, synced distributed-data paradigm addresses the n² problem directly. See the EbD principles below for per-principle mapping (refs 58–64).
Challenge themes

Six challenge areas define the problem space. Volt4 addresses all six.

C1
Securely source and share data across dispersed, siloed locations
Federated DID identity + distributed policy connects MOD ↔ NATO ↔ intelligence ↔ partners across security levels; data-centric security + E2E encryption keep data safe in transit and at rest; sync connects the Sensor-Decider-Effector chain across tactical/operational/strategic.
C2
Combine data sources to produce information and generate insights
Sensor fusion correlates radar/AIS/satellite/IoT into one coherent picture; signed VC schemas fuse heterogeneous sources with verifiable structure and provenance; AI agents derive insight.
C3
Build knowledge from information and make decisions faster
ML anomaly detection / pattern recognition / threat identification triages the data deluge; Cortex AI agents accelerate analysis; human-in/on-the-loop keeps decisions accountable.
C4
Provide the Digital Targeting Web out to the Edge
<100 MB native install on constrained hardware; offline sync with no security loss; bearer-agnostic transport across any comms link.
C5
Upgrade, integrate and interoperate at pace
Modular, additive Cortex agents add protocols/systems without re-architecture; signed VC schema + continuous-assurance policy let new data join live systems without compromising security.
C6
Provide skills, training and tools
Digital twins and synthetic environments provide training, test and validation tooling; open, documented, discoverable platform lowers the developer barrier. Courseware delivery remains service-led.
Exploitable-by-Design — data fabric API principles

The EbD framework frames APIs in a data-fabric architecture where data is treated as a product and domain-oriented teams own it. Volt4 satisfies all seven principles.

§58
Data Product Access

Discovery API + signed declared data; standardised interfaces; multi-protocol access.

§59
Data Integration

Signed schemas fuse sources; Cortex agents wrap any source; Synapse combines data products.

§60
Data Governance

Distributed policy — defined and enforced through declared, signed, auditable policy with continuous assurance.

§61
Metadata Management

Signed Verifiable Credential Schema (metadata must be signed); operational metadata assembled across supply chains via synchronised VCs (NIST SP 1800-36, TAIBOM).

§62
Scalability and Flexibility

Distributed resilience + redundancy; signed VC schema/API model lets new data be added to live systems without compromising security.

§63
Monitoring and Logging

Multi-dimensional, integrity- and provenance-bearing telemetry through Synapse.

§64
Overall — democratisation, interoperability, agility

Standards-based, decentralised data fabric addresses the n² connectivity problem at its root.

Coverage summary
All 10 technical criteria, all 7 Exploitable-by-Design principles, all 4 strategic objectives and all 6 challenge themes are fully addressed.
Maturity & submission notes
TRL 6+

Volt4 is deployed/under evaluation with NATO, MoD OFEME, BAE InteACT and reviewed in NIST NCCoE labs — supports a TRL-6+ claim; cite the specific deployment per criterion.

Quantum-resistant encryption

Key management supports quantum-safe methods — state the specific algorithms and roadmap explicitly in submission.

STANAG 4774/4778

Binding is in development — flag as roadmap item, not delivered.

Adversarial-AI / chaos testing

DTW programme expectations not directly claimed by a feature; position Volt4 as the resilient fabric on which those capabilities run.

Volt4 — the verifiable trust fabric. Secure · Sovereign · AI-native.

100% UK founder-owned. No foreign parent, no foreign capital, no US platform dependency — and cryptographically provable.

Copyright 2026 NquiringMinds. All Rights Reserved