Battlefield Operations
Battlefield Operations is mission-domain decision support running on the same governed substrate as the rest of the platform, so a fires decision inherits the same identity, classification, human-authorization and audit model as a database read. It is offered as a gated deployment option, not a general-availability console.
What it computes, and what it does not
One boundary governs everything below, and it is the first thing to establish:
This is command-plane compute. These surfaces model, score, prioritise and sequence. They do not touch a weapon or a fire-control system. The output of a weapon-target pairing is a recommendation on a screen and a row on an audit chain, not a round leaving a tube.
Everything is reached through a single ITAR-gated surface. The gate is a four-way conjunction of military licence tier, sovereign or tactical deployment profile, an export-eligible class, and a feature flag, applied at the router rather than per endpoint, and it fails closed: with no military licence installed, every one of these routes refuses.
The reachable slice
The surface is broad and it is moving. The subsystem carries a machine-readable inventory of substantive exports, covering sixteen mission subpackages, which continuous integration imports on every build so a deletion or a regression to a stub fails rather than passing quietly. The route surface over it grows faster than any count printed here would stay true, so this page describes the domains rather than totalling the endpoints.
It spans the mission domains below, and the fires and tracking decision chain described next is the spine that human authorization sits on:
- Fires and targeting, call-for-fire formatting, ballistic and engagement-zone solutions, weapon-target pairing, rules-of-engagement checks, human authorization, and battle-damage assessment.
- Counter-battery, deriving a firing origin to respond to incoming fire.
- Blue-force and composite tracking, position reporting, composite tracks, Kalman / EKF / IMM filtering, and fratricide prevention.
- Radar ingest, bringing radar returns into the track picture.
- Ammunition status: the logistics state a fires decision depends on.
- Orbital tracking, including the link-budget calculation for a satellite / tactical-satellite (TACSAT) link.
Beyond that spine, the mission domains each carry a real surface:
| Domain | What is reachable |
|---|---|
| Intelligence | Course-of-action development, scoring, comparison and wargaming; threat prediction and assessment; warning indicators; PMESII and JIPOE analysis; centre-of-gravity analysis; priority-intelligence-requirement sweeps; deception planning; sensor fusion; terrain assessment; counter-intelligence vetting |
| Fires | Call-for-fire, ballistic trajectory, fire envelopes, weapon-target pairing, high-value-target prioritisation, strike-package and target-list build, joint-terminal-attack validation, air rules-of-engagement, loiter missions, long-range precision fires |
| Command structure | Planning-process advance, force units, operational design, air-tasking cycles, theatre allocation, campaign design, handovers, battle-drill transitions, combat-power assessment |
| Defense | Air and missile defense engagement, integrated air-defense cycles, close-in weapon-system timing and queueing, counter-rocket/artillery/mortar, counter-UAS, counter-IED fusion, torpedo evasion, decoy planning, force protection |
| Logistics | Convoy planning and threat assessment, resupply priority, sustainment across horizons, refuel cycles, personnel accountability, casualty evacuation, recovery planning, throughput optimisation |
| CBRN | Hazard mapping, plume dispersion, weather, alerts, concealment planning, counter-WMD interdiction |
| Sensors | Acoustic and underwater localisation, automatic target recognition matching, maritime patrol planning, periscope detection, counter-mortar scheduling |
| Electronic warfare | Suppression planning and sweeps, counter-UAS tiering and track advance, battle-damage assessment |
| Swarm | Path planning, formation positions, coverage assignment, collision checking, search patterns, cordon arcs |
| Soldier systems | Personnel and health status, dead reckoning, biometric stress, casualty treatment planning |
| Platforms | Firing solutions, carrier launch cycles, UAV recovery, escort and surface-patrol planning |
| Space | TACSAT link sweeps, joint-operations-area airspace |
| Tactical cyber | Cyber-electromagnetic deconfliction, adversary assessment, payload selection |
| Tracking | Composite operational picture aggregation, Kalman, IMM and range-bearing filtering |
| Combat engineering | Obstacle planning, route clearance, mobility corridors, bridge assessment, mine-countermeasure mission planning |
| Media | Imagery compression and delivery-channel selection for constrained links |
Recent additions include a multi-battery air-warfare raid roll-up, counter-rocket impact and point-of-origin back-projection, mine detection and clearance tracking, weaponeering probability solves, a Find–Fix–Track–Target– Engage–Assess cycle for time-sensitive targets, and a CBRN hazard subsystem with Gaussian-plume dispersion.
Rules of engagement and human authorization are not an add-on here, they are the reason any of this can be pointed at a real operation at all. Every fires decision passes an ROE check and a human authorization, and lands on the tamper-evident record.
The reachable decision chain
Figure: the Battlefield Operations decision chain. A track picture built from radar, tracking and orbital inputs feeds a fires proposal (cyan, in-flight), which passes a rules-of-engagement check and human authorization (amber gate) before becoming authorized fires (green), with every decision, including refusals, recorded. The mission domains feed the same spine and land on the same record. Ceiling: every element is command-plane compute behind a fail-closed ITAR gate; none of it contacts a weapon or fire-control system.
Table equivalent
| Element | State | Reachable? | What it is |
|---|---|---|---|
| Blue-force + composite tracking | track picture | Yes | Position reporting, composite tracks, Kalman/EKF/IMM, fratricide prevention |
| Radar ingest | input | Yes | Radar returns brought into the track picture |
| Counter-battery | input | Yes | Deriving a firing origin from incoming fire |
| Ammunition status | input | Yes | Logistics state a fires decision depends on |
| Orbital / TACSAT tracking | input | Yes | Orbital tracking including satellite link-budget |
| Fires + targeting | candidate / in-flight | Yes | Call-for-fire, ballistic solutions, weapon-target pairing |
| ROE check + human authorization | refusal gate | Yes | Every fires decision passes ROE and a human authorization |
| Authorized fires + BDA | verified | Yes | The authorized action and its battle-damage assessment |
| Tamper-evident record | verified | Yes | Every decision, including refusals, recorded |
| Mission domains (intel, structure, defense, logistics, CBRN, sensors, EW, swarm, soldier, platforms, space, tactical cyber) | reachable | Yes | Each carries a real surface; see the table above |
What the boundary actually is
The old boundary here was coverage: whole mission verticals existed in the model and not on a running cell. That is no longer where the line sits. The line is now about what these surfaces do, and it is worth being exact, because it is the difference between a defensible claim and an indefensible one.
They compute; they do not act. A weaponeering solve returns a probability. A targeting cycle returns a phase and a recommendation. A dispersion model returns a hazard footprint. Acting on any of it is a separate decision made by a person, through the rules-of-engagement and authorization gate, and the acting is done by systems that are not this one.
Nothing here is graded. These are mechanisms, described. No claim is made that any model has been validated against operational data, accredited, or tested in the field. A customer evaluating this should expect to validate the models against their own standards. The surface exists; the evidence that any particular model is fit for a particular mission is theirs to build.
A gated deployment option
Battlefield Operations is not part of the general product. It sits behind an issued military-tier licence and export-control gating, and is enabled per customer. It is a gated deployment option carrying the reachable slice above, not a console anyone can turn on.
Across the deployment matrix
The reachable decision chain runs on a single cell with local tracking, ROE enforcement and human authorization, so it holds in the sovereign, air-gapped corner with no coordinator, the corner this capability is deployed into. It works single-cell and, where cells can reach each other, multi-cell.
Related topics
- Tactical Communications, the governed field network the mission picture rides over.
- Sensor Intake, governed capture that can feed the track picture.
- Governance (deny-closed), the gate model the ROE and human-authorization step fits into.
- Audit and tamper-evidence : the record every fires decision, and every refusal, lands on.