System 03 / 05Command + Control

Coordinate

COMPOSITION

Turn distributed systems into one operating picture.

Mission role

The mission coordination and control layer.

Current phase

Active software development

System intent

Built for its layer. Engineered for the whole mission.

A complete defense architecture needs more than connected components. It needs a mission layer that preserves context from first detection through final action. COMPOSITION is being built to fuse tracks, organize decisions, keep the operator in command, and coordinate the systems assigned to the engagement.

COMPOSITION turns sensor data into a common operating picture, connects operators with distributed systems, and coordinates the path from track formation to interceptor launch and mission oversight.

Public capability profile

The responsibilities that define COMPOSITION.

01

Common operating picture

Organizes distributed sensor inputs into a coherent view of the defended environment and the tracks inside it.

02

Track management

Maintains mission context as tracks are formed, updated, evaluated, and handed between connected systems.

03

Operator authority

Keeps human judgment and mission oversight at the center of system coordination and engagement control.

04

System orchestration

Coordinates sensors, MOUND nodes, TANKARD launch systems, and THORNWALL interceptors through defined interfaces.

Controlled public release

Not shown
by design.

Configuration imagery is withheld while validation and release review continue.

Public system profile

System layerMission command + coordination
Mission roleBuild the picture and coordinate action
Primary interfaceSensors, operators, and effectors
Development focusGuidance, C2, and mission software

Release boundary

Operator interfaces, software architecture, data models, autonomy logic, and implementation details are withheld from public release.

The architecture

One system is never the whole mission.