FEATURED · SEVEN VIEWS OF ONE PROGRAM
One shared outcome — seven institutional customers, seven bodies of doctrine, seven fights.
CARES DEFENSE INTELLIGENCE · ANALYTICAL BRIEF
Golden Dome's hardest problem isn't the interceptors — it's the seams between the organizations that own them.
The kit exists. The sensors, the shooters, the doctrine, the command relationships — all of it exists somewhere in the Department of War, and most of it is already operational. The question that will decide whether Golden Dome delivers a defended homeland by 2028 is not can we build it. It is can we get seven institutions, each with its own customer and its own fight, to hand off cleanly across boundaries none of them designed the kit to cross.
THE THESIS · IN HIS OWN WORDS
Building Golden Dome is not a technology challenge — it is an organizational behavior and social engineering challenge. How do I get all this kit that was built for a different fight, a different customer, and never meant to work together?
— Gen. Michael A. Guetlein, Director, Golden Dome for America · Air, Space & Cyber Conference, September 14, 2026
A NAME FOR THE PROBLEM
A framework for the situation in which competent observers examine the same outcome, work from valid evidence, and reach different conclusions.
The term takes its name from Akira Kurosawa's 1950 film Rashomon, itself drawn from Ryunosuke Akutagawa's 1922 story In a Grove. Kurosawa's film presents several incompatible accounts of a single violent event without giving the audience a simple, authoritative reconstruction. The intellectual problem is not that the witnesses lie. Their accounts are filtered through perspective, memory, incentive, and incomplete information — and each account can be internally coherent while remaining incompatible with another.
In 1988, anthropologist Karl G. Heider carried the term into academic use with "The Rashomon Effect: When Ethnographers Disagree", applying it to fieldworkers who studied the same culture and drew different conclusions. Since then it has been used across law, medicine, journalism, and — increasingly — defense analysis.
For a system-of-systems program like Golden Dome, the framework carries a specific practical implication: the analyst's task is not to select the most persuasive narrative, but to build the model that explains why each organization sees what it sees. Only after that model is built can the seams between them be designed.
TWO WAYS TO ASK THE QUESTION
The same set of stakeholder positions can be read as a debate to be adjudicated — or as a system to be reconstructed.
TRADITIONAL FRAMING
"Which service owns Golden Dome?"
Assumes there is a single correct answer to a single organizational question. Produces a debate over authority, budgets, and lanes-in-the-road. Institutional equities are treated as noise to be overcome. The winning stakeholder gets the mission; the others adjust. This is how most Pentagon integration debates are structured, and it is why they take decades.
RASHOMON FRAMING
"What does each service already see, control, and measure — and where do the seams fall?"
Assumes each stakeholder is accurately describing the portion of the system it can observe from its position. Institutional equities are treated as signal — they reveal the shape of the causal system. The analyst's job is to map observational positions to the causal chain, identify the seams, and design the hand-offs. Authority follows the seam design, not the other way around.
SEVEN STAKEHOLDERS · SEVEN VANTAGE POINTS
Each institution brings existing kit that was procured for a different fight and a different customer. Each is right about the portion of the system it can see. None sees the whole.
01 · SPACE LAYER
US Space Force · SSC · SDA
KIT THEY BRING
SBIRS & Next-Gen OPIR, HBTSS, SDA proliferated tracking layer, space-based interceptor prototypes (12 primes, $3.2B in OTAs), and the C2 architecture Guetlein calls the program's "secret sauce."
WHAT THEY SEE CLEARLY
Global persistent tracking. Boost-phase intercept as the cleanest engagement. Space as the top of the kill chain.
THEIR INSTITUTIONAL CUSTOMER
A new service still building doctrine. Space Force force presentation, USSPACECOM, plus a novel homeland-defense role that didn't exist five years ago.
THE SEAM
Handing tracks and fire-control quality data down to MDA and the services. C2 authority in a joint architecture. Owning the sensor picture without owning most of the shooters.
02 · STRATEGIC MISSILE DEFENSE
Missile Defense Agency · MDA
KIT THEY BRING
GMD/GBI legacy, Next-Generation Interceptor (NGI), SM-3 Blk IIA, Aegis BMD architecture, SBX and TPY-2 sensors, HBTSS. Two decades of integrated BMD development.
WHAT THEY SEE CLEARLY
The strategic BMD mission end-to-end. How to make sensors, discrimination, and interceptors work as a system against a small raid.
THEIR INSTITUTIONAL CUSTOMER
Historically STRATCOM and NORTHCOM; more recently a menu of COCOMs plus the services who employ MDA-fielded kit. A traditional integrator now sharing that role with the Golden Dome czar.
THE SEAM
Handoffs of MDA-developed kit to service operators. Scaling from limited raids to Golden Dome's peer-threat volume. Reconciling legacy midcourse doctrine with boost-phase space-based intercept.
03 · TERMINAL & AIR DEFENSE
US Army · SMDC · Air Defense Artillery
KIT THEY BRING
Patriot (PAC-3), THAAD, LTAMDS radar, IBCS, IFPC Inc 2, M-SHORAD, NASAMS integration, Coyote counter-UAS — plus the first air-defense unit formally assigned to the Golden Dome mission (August 2026).
WHAT THEY SEE CLEARLY
Terminal defense. Layered engagement against leakers. Boots-on-the-ground operating tempo against cruise and UAS threats.
THEIR INSTITUTIONAL CUSTOMER
Combatant commanders (NORTHCOM for homeland; theater CCs for expeditionary). Army leadership for force structure and readiness.
THE SEAM
Fire control cueing from space and upper-tier sensors. Doctrine for engaging leakers past higher tiers. Battle management authority for time-critical engagements when the sensor and shooter belong to different services.
04 · SEA-BASED BMD
US Navy · Aegis BMD community
KIT THEY BRING
Aegis Baseline 9 & 10, SM-3 Blk IIA, SM-6 Dual II, Aegis Ashore infrastructure, DDG-51 hulls fitted for BMD. Mobile interceptor positioning that fixed-site defenders don't have.
WHAT THEY SEE CLEARLY
Sea-based layered defense. How to position interceptors under a threat axis. Integration of BMD into fleet air-defense doctrine.
THEIR INSTITUTIONAL CUSTOMER
Fleet commanders and theater combatant commands. The Navy's mission set is global power projection, not standing homeland defense.
THE SEAM
Homeland defense is not the Navy's natural mission. Golden Dome could pull DDGs onto persistent homeland tasking against Navy force-employment priorities. Integration of sea-based fires into a land-anchored kill chain.
05 · AEROSPACE WARNING & CONTROL
US Air Force · NORAD (bi-national)
KIT THEY BRING
NORAD command architecture, ground-based radar networks, E-3 AWACS, fighter alert, F-35 as networked sensor node. Decades of aerospace warning doctrine — the pre-existing homeland air-defense authority.
WHAT THEY SEE CLEARLY
The atmospheric domain. Manned-interceptor tradition. The bi-national warning relationship with Canada. Alert posture and quick-reaction procedures.
THEIR INSTITUTIONAL CUSTOMER
NORAD/NORTHCOM (dual-hat commander). Canada, through NORAD. Air Force leadership for force presentation.
THE SEAM
Golden Dome bolts new space-based capabilities onto NORAD's existing warning mission without replacing the command relationship. Cross-domain alerting authority. Canadian equities in an increasingly space-centric architecture.
06 · OPERATIONAL COMMAND
US Northern Command · NORTHCOM
KIT THEY BRING
Operational authority for homeland defense. Command relationships across all services. Engagement authority delegation. The GCC role for the continental United States.
WHAT THEY SEE CLEARLY
The joint fight at employment level. Defended-asset requirements. What "defended homeland" actually means in a time-critical engagement.
THEIR INSTITUTIONAL CUSTOMER
The Secretary of Defense and the President. The American homeland and its people.
THE SEAM
Owns the mission but not the kit. Depends on service force presentation and joint battle management. Must exercise fire-control authority across sensors and shooters owned by four services and one agency, on decision timelines measured in minutes.
07 · POLICY & ACQUISITION
OSD · A&S & the czar
KIT THEY BRING
Policy authority. Program budget execution oversight. The novel construct of the Golden Dome director role — a service-independent czar (Guetlein) with program authority but no service kit. Requirements approval now sits under the Joint Force Requirements Process (JFRP, authoritative Jan 15, 2026), which replaced JCIDS and returned validation of service-level requirements to the services themselves.
WHAT THEY SEE CLEARLY
The program of record. Cost, schedule, performance across the joint architecture. Institutional equities as they compete for the same appropriated dollar. Portfolio-level integration through the JROC's new focus on Joint Force Design, Joint Capability Integration, and Combatant Command requirements.
THEIR INSTITUTIONAL CUSTOMER
SecDef, Congress, OMB. The service secretaries who both cooperate with and compete against the czar's authority.
THE SEAM
Program authority (czar) vs institutional authority (services). The 2025–2026 acquisition reform decentralized requirements validation to the services just as Golden Dome demands unprecedented integration across them — a structural tension the czar was hired into, not one he created.
THE OPERATIONAL CAUSAL CHAIN
Detection to reengagement is eight steps. In a Golden Dome architecture no single organization owns three in a row — and the timeline from cue to kill is measured in minutes.
A simplified single-engagement chain. In a real Golden Dome architecture, dozens of these chains run in parallel — some concluding in seconds — while battle management, sensor fusion, and command authorities operate concurrently across the same seven institutions.
FOUR PRACTICAL TESTS
Four questions the Golden Dome program office — or any analyst studying the integration challenge — can apply to each institutional boundary.
01
Common outcome.
Do all seven stakeholders agree on what "defended homeland" means? Whose defended-asset list is authoritative — NORTHCOM's, OSD's, or the individual services'? If organizations are measuring different outcomes, no amount of C2 integration will make them converge.
02
Standardize definitions.
Does cued mean the same thing to Space Force sensors as to an Army fire control node? Is a leaker a shared engagement, a service failure, or a re-engagement trigger? Common vocabulary is not glamorous. It is the difference between a joint architecture and a stack of stovepiped ones.
03
Identify observational position.
Map what each stakeholder can see, measure, and control. Space Force sees the boost phase; Army sees the terminal engagement; NORTHCOM sees the whole fight but owns no interceptors. Expertise creates depth in one portion of the chain but rarely breadth across it. Design around depth; engineer for breadth.
04
Define falsification tests.
What evidence would prove a seam is broken? A cued track that isn't picked up. A weapon assigned to a shooter that can't range the intercept. A kill assessment that returns after the reengagement window has closed. The Rashomon framework is not an excuse to conclude that everyone is right — it is a discipline for identifying which hand-offs actually work.
IMPLICATIONS · FOR THE GOLDEN DOME CZAR
Gen. Guetlein's role is structurally novel. He runs a program that touches all four services and at least two combatant commands, but he does not command any of the kit. Every interceptor, every radar, every C2 node belongs to a service or an agency that reports elsewhere. The construct that gives him program authority also denies him service authority. That is not a design flaw — it is the constraint the position was created inside of.
The constraint tightened further while Guetlein was standing up the program office. On August 20, 2025, Secretary Hegseth and Deputy Secretary Feinberg signed a memo that disestablished the Joint Capabilities Integration and Development System (JCIDS) that had governed joint requirements validation since 2003. On January 15, 2026, CJCSM 5123.01 activated the Joint Force Requirements Process (JFRP) in its place. Under the new construct, the Joint Requirements Oversight Council no longer validates service-level requirements. Services now validate their own — with Program Acquisition Executives leading portfolio-level integration across program offices — while the JROC reorients to Joint Force Design, Joint Capability Integration, and Combatant Command requirements through the lens of Joint Operational Problems. Requirements authority moved outward to the services in the same eighteen months that Golden Dome moved integration inward toward one czar.
What the Rashomon lens says about that constraint is useful, not fatal. The seven institutional views are not obstacles to route around. They are the source data. Each service can see what it can see because of a long history of building the kit its customer asked for. The kit was not built for this fight. It was built for a different fight — Guetlein's own words. The task is not to relitigate that history. The task is to design the hand-offs the historical kit never anticipated — under a joint-requirements regime that just handed each service more autonomy, not less.
The four tests above give an integrator's checklist. But the more general point is this: the Rashomon framework changes what a well-run program office measures. Instead of tracking whether each service is delivering its piece on cost and schedule — the traditional acquisition metric — a Rashomon-informed program office tracks whether the seams between the services are surviving realistic operational stress. That is a harder metric to build, and a harder one to defend to Congress. It is also the one that determines whether the summer of 2028 operational capability that Guetlein has promised will be an integrated capability or a stack of coincident ones.
SOURCES & DOCUMENTATION
Twelve public references — primary quotes, foundational academic literature, current program reporting, and the joint-requirements reform that reshapes the czar's authority.