astra: extract claims from 2026-04-03-mit-tech-review-four-things-data-centers-space

- Source: inbox/queue/2026-04-03-mit-tech-review-four-things-data-centers-space.md
- Domain: space-development
- Claims: 1, Entities: 0
- Enrichments: 4
- Extracted by: pipeline ingest (OpenRouter anthropic/claude-sonnet-4.5)

Pentagon-Agent: Astra <PIPELINE>

domains/space-development/leo-orbital-shell-capacity-ceiling-240000-satellites-physics-constraint.md

@@ -0,0 +1,17 @@
+---
+type: claim
+domain: space-development
+description: Each orbital shell can safely accommodate only 4,000-5,000 satellites before collision risk becomes catastrophic, creating a geometry-based constraint that no technology can overcome
+confidence: experimental
+source: MIT Technology Review, April 2026 technical assessment
+created: 2026-04-14
+title: LEO orbital shell capacity has a hard physical ceiling of approximately 240,000 satellites across all usable shells independent of launch capability or economics
+agent: astra
+scope: structural
+sourcer: MIT Technology Review
+related_claims: ["[[orbital debris is a classic commons tragedy where individual launch incentives are private but collision risk is externalized to all operators]]", "[[spacex-1m-odc-filing-represents-vertical-integration-at-unprecedented-scale-creating-captive-starship-demand-200x-starlink]]", "[[space traffic management is the most urgent governance gap because no authority has binding power to coordinate collision avoidance among thousands of operators]]"]
+---
+
+# LEO orbital shell capacity has a hard physical ceiling of approximately 240,000 satellites across all usable shells independent of launch capability or economics
+
+MIT Technology Review's April 2026 analysis identifies orbital capacity as a binding physical constraint distinct from economic or technical feasibility. The article cites that "roughly 4,000-5,000 satellites in one orbital shell" represents the maximum safe density before collision risk becomes unmanageable. Across all usable LEO shells, this yields a total capacity of approximately 240,000 satellites. This is a geometry problem, not an engineering problem—satellites in the same shell must maintain minimum separation distances to avoid collisions, and these distances are determined by orbital mechanics and tracking precision limits. SpaceX's 1 million satellite filing exceeds this physical ceiling by 4x, requiring approximately 200 orbital shells operating simultaneously—essentially the entire usable LEO volume dedicated to a single use case. Blue Origin's 51,600 satellite Project Sunrise represents approximately 22% of total LEO capacity for one company. Unlike launch cost or thermal management, this constraint cannot be solved through better technology—it's a fundamental limit imposed by orbital geometry and collision physics.

domains/space-development/orbital-radiators-are-binding-constraint-on-odc-power-density-not-just-cooling-solution.md

@@ -0,0 +1,17 @@
+---
+type: claim
+domain: space-development
+description: Radiator surface area scales faster than compute density making thermal management the hard limit on ODC power levels
+confidence: experimental
+source: Starcloud-2 mission specifications, TechCrunch March 2026
+created: 2026-04-14
+title: Deployable radiator capacity is the binding constraint on orbital data center power scaling as evidenced by Starcloud-2's 'largest commercial deployable radiator ever sent to space' for 100x power increase
+agent: astra
+scope: structural
+sourcer: "@TechCrunch"
+related_claims: ["[[orbital-data-center-thermal-management-is-scale-dependent-engineering-not-physics-constraint]]", "[[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]]"]
+---
+
+# Deployable radiator capacity is the binding constraint on orbital data center power scaling as evidenced by Starcloud-2's 'largest commercial deployable radiator ever sent to space' for 100x power increase
+
+Starcloud-2's mission manifest highlights the 'largest commercial deployable radiator ever sent to space' as a key enabling technology for its 100x power generation increase over Starcloud-1. This framing — radiator as headline feature alongside NVIDIA Blackwell GPUs and AWS server blades — reveals that radiator capacity, not compute hardware availability, is the binding constraint on ODC power scaling. The physics: radiative cooling in vacuum requires surface area proportional to the fourth root of power dissipation (Stefan-Boltzmann law), meaning doubling compute power requires ~19% more radiator area. But deployable radiators face mechanical complexity limits: larger structures require more robust deployment mechanisms, increasing mass and failure risk. Starcloud-2 is likely operating at 1-2 kW compute power (100x Starcloud-1's estimated <100W), still toy scale versus terrestrial data centers. The radiator emphasis suggests that reaching datacenter-scale power (10+ kW per rack) in orbit requires breakthrough deployable radiator technology, not just cheaper launches. This is consistent with the thermal management claims in the KB but adds specificity: the constraint isn't cooling physics broadly, it's deployable radiator engineering specifically.

domains/space-development/starcloud-3-cost-competitiveness-requires-500-per-kg-launch-cost-threshold.md

@@ -0,0 +1,17 @@
+---
+type: claim
+domain: space-development
+description: First explicit industry-stated threshold connecting ODC viability to specific launch cost milestone with $0.05/kWh target power cost
+confidence: experimental
+source: Philip Johnston (Starcloud CEO), TechCrunch interview March 2026
+created: 2026-04-14
+title: Orbital data centers achieve cost competitiveness with terrestrial facilities at $500/kg launch costs according to Starcloud CEO projections for Starcloud-3
+agent: astra
+scope: causal
+sourcer: "@TechCrunch"
+related_claims: ["[[launch cost reduction is the keystone variable that unlocks every downstream space industry at specific price thresholds]]", "[[orbital-data-center-cost-premium-converged-from-7-10x-to-3x-through-starship-pricing-alone]]", "[[Starship achieving routine operations at sub-100 dollars per kg is the single largest enabling condition for the entire space industrial economy]]"]
+---
+
+# Orbital data centers achieve cost competitiveness with terrestrial facilities at $500/kg launch costs according to Starcloud CEO projections for Starcloud-3
+
+Starcloud CEO Philip Johnston explicitly stated that Starcloud-3, their 200 kW / 3-tonne orbital data center designed for SpaceX's Starship deployment system, will be 'cost-competitive with terrestrial data centers' at a target of $0.05/kWh IF launch costs reach approximately $500/kg. This is the first publicly stated, specific dollar threshold for ODC cost parity from an operational company CEO. Current commercial Starship pricing is ~$600/kg (per Voyager Technologies filings), meaning the gap is only 17% — narrow enough that higher reuse cadence could close it by 2027-2028. Johnston noted that 'commercial Starship access isn't expected until 2028-2029,' placing cost-competitive ODC at scale in the 2028-2030 timeframe at earliest. This validates the general threshold model: each launch cost milestone activates a new industry tier. The $500/kg figure is specific, citable, and comes from a CEO with operational hardware in orbit (Starcloud-1) and paying customers lined up (Crusoe, AWS, Google Cloud, NVIDIA for Starcloud-2). This is not speculative modeling — it's a business planning threshold from someone betting $200M+ on the outcome.

inbox/archive/space-development/2026-04-03-mit-tech-review-four-things-data-centers-space.md

@@ -7,9 +7,12 @@ date: 2026-04-03
 domain: space-development
 secondary_domains: []
 format: article
-status: unprocessed
+status: processed
+processed_by: astra
+processed_date: 2026-04-14
 priority: high
 tags: [orbital-data-centers, feasibility, debris, orbital-capacity, launch-cost, thermal-management, MIT]
+extraction_model: "anthropic/claude-sonnet-4.5"
 ---
 
 ## Content