Four Operating Domains

Land, sea, air and space impose different physics on a protective suit. They impose the same physiology on the person inside it.

WHERE THE PHYSICS DIFFER

Sea: hydrostatic compression, inert gas narcosis, and below roughly 150 metres, high-pressure nervous syndrome producing tremor and neurological instability.

Air: the inverse pressure problem. A pressure suit becomes necessary above approximately 50,000 feet, and near 62,000 feet ambient pressure falls to the vapour pressure of water at body temperature. G-loading imposes a competing requirement on the same garment.

Land: agent permeation through barriers, and thermal accumulation that can limit a mission to under an hour in encapsulating protection.

Space: vacuum, thermal flux spanning hundreds of degrees, radiation and micrometeoroid exposure.

WHERE THEY DO NOT

Cardiac output, core temperature regulation, cognitive performance under stress, hydration state, respiratory function, fatigue accumulation and situational awareness follow the same physiology in all four environments.

Sensing architecture, data schema, analytics and validation methodology transfer directly. Thresholds, alerting priorities and barrier layers are domain-specific.

CROSS-DOMAIN EFFECTS

Heat strain models validated on CBRN operators apply to divers in hot-water suits. Seal degradation observed in stratospheric testing informs inspection intervals for subsea equipment. Deployments in any domain add to the shared qualification base.

MARKET STRUCTURE

Space agencies buy on qualification evidence over long cycles. Defence buys through capability programmes, often via primes. Industrial buyers purchase on risk reduction and compliance. Subsea operators buy on incident cost avoidance and operational efficiency.

Sales motions do not transfer between them. Multi-domain operation also adds export control and security classification complexity, managed by keeping controlled elements in defined modules rather than distributed through the core architecture.

SHARED LAYERS

The CORE integration architecture, PULSE data schema and PROVE validation methodology are common across domains. Barrier and pressure layers are not.