ATLAS FIRES — STAGE 3 MISSION CONSOLE

OPS HUB COP / ALERTS KILL WEB
JTIC2S stage-3 lane Checking APIs... Ready: select system + munition + charge, generate mission, then execute kill-chain gates.
Execution flow: Target + firing unit selection -> Generate mission -> Table-backed weaponeering -> CDE bind -> NOMINATE -> IN_DEVELOPMENT -> READY_FOR_EXECUTION -> SENT_FOR_EXECUTION -> SHOT/SPLASH/BDA completion with full audit trail.
0
missions
0
pending
0
approved / in effect
0
danger close

1 - Mission setup

Firing configuration (published-data only)
Release/CDE authority

2 - Mission output

no mission PENDING 
Generate a mission to view CFF, AFATDS, VMF, CoT, and validated weaponeering references.

3 - Published references and JTIC2S readiness

Selected firing combo references
Loading references...
JTIC2S integration posture
Loading JTIC2S status...

4 - Recent fire missions with kill-chain gates

Loading...

5 - COP engagements (synced)

Loading...

6 - Weaponeering records (table-verified)

Loading weaponeering records...
PRESENCE ✓
⚠ SANDBOX / TRAINING MODE — Live read-only data. Write commands are inhibited (train as you fight, missile button safed).