Air Combat Mission Replanning #2: Stack Spike & Doctrine
This is the second installment in the engineering series on the Air Combat Dynamic Mission Replanning System (SDC). In the previous episode, Air Combat Mission Replanning #1: Architecture & KLM Analysis, we established the multi-tier distributed architecture, overcame the CPython 14.5s latency barrier, optimized GPU memory to 0.80 GB, and numerically validated the F-16C fuel integration model via 4th-order Runge-Kutta (RK4).
This article documents the engineering facts from October 23, 2026, when we conducted Technology Stack Spike (a) to de-risk core feasibility before full distributed prototype implementation. We present the verification of 6 quantitative pass criteria, along with the formulation of Operational Threat Situations (T1~T12) and System Bottleneck Hypotheses (H1~H9) derived from official doctrine analysis.
Figure 1: Architectural overview of Stack Spike (a) verification metrics and the ROK 2022 Defense White Paper-grounded T1~T12 operational threat matrix.