astra: extract claims from 2026-02-05-spacex-1m-satellite-odc-fcc-amazon-critique

- Source: inbox/queue/2026-02-05-spacex-1m-satellite-odc-fcc-amazon-critique.md
- Domain: space-development
- Claims: 2, Entities: 0
- Enrichments: 3
- Extracted by: pipeline ingest (OpenRouter anthropic/claude-sonnet-4.5)

Pentagon-Agent: Astra <PIPELINE>

domains/space-development/orbital-data-center-microgravity-thermal-management-requires-novel-refrigeration-architecture-because-standard-systems-depend-on-gravity.md

@@ -1,17 +1,18 @@
 ---
 type: claim
 domain: space-development
-description: Microgravity eliminates natural convection and causes compressor lubricating oil to clog systems, making terrestrial data center cooling designs non-functional in orbit
+description: Microgravity eliminates natural convection and causes compressor lubricating oil to clog systems, blocking direct adaptation of terrestrial cooling
 confidence: experimental
 source: Technical expert commentary, The Register, February 2026
 created: 2026-04-14
-title: Orbital data center thermal management requires novel refrigeration architecture because standard cooling systems depend on gravity for fluid management and convection
+title: Orbital data center refrigeration requires novel architecture because standard cooling systems depend on gravity for fluid management and convection
 agent: astra
-scope: functional
+scope: causal
 sourcer: "@theregister"
-related_claims: ["orbital-data-center-thermal-management-is-scale-dependent-engineering-not-physics-constraint.md", "space-based computing at datacenter scale is blocked by thermal physics because radiative cooling in vacuum requires surface areas that grow faster than compute density.md", "orbital data centers require five enabling technologies to mature simultaneously and none currently exist at required readiness.md"]
+challenges: ["orbital-data-center-thermal-management-is-scale-dependent-engineering-not-physics-constraint"]
+related: ["orbital-data-center-thermal-management-is-scale-dependent-engineering-not-physics-constraint", "orbital-radiators-are-binding-constraint-on-odc-power-density-not-just-cooling-solution"]
 ---
 
-# Orbital data center thermal management requires novel refrigeration architecture because standard cooling systems depend on gravity for fluid management and convection
+# Orbital data center refrigeration requires novel architecture because standard cooling systems depend on gravity for fluid management and convection
 
-Technical experts identified a fundamental engineering constraint for orbital data centers that goes beyond radiative cooling surface area: standard refrigeration systems rely on gravity-dependent mechanisms. In microgravity, compressor lubricating oil can clog systems because fluid separation depends on gravity. Heat cannot rise via natural convection, eliminating passive cooling pathways that terrestrial data centers use. This means orbital data centers cannot simply adapt existing data center cooling designs — they require fundamentally different thermal management architectures. The constraint is not just about radiating heat to space (which is surface-area limited), but about moving heat from chips to radiators in the first place. This adds a layer of engineering complexity beyond what most orbital data center proposals acknowledge. As one expert noted, 'a lot in this proposal riding on assumptions and technology that doesn't appear to actually exist yet.' This is distinct from the radiative cooling constraint — it's an internal fluid management problem that must be solved before the external radiation problem even matters.
+Standard terrestrial refrigeration systems face fundamental physics barriers in microgravity environments. Natural convection—where heat rises via density differences—does not occur in microgravity, eliminating passive heat transfer mechanisms. Compressor-based cooling systems rely on gravity to separate lubricating oil from refrigerant; in microgravity, oil can migrate and clog the system. This is distinct from the radiator scaling problem (which is about heat rejection to space) and represents a separate engineering challenge for the refrigeration cycle itself. Technical experts quoted in the FCC filing analysis noted that 'a lot in this proposal riding on assumptions and technology that doesn't appear to actually exist yet,' with refrigeration specifically called out as an unresolved problem. This suggests orbital data centers require either novel refrigeration architectures (possibly using capillary action, magnetic separation, or entirely different cooling cycles) or must operate without active refrigeration, relying solely on passive radiative cooling.

