Counter-Action Selection Under Hostility Classification
by Nick Clark | Published April 25, 2026
When an entity is classified hostile, the operating unit's response set expands. Counter-action selection runs through composite admissibility — hostility classification produces a permissive admissibility envelope rather than automatic counter-attack.
What Counter-Action Selection Specifies
When a credentialed hostility classification of an entity is admitted into the operating unit's admissibility framework, the unit's response option set expands. Defensive maneuvers, hardened postures, evasive routing, broadcast alerts to allied units, and (in defense contexts) escalation to authorized counter-measures all become admissible candidates.
Selection within the expanded envelope still runs through composite admissibility. The unit may but need not use the expanded options; the actual selection is determined by environmental observations, mission policy, capability envelope, and confidence-governed actuation evaluation.
Why 'Hostility Triggers Counter-Action' Is Structurally Wrong
The naive pattern — hostile classification triggers counter-attack — produces predictable failure modes. False-positive hostility classifications produce inappropriate responses. Operating context that makes counter-action inadvisable (collateral risk, mission priorities, escalation considerations) is not architecturally consulted before counter-action commits.
The architecture treats classification and response as separate governance decisions. Classification opens the option space. Composite admissibility evaluates each option against environmental, mission, and policy considerations. The actual response is the result of the gating, not of the classification alone.
How Expanded Admissibility Composes With Mode Selection
The hostility classification is itself a credentialed observation that the admissibility evaluator consumes. The evaluator's policy specifies the admissibility envelope expansion: hostility classification of class X expands admissibility for actions in set Y. The expanded set then enters the standard mode-selection computation alongside the rest of the request context.
The selected response may be: full counter-action commit (under unambiguous classification, clear environmental conditions, mission policy admitting), stage-gated counter-action (commitment in successive stages with intermediate verification), advisory display of contemplated counter-action (the operator ratifies before commit), or no counter-action despite the expanded envelope (admissibility fails on environmental or mission grounds).
What This Enables for Defense and Civilian Protective Response
Defense autonomy gains structural counter-action governance. Hostility classification expands the option space; mission ROE, theater conditions, and operational context govern what actually commits. The audit-grade lineage covers every counter-action with its supporting computation.
Civilian protective response — vehicle defense against road-rage attackers, drone defense in contested airspace, anti-piracy maritime response, anti-stalker personal protection — gains the same architectural primitive scaled to civilian use.
