Data provenance & verification

Methodology

MoonOpps tracks lunar missions from 2026 to 2035 and the federal CLPS contract money behind them. This page states exactly where each kind of data comes from, how a recipient's identity is verified, and the rules that keep the numbers honest — including what the site deliberately does not claim. For the catalog's confidence labels see About; for the underlying references see Sources.

Mission & launch data

The mission catalog — missions, actors, payloads, regions, and the source links behind them — is a normalized public-data set, generated at build time. Each record carries a confidence label (High / Medium / Low, defined on About) and links to the public sources it rests on, indexed under Sources. Programmatic records — a contract, payload slot, or planning milestone — are not the same as a scheduled launch.

Federal funding data

Funding figures are federal lunar contract awards compiled from public U.S. government spending records — primarily NASA CLPS robotic-delivery task orders, plus the Blue Origin Blue Moon Mark 2 human-landing-system (HLS) award, which is tracked and shown separately from the CLPS total. Every dollar is paired with an amount type — announced, current, obligated, potential, or an IDIQ ceiling — and an as-of date. These are reported award values, not audited spend. The as-of date is frequently the date the figure was crosswalked from public records, not the original announcement date, and a given line figure may be unverified at the contract level; where that is so it is presented as reported, not confirmed.

Recipient verification — SAM.gov by UEI

A recipient is marked SAM-verified only when its organization identity has been confirmed against the U.S. government's entity registry (SAM.gov) by Unique Entity ID (UEI), and that confirmation recorded in our data — with the registry's CAGE code and a link to the SAM.gov entity record where available.

This is a dated, human-reviewed verification pass — not a live lookup performed on every page view. A confirmed recipient stays marked verified in the data until a later pass re-checks it. The funding figures themselves are reported values; verification confirms who the recipient is, not that a specific dollar amount is correct.

How the headline CLPS total is counted

The headline figure sums one value per distinct CLPS task order — not per record. A single order is reported at several valuations (announced, then current, then obligated); we keep the most concrete one per order, preferring obligated, then current, then announced, then potential, so the same order is never counted more than once. IDIQ program ceilings are excluded. Read it as reported award value across distinct CLPS delivery orders, not audited net spend.

Human-landing-system (HLS) awards — e.g. Blue Origin's Blue Moon Mark 2 — are a different program (crewed landers, not CLPS robotic deliveries) and are shown as a separate figure, never folded into the CLPS total. The “SAM-confirmed” count is the number of underlying award records whose recipient is SAM.gov-verified, not a dollar amount.

The honesty rules

  • Confirmed only on verified identity. Funding renders as confirmed only when the recipient's UEI is SAM-verified. Everything else is shown as reported, not confirmed.
  • Reported is not confirmed. The two are shown distinctly: the headline dollar figure is the reported total; a separate count shows how many records have a SAM-verified recipient.
  • Ceilings are not spend. IDIQ and program ceilings are flagged “not mission spend,” excluded from the headline total and from the structured data, and never counted as awarded money.
  • Every amount carries its type and date. No bare dollar figure — each is labeled announced / current / obligated / potential / ceiling and given an as-of date.
  • “Couldn't verify” is never “false.” An unconfirmed recipient is labeled unverified. That is not a claim that the entity is fake or that the money did not exist — absence of confirmation is not a negative finding.
  • Nothing is fabricated when a source is unreachable. If the live funding feed is unavailable, the page says so and shows nothing rather than inventing figures.

Freshness, cadence & limitations

The “generated” timestamp on the funding pages is when the live data was last fetched for that view — not when a figure was last verified. Recipient verification carries its own dated pass. The catalog and the funding crosswalk are refreshed periodically; we do not claim a fixed update cadence or real-time accuracy.

Known limitations: as-of dates often reflect our reporting date rather than the original award date; some line figures are unverified at the contract level; and a recipient shown as unverified may simply be awaiting the next verification pass. The catalog performs no live scraping, prediction, or financial analysis beyond the provided data.

Corrections

Every figure links the public source it came from. Where our record disagrees with the cited source, treat the source as authoritative and our record as the error — the verification pass exists to catch exactly that. Corrections that point to a public primary source (a SAM.gov entity record, a federal spending record, or an official announcement) are the most actionable.

Data reuse: the MoonOpps compilation is offered under CC BY 4.0 — see Data for the machine-readable downloads and dataset description.