4. Department of Defense · Notable
Declassify information about threats to the U.S. space constellation
Printed page 118 4. Department of Defense
“Declassify appropriate information about terrestrial and on-orbit space capabilities that threaten the U.S. space constellation, as well as those being pursued by our competitors, to secure the principled right to counter them offensively.”
What has happened
- Partially done
The Space Force does publish an unclassified account of the threat, and it is substantive. The *Space Threat Fact Sheet* on `spaceforce.mil`, marked "(Current as of July 2026)", names adversary counterspace systems, orbits and dates: the PLA's 2007 ground-based ASAT test and DIA's assessment that China "probably intends to field ASAT weapons able to reach up to GEO at 36,000 km"; SJ-21's 2022 relocation of a BeiDou satellite to a graveyard orbit; "multiple ground-based laser weapons able to disrupt, degrade, or damage satellite sensors"; Russia's November 2021 Nudol test and its 1,500 pieces of trackable debris; and "Russia has deployed probable orbital ASAT prototypes into LEO in 2017, 2019, 2022, 2024, and 2025. The four most recent were all placed in orbits matching those of U.S. national security satellites, and one ejected an object near a Russian satellite while testing a space-based ASAT weapon", with a June 2025 launch "into a peculiar high-altitude orbit, passing near numerous U.S. and allied satellites". Some of that could not have been published before this window: the 2025 deployments and the 2026 Chinese launch figures postdate it. That is the ask's object — information about capabilities that threaten the U.S. space constellation, in public. It is `partial` and not `done` for three reasons. The page carries no publication date of its own, so it cannot be shown that anything was *declassified* rather than compiled from material already unclassified. Nothing establishes when the fact sheet first appeared or whether it re-issues pre-window text. And the Quote's purpose limb — declassification "to secure the principled right to counter them offensively" — is not addressed anywhere in it; see #230, #235 and #236, all of which this read leaves unmoved.
Research log
What was searched, and what didn’t count as evidence
Research notes
One negative search covered the space asks on pages 118–119.
- not started → partial on 2026-09-03, and the wall was a hostname. The earlier search recorded spaceforce.mil as refusing us. Bare spaceforce.mil does not resolve; www.spaceforce.mil does, and can be read — the same mistake of a failed address read as a refusal that turned up on navy.mil and saffm.hq.af.mil. The stale not started event of 2026-08-28 was replaced rather than appended to, so the page does not show a reversal that never happened.
- The negative that remains is bounded, and the boundary matters. What was read on 2026-09-03: https://www.spaceforce.mil/space-policy-page/ (the service’s own policy-document index) and the complete USSF newsroom feed — 500 items spanning 2024-07-30 to 2026-09-01. Neither carries a declassification announcement. So the reading is: the fact sheet exists and is the strongest thing on the record for this ask, and no allowlisted source says any of it was newly declassified. That reaches USSF’s own publication channels; it does not reach OSD, the NSC or any classified annex.
- Dating is the item’s weakest point, and the Evidence title says so in the form used for an undated page: dated at the day we observed it, and approximate. The nearest thing to an internal date is the fact sheet’s own content — it reports Chinese orbital launch counts “through June” and a 2026 launch target — which puts the current text inside the window but says nothing about when the page was first published.
- Action
- issue
- Object
- classified information on threats to U.S. space assets
- ID
- 233