Lockheed Martin JADC2 Programs Lack Cross-Service Mesh
by Nick Clark | Published April 25, 2026
Lockheed Martin operates major JADC2 program contracts across services. Cross-service composition is implementation-by-implementation; governed spatial mesh provides the cross-service substrate that JADC2's stated ambition requires.
Lockheed JADC2 Reality
Lockheed contracts span multiple JADC2 efforts (F-35 sensor fusion, Aegis AWS evolution, ADVENT ABMS, Skunk Works classified work). Each program produces operational coherence within program; cross-program composition is structurally underspecified.
JADC2 Cross-Service Gap
JADC2 ambition requires cross-service composition. Current architecture handles service-internal operations effectively but produces friction at service boundaries.
Mesh as Cross-Service Substrate
Each program contributes credentialed observations; cross-service operations admit through declared federation; coalition operations admit through declared coalition federation.
Lockheed Position
Lockheed gains cross-service architectural alignment. JADC2 ambition gains structural support. Coalition operations gain structural support.
