How does DEPLOY apply verified-vs-claimed discipline to autonomous space missions?

Why space demands the sharpest verification

Space hardware ships with autonomy as a primary feature, but the sector attracts hype disproportionate to its verification depth. A lunar lander demo reel, a render of a future satellite-servicing platform, or a keynote promise travels farther than a mission-operations log. The verified-vs-claimed framework exists to close that gap.

The framework reads space missions across three axes:

1. Mission outcome: success, partial success, failure, or pre-flight. The public record is unusually complete because regulators (NASA, FAA-AST, ESA, JAXA, CNSA) and customers (commercial payload buyers, defense agencies) are highly disclosure-oriented.
2. Autonomy depth: autonomous descent and landing vs operator-supervised mission execution vs crew-in-the-loop. The framework distinguishes what executed without human intervention from what required ground control or astronaut oversight.
3. Source quality: primary-source telemetry and customer acceptance documentation vs company press releases vs third-party media coverage. The 9-tier source-quality rubric applies unchanged.

---

Worked examples from the 2023-2025 lunar landing wave

Firefly Blue Ghost Mission 1 — verified success. The lander touched down in Mare Crisium on March 2, 2025, operated for the planned lunar day, and delivered ten NASA CLPS payloads. Verification anchor: NASA's CLPS Mission 1 acceptance documentation and Firefly's published telemetry record. No ambiguity; the mission outcome is verified at primary-source depth. See the Blue Ghost entity anchor.

Intuitive Machines IM-1 and IM-2 — verified tipped. Both missions reached the lunar surface but tipped on landing, compromising payload deployment and mission duration. Verification anchor: primary-source images released by Intuitive Machines showing the lander orientation. The maker's "successful landing" framing is technically true—the vehicle reached the surface—but the framework records the outcome as tipped because the primary-source images show the mission objective was not fully achieved. The same discipline applies to IM-2 (March 2025), producing the same tipped classification. See the Intuitive Machines entity anchor.

ispace HAKUTO-R Mission 1 — verified failure. The lander lost communication during descent in April 2023; telemetry analysis confirmed it crashed. Verification anchor: ispace's own post-mission telemetry report plus JAXA corroboration. The framework does not soften the outcome because the mission carried commercial and scientific payloads; failure is a signal, not a verdict on the company's future. See the ispace entity anchor.

Astrobotic Peregrine — verified never-landed. A propellant leak shortly after launch prevented the January 2024 mission from attempting lunar descent. Verification anchor: Astrobotic's public mission statement plus published telemetry showing the anomaly. The framework records the outcome as "never attempted landing" rather than "failure" because the mission never reached the landing phase; precision matters. See the Astrobotic Peregrine entity anchor.

---

Orbital servicing: success and honest absence

Northrop Grumman SpaceLogistics MEV-1 and MEV-2 — verified commercial success. Both missions successfully docked with Intelsat satellites in 2020 and 2021 and extended operational life by years. Verification anchor: Intelsat customer-of-record statements plus published mission telemetry. These are the cohort's canonical verified commercial successes at customer-of-record depth. See the Northrop Grumman MEV entity anchor.

Astroscale ELSA-d — verified capture aborted. The 2021 mission demonstrated rendezvous but the magnetic capture demonstration was aborted. Verification anchor: Astroscale's own mission statement. The framework records the outcome as "capture aborted" rather than "partial success" because the primary objective (demonstrating capture) did not execute. Astroscale ADRAS-J (2024-2025) later completed close-proximity inspection without capture attempt, operating at a different verification tier. See the Astroscale entity anchor.

---

Why honest mission records are the content

Space missions are expensive, visible, and politically significant. The temptation to reframe a tipped lander as a "successful landing" or a pre-flight render as a "demonstrated capability" is constant. The verified-vs-claimed framework treats each mission outcome as editorial substance because readers—engineers, investors, policymakers, and the public—make decisions based on an honest map of what has actually been demonstrated.

Honest absence is also a signal. Starfish Space Otter and ClearSpace ClearSpace-1 are pre-flight as of mid-2026. The framework records them as pending verification, not as implied future successes. That honest absence is itself a trust signal: the map tells you where the blank spaces are.

For the canonical framework reference, see how DEPLOY verifies. For the source-quality rubric applied to mission records, see the 9-tier source-quality rubric. For per-mission institutional depth, see the registry's space category.