The Marine Corps is eleven months into Project Dynamis, and it’s worth watching if you’re anywhere near the defense C&C stack. The initiative is moving fast—seven sprints already, each one a 10- to 15-day live exercise with Marines, soldiers, and Navy assets iterating on AI-driven command and control in the field, not in a conference room. They’re running Lattice Mesh for decentralized data sharing, Palantir’s Maven Smart System for agentic workflows, and high-compute edge nodes that replace the old proprietary black boxes. Vendors and operators sit side-by-side, fix problems between sprints, and move on.
What stands out is the shift in how capability gets built. Instead of multiyear requirements documents handed off to contractors, Project Dynamis brings engineers and Marine sergeants together in operationally realistic scenarios—artillery missions, live fire, real ships—and solves data transfer problems in real time. It’s inherently joint from the start, built with the Army at Fort Carson and the Navy’s Project Overmatch team. The process isn’t perfect, but it’s honest about the tradeoff: speed and iteration over polish and predictability.
For cleared talent in this space, the implications are straightforward. The services are hiring and partnering differently now—less program-office overhead, more operator-engineer pairing, and a premium on people who can work across domains and clearance boundaries. If you’ve built or fielded C2 systems, worked Maven or mesh architectures, or led joint integration at scale, you’re seeing more inbound. The search for leaders who can run point on these programs is already tight, and it’s only getting tighter as Dynamis scales to theater events with allies.