According to a document from 04 March 2026, ATP 2-01.4 is not a landing manual. ATP 2-01.4 lays out a corps-and-below kill-chain doctrine that fuses pre-mission analysis, IPOE, collection management, target development, D3A, and BDA into one continuous staff cycle. Page 12 treats collection against EW, cyberspace, space, and information activity as equal in importance to collection against air defense and conventional targets. Appendix D then shows a targeting matrix that pairs Rivet Joint, national technical means, full-motion video, artillery, AH-64E, F-16, and F-35 against SA-15/SA-19-type air defense, reconnaissance, command, and maneuver targets. Any U.S. entry into Iran sits on top of that logic. Russian readers do not need the word Iran printed in black ink. Russian readers read the grammar and fill in the nouns.
Russian reference writing already describes U.S. multi-domain operations as a concept built to punch through layered A2/AD by synchronized action across land, sea, air, space, cyber, and the electromagnetic spectrum, with China and Russia as the original benchmark foes. Russian expert writing also treats multi-domain war as an escalatory doctrinal shift rather than a narrow technical update. Under that Russian lens, Iran becomes a likely fit for the same playbook. ATP 2-01.4 reinforces that reading because the manual centers on target systems, HVT/HPT selection, dynamic retasking, and post-strike assessment rather than on one branch or one platform.
Russian perception likely sees ATP 2-01.4 as a staff manual for systematic corridor-making. Russian officers likely read three American assumptions running through the text. First, U.S. staffs expect enough sensor fusion to find the right nodes at the right moment. Second, U.S. staffs expect enough communications stability to keep decide, detect, deliver, and assess moving in sequence. Third, U.S. staffs expect enough post-strike visibility to know what lived, what moved, and what needs restrike. Russian military culture attacks each assumption. Russian culture prizes concealment, false signatures, mobility, redundancy, and time theft. Iran already prizes the same habits. ATP 2-01.4 almost invites that defense.
Scenario 1: stand-off air and missile coercion
Russian perception sees ATP 2-01.4 as the opening script for blinding radars, shrinking air-defense coverage, tracking missile launch chains, isolating command posts, and building restrike recommendations in near-real time. Russian value to Iran fits that fight. Moscow and Tehran signed a 20-year strategic partnership in January 2025 that deepens security and defense ties yet stops short of a mutual defense clause. Space ties already run deeper than rhetoric: Russia launched Iran’s Pars-1 remote-sensing satellite in February 2024, and Russian launch support placed three more Iranian remote-sensing satellites into orbit in December 2025. Recent Reuters reporting adds a sharper edge: Western and Ukrainian sources say Russia has supplied Iran with satellite intelligence and drone know-how during the current war, while the Kremlin rejects the charge. Direct proof for each transfer remains contested, yet the pattern of cooperation no longer looks theoretical.
Russian help matters here because ATP 2-01.4 lives or dies on track quality and battle-damage clarity. ATP says BDA starts before the strike, depends on collection quality, and gains strength from more than one source. Russian aid does not need to hand Iran perfect awareness. Russian aid only needs to thicken Iranian early warning, speed target movement, and muddy post-strike truth long enough to force U.S. restrikes against emptier, cheaper, or fake positions. That is a brutal cost exchange for Washington.
Scenario 2: Gulf lodgment, island seizure, or port opening
Russian readers likely view any U.S. landing scheme as a downstream event. First comes the corridor-making phase. ATP’s own sync matrix reads like a suppressed-air-defense primer: SA-15, SA-19, MLRS, reconnaissance radars, UAVs, C2 nodes, and maneuver forces get mapped to national technical means, Rivet Joint, full-motion video, artillery, AH-64E, F-16, and F-35. Iran does not need Russian troops on a beach. Iran needs Russian help in stretching sensor-to-shooter time, hiding real emitters among false ones, compressing electronic dwell, and forcing U.S. staff cells to argue over target validity. Russian military leaders said in 2024 that Moscow stood ready to widen military and military-technical cooperation with Tehran.
A scathing point sits right in the middle of that scenario. ATP 2-01.4 treats synchronization as a virtue. Russian readers treat synchronization as a weakness once the defender gets a vote. A landing force needs timing, staging, predictable lanes, air-defense suppression, clean communications, and honest BDA. Iran, with Russian tutoring and support, needs only partial disruption. One broken track, one decoy battery, one false damage picture, one jammed relay, one survivable launcher after a strike, and the neat American sequence starts to fray.
Scenario 3: decapitation raids against HVIs, missile command nodes, or nuclear-linked sites
ATP 2-01.4 pays unusual attention to target folders, identity-linked data, HUMINT, GEOINT, MASINT, SIGINT, OSINT, biometrics, and forensics. Russian perception likely reads that as a hunt manual for leaders, network brokers, UAV controllers, and guarded facilities rather than as a generic fire-support aid. Russian help to Iran fits the defense of identity and signature: tighter compartmentation, briefer transmission windows, cleaner use of couriers and cutouts, denser false pattern-of-life trails, and faster shifts between fixed and mobile command paths. Public record does not prove a standing joint Russia-Iran cell for anti-U.S. target denial. Public record still shows widening information-security and AI/cybersecurity cooperation, including a 2021 information-security agreement that entered force in 2024 and a new AI/cybersecurity cooperation document signed in Moscow in December 2025.
Russian support in that scenario also reaches the narrative fight. ATP 2-01.4 does not stop at strike approval. ATP folds assessment, current intelligence estimates, event templates, and targeting boards into a recurring decision loop. Russian and Iranian cyber and information-security ties fit the defender’s side of that loop. Faster filtering of open reporting, faster scrub of compromised channels, and faster injection of misleading post-strike claims all impose friction on American assessment. Russian help does not need glamour. Russian help needs timing.
Scenario 4: major ground invasion
Russian officers likely sneer at any belief that ATP 2-01.4 solves the real Iran problem. Staff elegance is not combat physics. D3A looks sharp on paper because paper does not jam, lie, move, or crowd channels with civil clutter. ATP itself admits that collection assets face tradeoffs, that deceptive targets distort assessment, and that BDA reliability rests on source quality. Russian advice, Russian data, Russian cyber help, and Russian drone lessons reinforce one simple Iranian defense idea: make American precision spend itself on ambiguity. A U.S. force that needs constant synchronization grows more brittle each time the defender breaks timing, injects doubt, or survives one more cycle than expected.
Scathing bottom line
Russian perception does not flatter ATP 2-01.4. Russian perception likely treats the manual as a very American faith document: enough data, enough connectivity, enough staff discipline, enough cross-cueing, enough assessment, and the enemy system cracks on schedule. Iran, especially with Russian backing, does not need to defeat that machine outright. Iran only needs to desynchronize it. Russia complements Iran through treaties, launch support, information-security ties, AI/cyber links, military-technical cooperation, and, according to current contested reporting, direct intelligence and drone assistance. Landings come last in that picture. Kill-chain sabotage comes first. That is where Moscow sees the real fight, and that is exactly where ATP 2-01.4 shows its seams.
