The next cislunar tracking race may not start with a new telescope. It may start inside software that can turn scattered observations into a cleaner operating picture before an operator loses the thread. That is why the Space Force's September move to prototype better data fusion for space domain awareness deserves attention beyond Earth orbit. Breaking Defense reported that Mission Delta 2 is pursuing software to automate the integration of commercial and military tracking data. In the same policy window, Defense One reported senior military leaders using unusually direct language about contested operations extending from the seabed to cislunar space . AI-generated image A cislunar operating picture depends on software that can reconcile many sensor feeds, not just one exquisite instrument. The News Is About Data Plumbing The immediate procurement story is modest by space-program standards. Mission Delta 2, the Space Force organization responsible for space domain awareness, wants to prototype software that can bring commercial and military tracking sources together more quickly. The goal is faster, more accurate awareness for space-control operations, with less manual work standing between a sensor hit and an operational judgment. That sounds bureaucratic until it is put in cislunar context. Near Earth, the United States has decades of habits, catalogs, radars, optical telescopes, operator procedures, and orbital regimes that are at least familiar. Beyond geosynchronous orbit, the geometry changes. Objects are dimmer. Observation windows are less forgiving. Motion is harder to predict with old mental models. A spacecraft operating on a lunar transfer, near an Earth-Moon Lagrange region, or around the Moon does not behave like a satellite in a tidy low Earth orbit shell. The result is a tracking problem that is too large for a single sensor family. Ground telescopes, military systems, allied data, commercial catalogs, ephemeris feeds, owner-operator updates, lunar mission telemetry, and future dedicated cislunar sensors all have to feed a common workflow. The hard part is not collecting more dots. It is deciding which dots belong together fast enough to matter. Why This Matters A cislunar catalog will be judged by continuity. If a spacecraft is seen once near the Moon and then lost in the data stack, the sensor technically worked but the mission picture failed. 2 Space Defense Squadrons tied to the expanding awareness mission 2026 Year cislunar coordination became a sharper Space Force issue 384K Kilometers from Earth to the Moon, roughly Many Sensor feeds that must become one operational picture Cislunar Awareness Has a Custody Problem Space domain awareness is often described as finding and tracking objects. Cislunar awareness is more specific: keep custody when the object leaves comfortable orbital neighborhoods. Custody means the system can connect observation to observation, update the expected path, flag uncertainty, and hand the object between sensors or organizations without creating a mystery every few hours. That is a software and standards burden as much as a hardware burden. A new telescope can widen coverage, but it still produces measurements that need to be weighted, compared, filtered, and turned into a track. Commercial providers may describe an object with one level of confidence. A government system may use another. A mission operator may know planned maneuvers that never appear in a public catalog. An allied sensor may add a useful angle but arrive with different metadata. The farther the operating area reaches from Earth, the more expensive confusion becomes. A missed maneuver in low Earth orbit may be recoverable with frequent passes and dense tracking. Near the Moon, gaps can grow. A delayed update can affect conjunction screening, inspection planning, communications pointing, defensive posture, and the basic question of whether an unknown object is benign, malfunctioning, or intentionally hard to characterize. AI-generated image Tracking grows harder as spacecraft move through weakly observed paths between Earth, GEO, Lagrange regions, and lunar orbit. The Catalog Will Need More Than Positions A useful cislunar catalog needs position estimates, uncertainty bounds, maneuver history, ownership clues, planned mission phases, sensor provenance, and alert logic. It also needs a way to preserve confidence when sources disagree. That is where automated fusion matters. Human analysts still make judgments, but they need software that reduces noise before a shift becomes a scavenger hunt through disconnected feeds. For the lunar economy, the same problem appears in non-military form. Commercial landers, relays, transfer stages, inspection vehicles, and surface support spacecraft will all need basic traffic awareness. A lender, insurer, payload customer, or mission partner will not want vague answers about where critical hardware is. The defense stack and the commercial stack are likely to evolve together because both need track quality, timeliness, and trusted handoffs. Why September's Signals Line Up The timing matters because September brought several related signals. Defense One quoted senior leaders placing cislunar space inside the future contested environment. The same reporting described the 18th and 19th Space Defense Squadrons sharing the cislunar mission as the operating area expands. Breaking Defense then reported the Mission Delta 2 software-prototype push, with a focus on fusing commercial and military tracking data. Taken alone, any one of those developments could sound incremental. Together, they show a shift from speeches about the Moon to operating mechanics. If cislunar space is part of the military planning map, then the United States needs a repeatable way to know what is there. If commercial providers are part of the sensor base, then their data must enter government workflows without months of bespoke integration. If the same region will host Artemis, commercial landers, scientific missions, and potential adversary spacecraft, then the catalog cannot wait for a crisis to mature. Layer Near-Term Need Cislunar Consequence Sensors More observations beyond GEO Fewer blind periods on lunar transfers and high-altitude routes Data fusion Automated correlation across commercial and military feeds Better custody when objects are faint, slow, or maneuvering Standards Shared metadata, confidence measures, and alert formats Less friction between civil, defense, allied, and commercial operators Operations Faster analyst workflows and clearer tasking Quicker decisions during anomalies, conjunctions, and inspections Commercial Data Is No Longer Optional The Space Force already leans on commercial space-tracking providers closer to Earth. Cislunar operations make that dependence more important, not less. Commercial operators can place sensors in useful locations, process optical data at scale, and offer specialized analytics faster than a traditional government-only architecture can be built from scratch. That does not mean commercial data can simply be pasted into a military picture. Feeds need validation. Contracts need service levels. Data rights need to be clear. Latency has to be measured. False correlations must be caught. Cybersecurity matters because the catalog itself becomes operational infrastructure. A bad track can waste attention. A manipulated track could be worse. The cislunar version of this challenge will likely include civil and scientific data too. Artemis missions, Gateway operations, CLPS landers, lunar relays, and international spacecraft will generate telemetry and ephemeris information that can improve situational awareness if shared properly. The question is whether the architecture can accept useful data without turning every mission into a custom integration project. What Good Fusion Has To Do • Correlate: Decide whether observations from different sensors describe the same object. • Weight: Treat ea