The network is the weapon: The missing link in the military’s AI revolution

The Navy announced recently that it is creating a new Robotic and Autonomous Systems Warfighting Development Center at Joint Expeditionary Base Little Creek-Fort Story. This month, the War Department added ChatGPT and Grok to GenAI.mil alongside Gemini. The Defense Information Systems Agency’s fiscal 2026 technology watchlist, meanwhile, places agentic AI and AI-augmented software engineering in proof-of-concept work, network detection and response in pilot, and AIOps among technologies already in deployment.Those are different initiatives, but they share one dependency: The network has to be ready enough to carry the intelligence, permissions, data, and recovery paths that make artificial intelligence useful in the first place.That is why network readiness is becoming a warfighting discipline rather than an IT background function. DISA’s own strategy already points in this direction. Its priorities include a resilient and redundant defense information backbone, hybrid cloud, zero-trust tools, a consolidated network, data management, and the deliberate reduction of technical debt. The agency’s ReForged program is also modernizing legacy warfighter applications incrementally so that long-standing codebases can move toward cloud and AI capabilities without interrupting ongoing missions.The important next step is to make the readiness of those digital dependencies as visible as the readiness of the platform they support.A fighter, ship, or autonomous vehicle may be mechanically available while the digital services around it are degraded. Maintenance scheduling, identity services, mission data, cloud access, logistics, communications, and software update systems can all affect what the platform can actually do. The useful readiness question is therefore not simply whether the network is ‘up.’ It is what mission functions the network can still support under the conditions that matter.That question can be made concrete.First, every consequential mission should have a dependency map. The map does not need to expose classified architecture broadly. It needs to give authorized operators a reliable answer to a smaller set of questions: which digital services the mission depends on, which dependencies are shared, what the fallback preserves, and which single failure could affect several supposedly separate paths.AI makes this more important because automation can connect weaknesses and dependencies at machine speed. A defensive agent may correctly identify suspicious activity and still face a difficult operational choice if isolating one service also interrupts something the mission needs. The solution is not to hold back automated defense. It is to give that automation a mission-aware picture of the system it is protecting.Second, network changes should have a safe-change envelope.Military networks cannot be maintained like ordinary office laptops. A configuration change, identity-policy update, or software patch can be technically correct while arriving at the wrong operational moment. The department already has the right engineering instinct in its modernization programs: test, stage, migrate incrementally, and preserve ongoing operations.That principle should become explicit for AI-enabled cyber defense. Before an automated defender receives authority to change a consequential configuration, the organization should know which mission functions might be affected, which changes are reversible, what rollback path exists, and when human approval is required. Digital twins, representative test environments, and shadow deployment can make those consequences visible before the operational network has to absorb them.Third, recovery should be treated as evidence, not merely as connectivity.A service coming back online does not necessarily mean every permission that depended on it should return at once. If a communications path, identity service, or data feed was restricted during an incident, restoration can proceed in steps. Read access may return before write access. Advisory use may return before autonomous execution. A higher-risk permission can remain restricted until the specific condition that justified the restriction has been retested.That is particularly relevant as the department expands the use of agents. DISA’s own technology pipeline now treats agentic AI as an active area of proof-of-concept work. The strongest architecture for those systems will not be one in which an agent is either fully trusted or fully disabled. It will be one in which authority can contract and recover according to the evidence available.The department has already made substantial progress on the security foundation. GAO’s 2025 review of 24 major War Department IT business programs found that 22 reported approved cybersecurity strategies and 20 reported implementing zero-trust architecture. The point is not that a checklist establishes readiness. It is that the department is already moving a broad portfolio toward a common model of identity, access, and continuous verification.Network readiness can build on that foundation rather than create another bureaucracy.A practical readiness record for each mission-critical digital service could answer four questions: What mission function does it support? What degraded mode remains available if it is restricted? What change can be made safely during operations? What evidence is required before a restricted capability returns?Those fields would give commanders something more useful than a patch count. They would show what the force can still accomplish.This also helps reconcile modernization and sustainment. New AI tools, autonomous systems, and cloud capabilities do not compete conceptually with maintenance. They make disciplined sustainment more valuable because more operational capability is moving through software, data, and networks. The faster the force modernizes, the more valuable it becomes to know the condition of the digital foundation under that modernization.The War Department is already moving in that direction. The Navy is creating institutions for robotic and autonomous warfighting. GenAI.mil is expanding access to frontier models. DISA is testing agentic AI, deploying AIOps, modernizing legacy applications, and building toward a more resilient network.AMERICA’S AI GUARDRAILS ARE SO BROKEN THEY’RE DRIVING US STRAIGHT TO CHINAThe opportunity now is to connect those efforts with one operational idea: The network behind the weapon is part of the weapon’s readiness.The strongest AI-enabled force will not be the one that assumes its digital systems never fail. It will be the one that can recognize degradation, narrow authority, keep the essential mission moving, repair what changed, and restore capability with evidence.Burak Oktenli is a graduate student in applied intelligence at Georgetown University and an independent researcher focused on trustworthy AI, cybersecurity, autonomous systems, and emerging computing architectures. His work centers on verification, provenance, runtime authority, space governance, and resilient system design for AI-enabled technologies.