Defense & military
C2 and mission planning
The Military skill turns Nexma into a command-and-control planning platform. It models units, sensors, targets, and engagement geometry, and gives Jax the tools to plan and rehearse missions. This is the domain where spatial reasoning, time, and rules of engagement all converge — every plan is checked against doctrine before it is briefed.
What this skill models
The ontology captures a joint operating picture with the entity types, link types, and constraints a planning staff expects.
- Entity types.
JOC(joint operations center),Unit,Sensor,Target,EngagementArc, andThreatAssessment. Each carries typed properties — echelon, sensor type and range, target priority, assessment confidence. - Link types.
CommandAuthority,SensorCoverage,EngagementArc, andUnitMovement. Movements carry route, speed band, and stealth posture. - Key constraints. Rules-of-engagement gating; sensor fusion across overlapping feeds; threat prioritization; and communication-protocol compliance.
The ontology ships the doctrinal reference data a staff relies on: the MIL-STD-2525 symbol set, standard sensor performance envelopes, and joint-doctrine echelon definitions.
What Jax can do
Jax reasons about coverage, movement, and engagement geometry because the Skill binds its capabilities to this ontology.
- Plan sensor coverage. "Lay sensor coverage that holds eyes on every named area of interest with at least two-source overlap. Respect terrain masking." Jax positions sensors to meet the overlap requirement.
- Route units under threat avoidance and stealth-posture constraints.
- Check engagement geometry — flags configurations that violate ROE before execution.
- Fuse multiple sources so high-confidence tracks surface ahead of single-source reports.
- Validate coverage, ROE gates, and comms-link continuity.
Coverage optimization and unit routing run through the Nexma MathEngine, with results written back to the world model so the common operating picture updates the moment Jax finishes.
Tip: Define the named areas of interest and the ROE before placing sensors. Coverage planning optimizes against those areas, and ROE gating constrains every engagement arc, so fixing both first keeps the plan from being re-flagged on validation.
Constraints and standards
The skill enforces the doctrine a mission plan must satisfy before it is briefed.
| Concern | Rule enforced | Standard |
|---|---|---|
| Symbology | Standard military symbols | MIL-STD-2525 |
| Engagement | ROE gating on every arc | Doctrine and ROE |
| Messaging | Interoperable message formats | NATO STANAG 2014 |
| Echelons | Standard command structure | US JP 1 |
| Coverage | Multi-source overlap on NAIs | Sensor-fusion practice |
Export the common operating picture as a slide deck or KMZ.
Out of scope today: live weapons-systems control (planning surface only), classified-network deployment (standard infrastructure unless installed in a sovereign environment), and targeting-law adjudication (rules check only, not legal review).
Where to go next
- World simulation — rehearse a plan as an agent-based scenario.
- 5G wireless — coverage and line-of-sight modeling in a civil domain.
- Skills overview — the full catalog.
- Nexma MathEngine — the optimizer behind coverage and routing.