Pentagon Taps Musk, Luckey and Gingrich for 120-Day Future Warfare Study
The U.S. Department of Defense has commissioned Project Meridian, an advisory study on the technology needed for future wars, to be led by Elon Musk, Palmer Luckey and Newt Gingrich. Defense Secretary Pete Hegseth issued the commissioning note Engadget.
The stated job is requirements work. The group will study future battlefields, identify the weapons and technologies needed for U.S. dominance, and propose ways to develop, test and field them Engadget. In Pentagon terms, that covers the full path from spotting a capability gap (a job the military needs to do but lacks the tools for) through building prototypes and running test and evaluation, to getting working systems to units. It is not basic research.
The group has 120 days to study how warfare could change in the years and decades ahead CNBC.
None of the three leads has served in the U.S. military Engadget. Gingrich is a former Speaker of the U.S. House of Representatives New York Post, and Air University granted him an honorary doctorate Engadget. Musk's SpaceXAI and Luckey's Anduril both hold existing business contracts with the Pentagon Engadget.
The broader context here is familiar to defense watchers. A 120-day window means a survey and recommendations paper, not a development program or a buying decision. Outside panels like this are often used to work around entrenched assumptions about force structure (the size and makeup of forces), systems architecture, and how long acquisition takes. They can bring in commercial habits the Pentagon adopts slowly, such as rapid software updates, autonomy stacks (the layered software that lets machines sense and act), launch and sensing infrastructure, and large-scale manufacturing. They can also miss limits that decide whether a system works outside a demo, such as interoperability (whether different systems can work together), logistics, rules of engagement, and long-term sustainment.
In my view, technologists should read this as a signals exercise, not a technology selection. The useful output will not be a list of preferred platforms. It will be how the group defines the engineering problem: which mission threads (end-to-end military tasks) it puts first, what it assumes about contested communications and PNT (positioning, navigation and timing, including GPS), how it treats human-machine teaming and levels of autonomy, and what it suggests about open architectures, test ranges, and authority to field new versions step by step. Those choices shape interface standards, data rights, and testing demands that affect both established contractors and commercial vendors.
Looking at what this means for industry, the vendor overlap is worth tracking in plain terms. When advisers hold active Pentagon contracts, clear disclosure and recusal rules matter for trust in the advice, especially around develop, test and field steps where their companies could gain. That does not prejudge the work, but procurement officials will look for how the department writes down those limits.
What this enables, if executed as described, is a short, public forcing function for long-range thinking. A 120-day study cannot settle force design. It can clarify where the department thinks commercial technology cycles are moving faster than its own requirements and fielding processes, and where it wants new options to test and scale them.
