ReAct - Khan BMS Battlefield Management System
ReAct — ReAct Agent Pattern — is one of the unglamorous primitives modern BMS lives or dies on. Here is how Khan BMS engineers it.
ReAct is the kind of standard that looks finished on paper and turns out to be a set of unanswered design questions in practice. Anyone who tells you otherwise has not had to ship it.
Inside Khan BMS, ReAct is exposed to mission planners as a capability bundle rather than a vendor SDK. The planner composes effects out of ReAct-derived primitives; the integration path for new hardware is a manifest, not a code branch.
ReAct is anchored at the Arban — ten nodes under one tactical leader. Small enough to reason about by hand, large enough to absorb the loss of a node without re-planning. Authority for ReAct is bounded at this tier; nothing the Arban does can poison its parent.
If ReAct matters to your formation, the integration question is not whether to support it. It is how cleanly the rest of your stack survives when it is the only thing still working.