The mission stack is not a separate product
Most vendors selling into this market ship a defense edition, a fork, a hardened variant, or a partnership with somebody who has one. The gap between that edition and the commercial product is where the governance model diverges, and it never converges again.
System9 runs the same nine services and the same enterprise foundation in every deployment. Defense capability is a set of tiers unlocked by cell profile and licence, activating independently, so a contractor running enterprise analytics can take advanced detection without battlefield features, and a tactical unit can take communications and mission operations without cyber capability.
That is convergence by architecture rather than by integration, and it is the difference between one governance model and two.
What the tiers unlock
Tactical communications
Governed tactical networking and spectrum management with a software fallback physical layer. The reachable slice: the tactical control plane, mesh formation with self-healing multi-band routing, disruption-tolerant networking with custody transfer and contact-graph routing for links that are intermittent rather than merely slow, and one complete protected link. The wider spectrum and waveform families, spectrum monitoring, modulation and protocol identification, direction finding and geolocation, jamming detection, are built and not yet reached from production, and are described as such rather than as a full radio-frequency suite.
Battlefield operations
The reachable set, named precisely: fires and targeting with call-for-fire formatting, ballistic and engagement-zone solutions, weapon-target pairing, rules-of-engagement checks and human authorisation; counter-battery; force tracking with composite tracks and filtering with fratricide prevention; radar ingest; ammunition status; orbital tracking.
Cyber operations, governed
Ten subsystems from discovery through reporting, and the part to lead with is the engagement core: rules of engagement, an authorization workflow, an approval quorum, scope management and an engagement audit. Active discovery and exploitation are simulation and modelling rather than live testing, which is what makes running any of this inside a customer's production estate defensible.
Counter-threat operations
Counter-botnet with command-and-control analysis, sinkholing and a disruption coordinator; counter-influence with actor profiling, communication analysis and narrative tracking; and authorised fire missions with target development, authorization, mission management and battle-damage assessment.
The tactical crypto posture
An offline certificate authority and pre-provisioned material so a cut-off cell still issues and validates, session governance with hash-anchored auditing, and destruction of key material for the capture scenario, where the question is not whether an adversary gets the hardware but what they get with it.
The edge, in contested conditions
A hardware-bound device identity that cannot be spoofed even if the gateway is compromised, a delegation the platform can revoke within one round-trip, a schema-pinned wire that defeats downgrade, and a hash-chained journal that keeps recording with no link. Where there is no network at all, the device writes a signed bundle for an operator to carry rather than pretending to deliver.
What a programme office should test first
Not the feature list. Cut the link and watch what continues: whether the cell starts, whether it licenses itself, whether policy is still enforced, whether inference still runs, and whether the estate view still answers with children unreachable.
Then reconnect, and ask what it can prove about the interval, which entries accumulated, which are chained, and what a verifier can check without trusting the system that produced them.
Defense capability tiers are described here at the reachable slice, deliberately. A platform that names its boundary is one whose other claims you can price.