Sub-module

Joint A2/AD Orchestration

Compose access, denial, suppression, protection, sensing, sustainment and recovery across operational domains.

How it works

Domain postures and dependencies remain distinct while the campaign model exposes cross-domain windows, residual capability and failure propagation.

Build and compare joint alternatives, qualify contributions and prepare owner-bound mission packages.

Planners can see which combination opens or protects an operational corridor and what remains uncertain.

The admitted inputs, produced evidence and boundary of this capability.

InputsMission and task definitions, Platform and capability evidence, Owner inventory, readiness and reservation cuts
OutputsMission review and package records, Readiness and alternative dispositions, Owner-qualified assignment proposals
BoundaryThe product does not operate sensors, weapons, networks or platform controllers.

Operational decisionDecide which joint combination changes access or denial while protecting required operational functions.
Degraded or disputed stateDegraded links, deception and unavailable domain contributions preserve multiple possible postures.
Recovery and closureAssessment updates residual denial capability and reopens the campaign branch when expected windows fail.
Authority boundaryThe product does not operate sensors, weapons, networks or platform controllers.

Rehearse joint and domain missions without allowing a convenient simulation clock or message order to rewrite operational meaning.

Typed composition, clocks, mappings, queues, checkpoints and coupled simulation
Compose access, denial, suppression, protection, sensing, sustainment and recovery across operational domains.

Lugh-E binds operational entities, scenario assumptions and owner-qualified model contracts while HARMONIA preserves the declared coupling and time semantics across the run.

A completed coupled run is not a verified forecast, an approved plan or evidence that every participating model was fit for purpose.