domains/space-development/spacex-1m-satellite-filing-faces-44x-launch-cadence-gap-between-required-and-achieved-capacity.md

@@ -1,17 +1,18 @@
 ---
 type: claim
 domain: space-development
-description: Amazon's FCC analysis shows 200,000 annual satellite replacements required versus 4,600 global launches in 2025, creating a physical production constraint independent of cost or technology
+description: Amazon's FCC analysis shows 200,000 annual satellite replacements required versus 4,600 global launches in 2025
-confidence: experimental
+confidence: likely
-source: Amazon FCC petition, March 2026
+source: Amazon FCC petition, February 2026
 created: 2026-04-14
-title: SpaceX's 1 million satellite orbital data center constellation faces a 44x launch cadence gap between required replacement rate and current global capacity
+title: SpaceX's 1M satellite filing faces a 44x launch cadence gap between required replacement rate and current global capacity
 agent: astra
 scope: structural
 sourcer: "@theregister"
-related_claims: ["spacex-1m-odc-filing-represents-vertical-integration-at-unprecedented-scale-creating-captive-starship-demand-200x-starlink.md", "manufacturing-rate-does-not-equal-launch-cadence-in-aerospace-operations.md", "orbital-compute-filings-are-regulatory-positioning-not-technical-readiness.md"]
+supports: ["spacex-1m-satellite-filing-is-spectrum-reservation-strategy-not-deployment-plan", "leo-orbital-shell-capacity-ceiling-240000-satellites-physics-constraint"]
+related: ["spacex-1m-satellite-filing-is-spectrum-reservation-strategy-not-deployment-plan", "leo-orbital-shell-capacity-ceiling-240000-satellites-physics-constraint", "manufacturing-rate-does-not-equal-launch-cadence-in-aerospace-operations", "spacex-1m-odc-filing-represents-vertical-integration-at-unprecedented-scale-creating-captive-starship-demand-200x-starlink"]
 ---
 
-# SpaceX's 1 million satellite orbital data center constellation faces a 44x launch cadence gap between required replacement rate and current global capacity
+# SpaceX's 1M satellite filing faces a 44x launch cadence gap between required replacement rate and current global capacity
 
-Amazon's FCC petition provides the most rigorous quantitative challenge to SpaceX's 1 million satellite orbital data center filing. The math is straightforward: 1 million satellites with 5-year lifespans require 200,000 replacements per year to maintain the constellation. Global satellite launch output in 2025 was under 4,600 satellites. This creates a 44x gap between required and achieved capacity. This is not a cost problem or a technology readiness problem — it is a physical manufacturing and launch capacity constraint. Even if Starship achieves 1,000 flights per year with 300 satellites per flight (300,000 satellites/year), and if ALL of those launches served only this constellation, it would barely meet replacement demand. As of March 2026, Starship is not flying 1,000 times per year. The constraint is binding at the industrial production level, not the vehicle capability level. This analysis reveals that mega-constellation filings may be constrained more by manufacturing rate and launch cadence than by any single technology barrier.
+Amazon's FCC petition provides rigorous quantitative analysis of the physical constraints on SpaceX's 1 million satellite orbital data center constellation. With a 5-year satellite lifespan, the constellation requires 200,000 satellite replacements per year to maintain operational capacity. Global satellite launch output in 2025 was under 4,600 satellites across all providers and missions. This creates a 44x gap between required and achieved capacity. Even assuming Starship reaches 1,000 flights per year with 300 satellites per flight (300,000 satellites/year capacity), and if 100% of that capacity were dedicated to this single constellation, it would barely meet replacement demand—leaving zero capacity for initial deployment, other Starlink shells, or any other missions. The constraint is not cost or technology readiness, but physical manufacturing and launch infrastructure capacity that has never existed in spaceflight history.