Fusion at the tactical edge. Northwind is our distributed Fusion-in-a-Box platform — sensing, inference, and decision support that survive the loss of the network, and never leave a combat effect to a machine. Lamassu extends the same Enkidu stack to ambient urban sensing — turning the city’s already-existing sensors into defence-grade awareness.
Northwind gives a forward unit the fused picture and decision support that today only a rear Joint Intelligence Centre can provide — on hardware a platoon can carry. It is an intelligence-fusion platform, not a combat platform: each node infers on what it can see, shares that view with its neighbours and hub, and reconciles upward through a forward fusion centre to the rear — one continuous fabric from the smallest node to the data centre.
The inference that decides the next minute runs on the node, not in the rear. Reachback enriches; it is never a dependency. Any node, hub, or link may be lost and the surviving fabric continues to observe, infer, and inform.
A mesh gives peer-to-peer resilience; a distributed hub-and-spoke overlay gives the inference hierarchy. Every tier maps to NVIDIA silicon sized to its role — so weight, power, and inference capacity match the job.
Carried by a dismounted team, a crewed vehicle, or an autonomous platform (UAS, UGV, USV). Runs limited on-board inference and exchanges observations peer-to-peer across the mesh.
A higher-capacity unit acting as a fusion centre for a cluster of local nodes — running the harder inference a node abstains to, and hosting the seam where local fusion meets the unit's C2.
A forward fusion centre at the Forward Operating Base. Connects dozens of hubs and runs models up to ~80B parameters for forward all-source correlation, then reaches back to the rear.
The rear, data-centre-class tier. Supplies the deepest all-source reasoning with Large and Frontier models, and returns national direction and feeds down the same path.
Every tier of the fabric runs the same two frameworks — one for where things may happen, one for whether they may.
A zoning architecture spanning every tier. It bounds each operation to a physical zone — a sector of terrain — and a logical continuum with explicit entry and exit conditions, then tracks the movement of threats and notifies exactly the nodes, hubs, and fusion centres that need to know.
A trust and security layer over NVIDIA NeMo Guardrails. It assigns trust-operation zones to agents, controls whether one may use a sensor or an actuator, encrypts every link across the fabric, and captures the end-to-end chain of custody behind every inference — the evidence that becomes confidence in a threat.
Some are sensed forward by the nodes and hubs themselves; others arrive from the Central fusion centre over reachback. All enter through one common ingestion pipeline that tags classification at acquisition and checks it at every share.
COMINT, ELINT, direction-finding and electronic order of battle.
EO/IR imagery from organic RPAS forward; satellite imagery from the centre.
Acoustic, seismic, and RF measurement signatures from emplaced sensors.
SALUTE and spot reports, source reliability, document exploitation.
Foundation maps, terrain, line-of-sight and mobility analysis — field-updated.
Open-source reporting and context, brokered from the enterprise.
Staff product and direction from CJOC J-2, pushed down to the edge.
Five Eyes and coalition feeds, brokered centrally for releasability.
Northwind's actuator authority reaches only to intelligence collection — tasking, repositioning, or steering a sensor to gather data — which an agent may issue autonomously once it has earned a high trust zone. It never authorises a kinetic effect. An engagement is always cued to, and decided by, a cleared human operator or the combat platform's own function.
Book a technical briefing and see fusion, zoning, and the trust harness running on ruggedised edge hardware.