C4ISR · the intelligent decision core

Be the intelligent core, not the plumbing.

OAK's C4ISR decision layer fuses the picture, reasons over it, and recommends — sovereign, explainable and AI-assured. It sits on top of the C2 and comms backbone you already run: it ingests the fused sensor picture and returns ranked, trust-wrapped courses of action to a commander who stays on the loop. Against a foreign black box you can't audit, OAK is a decision core you own and can open up — and it's built on OAK's shipped, tested products.

Request a briefing How it decides

UNCLASSIFIED · representational // a decision-core capability in active development — built on OAK's demonstrator-grade software, not a fielded C4ISR system

Why a decision core, not another box

Three things a black box can't give you

The commodity C2 chassis, comms and infrastructure are a prime's game. The brain — the part that reasons and recommends, and that a commander has to trust — is where OAK is different.

Physics-grounded & explainable

Every recommendation traces to visible maths and the factors that drove it — a plain-language WHY, not an opaque score. Auditable by design.

Uncertainty-calibrated

Each course of action carries a calibrated confidence. A thinner or contested sensor picture honestly lowers it, so a commander knows how sure the machine really is.

Assured

The AI in the loop is graded by OAK's TEVV assurance battery — reliability is measured and gated, not asserted. The single biggest blocker to trusting AI in C2.

The sense → decide → act loop

Situation in → ranked courses of action out

1 · SENSE

Ingest the fused track picture — CoT/TAK, Link-16 formats, a live feed — into a Situation.

2 · DECIDE

Rank courses of action: worst-case-robust first, then cheapest-sufficient — each with confidence & a WHY.

3 · APPROVE

A commander reads the card, the confidence bar and the assurance badge — and approves. No auto-release.

4 · TASK

The approved action goes back out as tasking (CoT / J-series) to the systems that execute it.

The commander console turns an editable situation into ranked COA cards — confidence bar, plain-language rationale, assurance badge and an APPROVE gate.

The common operating picture the decision core reasons over

The live common operating picture the decision core reasons over — drawn from OAK BMS. Representational, unclassified data.

What's in the core

A working decision layer, not a diagram

Decision core — Situation → ranked, trust-wrapped courses of action; human-on-the-loop approval, no autonomous release
Commander console — editable situation → ranked COA cards (confidence bar · WHY · assurance badge · APPROVE)
Multi-sensor track fusion — radar / ESM / EO detections → fused tracks with a quality score; a thinner picture flows through to lower confidence
Theatre planner — value-weighted defence across scarce shared pools (sensing, interceptors, release authority); minimises value-at-risk over a closing window
Interoperability — CoT/TAK, Link-16 message formats and DIS/HLA (representational); ingests a live UDP feed
Tamper-evident audit — a hash-chained record of the whole decide → approve → task loop, verifiable INTACT/BROKEN
Assurance evidence — requirements-traceable verification and a confidence-calibration report

Multi-INT fusion feeding the decision core

Multi-sensor fusion resolves the picture the core reasons over — drawn from OAK's multi-INT fusion. Representational data.

Not a slide — it layers on shipped software

Built on OAK products you can see today

The decision core imports OAK's shipped, tested engines rather than re-inventing them — which is why it's real, and why productionising it is de-risked.

Own the decision layer

For a sovereign force that doesn't want a foreign black box in command, we'll walk the decision core end to end — sense, decide, approve, task — on representational data.

Request a briefing