GOAP - Khan BMS Battlefield Management System
What GOAP (Goal-Oriented Action Planning) actually does on a contested loyal wingman link, and why Khan BMS treats it as a formation-level primitive instead of a vendor integration.
For the record: GOAP stands for Goal-Oriented Action Planning. Lightweight STRIPS-style planner that chains actions by precondition and effect. GOAP represents the world as facts, actions as preconditions and effects, and goals as desired fact sets, then searches for an action sequence achieving the goal. GOAP is a popular middle ground between FSMs and full HTN planners for tactical autonomy because it tolerates dynamic worlds and supports re-planning under change.
Ask any signaller who has worked through Russian EW and they will tell you what GOAP actually does for a living. The textbook calls it Goal-Oriented Action Planning. The fight calls it the difference between a tasking that lands and one that times out.
At the Minghan tier — one thousand nodes — GOAP stops being a tactical convenience and becomes an operational capability. A Minghan commander issues GOAP-shaped intent and lets the ten subordinate Zuuns decompose it; the human never sees a thousand individual streams.
For loyal wingman workloads we found the right move was to make GOAP a first-class verb in the intent grammar. Operators don't configure GOAP; they invoke it, and the runtime decomposes it down the hierarchy.
GOAP is one of perhaps a dozen primitives that decide whether a modern force can fight through denial. Khan BMS is built on the premise that all of them deserve the same treatment.