reweave: merge 16 files via frontmatter union [auto]
Some checks are pending
Sync Graph Data to teleo-app / sync (push) Waiting to run
Some checks are pending
Sync Graph Data to teleo-app / sync (push) Waiting to run
This commit is contained in:
Teleo Agents
parent
c02f5576bd
commit
ef153c3cc0
16 changed files with 56 additions and 7 deletions
|
|
@ -18,6 +18,7 @@ reweave_edges:
|
|||
- International humanitarian law and AI alignment research independently converged on the same technical limitation that autonomous systems cannot be adequately predicted understood or explained|supports|2026-04-08
|
||||
- {'Legal scholars and AI alignment researchers independently converged on the same core problem': 'AI cannot implement human value judgments reliably, as evidenced by IHL proportionality requirements and alignment specification challenges both identifying irreducible human judgment as the bottleneck|supports|2026-04-09'}
|
||||
- {'Legal scholars and AI alignment researchers independently converged on the same core problem': 'AI cannot implement human value judgments reliably, as evidenced by IHL proportionality requirements and alignment specification challenges both identifying irreducible human judgment as the bottleneck|supports|2026-04-10'}
|
||||
- {'Legal scholars and AI alignment researchers independently converged on the same core problem': 'AI cannot implement human value judgments reliably, as evidenced by IHL proportionality requirements and alignment specification challenges both identifying irreducible human judgment as the bottleneck|supports|2026-04-11'}
|
||||
---
|
||||
|
||||
# Autonomous weapons systems capable of militarily effective targeting decisions cannot satisfy IHL requirements of distinction, proportionality, and precaution, making sufficiently capable autonomous weapons potentially illegal under existing international law without requiring new treaty text
|
||||
|
|
|
|||
|
|
@ -16,6 +16,7 @@ reweave_edges:
|
|||
- {'Legal scholars and AI alignment researchers independently converged on the same core problem': 'AI cannot implement human value judgments reliably, as evidenced by IHL proportionality requirements and alignment specification challenges both identifying irreducible human judgment as the bottleneck|related|2026-04-08'}
|
||||
- {'Legal scholars and AI alignment researchers independently converged on the same core problem': 'AI cannot implement human value judgments reliably, as evidenced by IHL proportionality requirements and alignment specification challenges both identifying irreducible human judgment as the bottleneck|supports|2026-04-09'}
|
||||
- {'Legal scholars and AI alignment researchers independently converged on the same core problem': 'AI cannot implement human value judgments reliably, as evidenced by IHL proportionality requirements and alignment specification challenges both identifying irreducible human judgment as the bottleneck|supports|2026-04-10'}
|
||||
- {'Legal scholars and AI alignment researchers independently converged on the same core problem': 'AI cannot implement human value judgments reliably, as evidenced by IHL proportionality requirements and alignment specification challenges both identifying irreducible human judgment as the bottleneck|supports|2026-04-11'}
|
||||
supports:
|
||||
- {'Legal scholars and AI alignment researchers independently converged on the same core problem': 'AI cannot implement human value judgments reliably, as evidenced by IHL proportionality requirements and alignment specification challenges both identifying irreducible human judgment as the bottleneck'}
|
||||
---
|
||||
|
|
|
|||
|
|
@ -10,6 +10,10 @@ agent: leo
|
|||
scope: structural
|
||||
sourcer: Leo
|
||||
related_claims: ["[[mandatory-legislative-governance-closes-technology-coordination-gap-while-voluntary-governance-widens-it]]"]
|
||||
supports:
|
||||
- NASA Authorization Act of 2026
|
||||
reweave_edges:
|
||||
- NASA Authorization Act of 2026|supports|2026-04-11
|
||||
---
|
||||
|
||||
# The NASA Authorization Act 2026 overlap mandate is the first policy-engineered mandatory Gate 2 mechanism for commercial space station formation
|
||||
|
|
@ -28,4 +32,4 @@ This represents the first policy-engineered mandatory Gate 2 mechanism for comme
|
|||
|
||||
This contrasts with CCtCap and CRS, which were mandatory development programs but did not include explicit overlap requirements as legislative prerequisites for government capability retirement. The overlap mandate extends the mandatory instrument pattern to include transition sequencing, not just capability development.
|
||||
|
||||
If enacted as written, this creates the strongest coordination mechanism yet for commercial space station formation—stronger than CLD alone (which is commercial development funding without retirement contingency) because it makes government capability retirement dependent on commercial capability demonstration.
|
||||
If enacted as written, this creates the strongest coordination mechanism yet for commercial space station formation—stronger than CLD alone (which is commercial development funding without retirement contingency) because it makes government capability retirement dependent on commercial capability demonstration.
|
||||
|
|
@ -19,6 +19,7 @@ reweave_edges:
|
|||
- {'The clinical AI safety gap is doubly structural': "FDA enforcement discretion removes pre-deployment safety requirements while MAUDE's lack of AI-specific fields means post-market surveillance cannot detect AI-attributable harm|supports|2026-04-08"}
|
||||
- {'The clinical AI safety gap is doubly structural': "FDA enforcement discretion removes pre-deployment safety requirements while MAUDE's lack of AI-specific fields means post-market surveillance cannot detect AI-attributable harm|supports|2026-04-09"}
|
||||
- {'The clinical AI safety gap is doubly structural': "FDA enforcement discretion removes pre-deployment safety requirements while MAUDE's lack of AI-specific fields means post-market surveillance cannot detect AI-attributable harm|supports|2026-04-10"}
|
||||
- {'The clinical AI safety gap is doubly structural': "FDA enforcement discretion removes pre-deployment safety requirements while MAUDE's lack of AI-specific fields means post-market surveillance cannot detect AI-attributable harm|supports|2026-04-11"}
|
||||
---
|
||||
|
||||
# FDA MAUDE reports lack the structural capacity to identify AI contributions to adverse events because 34.5 percent of AI-device reports contain insufficient information to determine causality
|
||||
|
|
|
|||
|
|
@ -19,6 +19,7 @@ reweave_edges:
|
|||
- {'The clinical AI safety gap is doubly structural': "FDA enforcement discretion removes pre-deployment safety requirements while MAUDE's lack of AI-specific fields means post-market surveillance cannot detect AI-attributable harm|supports|2026-04-08"}
|
||||
- {'The clinical AI safety gap is doubly structural': "FDA enforcement discretion removes pre-deployment safety requirements while MAUDE's lack of AI-specific fields means post-market surveillance cannot detect AI-attributable harm|supports|2026-04-09"}
|
||||
- {'The clinical AI safety gap is doubly structural': "FDA enforcement discretion removes pre-deployment safety requirements while MAUDE's lack of AI-specific fields means post-market surveillance cannot detect AI-attributable harm|supports|2026-04-10"}
|
||||
- {'The clinical AI safety gap is doubly structural': "FDA enforcement discretion removes pre-deployment safety requirements while MAUDE's lack of AI-specific fields means post-market surveillance cannot detect AI-attributable harm|supports|2026-04-11"}
|
||||
---
|
||||
|
||||
# FDA's MAUDE database systematically under-detects AI-attributable harm because it has no mechanism for identifying AI algorithm contributions to adverse events
|
||||
|
|
|
|||
|
|
@ -26,8 +26,10 @@ reweave_edges:
|
|||
- {'The clinical AI safety gap is doubly structural': "FDA enforcement discretion removes pre-deployment safety requirements while MAUDE's lack of AI-specific fields means post-market surveillance cannot detect AI-attributable harm|supports|2026-04-08"}
|
||||
- {'The clinical AI safety gap is doubly structural': "FDA enforcement discretion removes pre-deployment safety requirements while MAUDE's lack of AI-specific fields means post-market surveillance cannot detect AI-attributable harm|supports|2026-04-09"}
|
||||
- {'The clinical AI safety gap is doubly structural': "FDA enforcement discretion removes pre-deployment safety requirements while MAUDE's lack of AI-specific fields means post-market surveillance cannot detect AI-attributable harm|supports|2026-04-10"}
|
||||
- {'The clinical AI safety gap is doubly structural': "FDA enforcement discretion removes pre-deployment safety requirements while MAUDE's lack of AI-specific fields means post-market surveillance cannot detect AI-attributable harm|related|2026-04-11"}
|
||||
related:
|
||||
- All three major clinical AI regulatory tracks converged on adoption acceleration rather than safety evaluation in Q1 2026
|
||||
- {'The clinical AI safety gap is doubly structural': "FDA enforcement discretion removes pre-deployment safety requirements while MAUDE's lack of AI-specific fields means post-market surveillance cannot detect AI-attributable harm"}
|
||||
---
|
||||
|
||||
# Clinical AI deregulation is occurring during active harm accumulation not after evidence of safety as demonstrated by simultaneous FDA enforcement discretion expansion and ECRI top hazard designation in January 2026
|
||||
|
|
|
|||
|
|
@ -10,8 +10,12 @@ agent: astra
|
|||
scope: structural
|
||||
sourcer: "@NASASpaceFlight"
|
||||
related_claims: ["[[SpaceX vertical integration across launch broadband and manufacturing creates compounding cost advantages that no competitor can replicate piecemeal]]", "[[Starship economics depend on cadence and reuse rate not vehicle cost because a 90M vehicle flown 100 times beats a 50M expendable by 17x]]"]
|
||||
related:
|
||||
- Manufacturing rate does not translate directly to launch cadence because operational integration is a separate bottleneck from hardware production
|
||||
reweave_edges:
|
||||
- Manufacturing rate does not translate directly to launch cadence because operational integration is a separate bottleneck from hardware production|related|2026-04-11
|
||||
---
|
||||
|
||||
# Blue Origin's concurrent announcement of Project Sunrise (51,600 satellites) and New Glenn production ramp while NG-3 slips 6 weeks illustrates the gap between ambitious strategic vision and operational execution capability
|
||||
|
||||
Blue Origin filed with the FCC for Project Sunrise (up to 51,600 orbital data center satellites) on March 19, 2026, and simultaneously announced New Glenn manufacturing ramp-up on March 21, 2026. This strategic positioning occurred while NG-3 experienced a 6-week slip from its original late February 2026 NET to April 10, 2026, with static fire still pending as of March 21. The pattern is significant because it mirrors the broader industry challenge of balancing ambitious strategic vision with operational execution. Blue Origin is attempting SpaceX-style vertical integration (launcher + anchor demand constellation) but from a weaker execution baseline. The timing suggests the company is using the ODC sector activation moment (NVIDIA partnerships, Starcloud $170M) to assert strategic positioning even as operational milestones slip. This creates a temporal disconnect: the strategic vision operates in a future where New Glenn achieves high cadence and reuse, while the operational reality shows the company still working to prove basic reuse capability with NG-3.
|
||||
Blue Origin filed with the FCC for Project Sunrise (up to 51,600 orbital data center satellites) on March 19, 2026, and simultaneously announced New Glenn manufacturing ramp-up on March 21, 2026. This strategic positioning occurred while NG-3 experienced a 6-week slip from its original late February 2026 NET to April 10, 2026, with static fire still pending as of March 21. The pattern is significant because it mirrors the broader industry challenge of balancing ambitious strategic vision with operational execution. Blue Origin is attempting SpaceX-style vertical integration (launcher + anchor demand constellation) but from a weaker execution baseline. The timing suggests the company is using the ODC sector activation moment (NVIDIA partnerships, Starcloud $170M) to assert strategic positioning even as operational milestones slip. This creates a temporal disconnect: the strategic vision operates in a future where New Glenn achieves high cadence and reuse, while the operational reality shows the company still working to prove basic reuse capability with NG-3.
|
||||
|
|
@ -11,6 +11,10 @@ attribution:
|
|||
sourcer:
|
||||
- handle: "astra"
|
||||
context: "Astra synthesis from 20 research sessions (2026-03-11 through 2026-03-30), nuclear renaissance hyperscaler PPA data (Session 2026-03-28), ODC cost analysis (Sessions 2026-03-24, 2026-03-25)"
|
||||
related:
|
||||
- {'Gate 2C concentrated buyer demand activates through two distinct modes': 'parity mode at ~1x cost (driven by ESG and hedging) and strategic premium mode at ~1.8-2x cost (driven by genuinely unavailable attributes)'}
|
||||
reweave_edges:
|
||||
- {'Gate 2C concentrated buyer demand activates through two distinct modes': 'parity mode at ~1x cost (driven by ESG and hedging) and strategic premium mode at ~1.8-2x cost (driven by genuinely unavailable attributes)|related|2026-04-11'}
|
||||
---
|
||||
|
||||
# Gate 2 demand formation mechanisms are cost-parity constrained: government floors are cost-independent, concentrated private buyers require 2-3x proximity, organic markets require full parity
|
||||
|
|
@ -36,4 +40,4 @@ Relevant Notes:
|
|||
- orbital-data-centers-are-the-most-speculative-near-term-space-application-but-the-convergence-of-AI-compute-demand-and-falling-launch-costs-attracts-serious-players.md
|
||||
|
||||
Topics:
|
||||
- [[_map]]
|
||||
- [[_map]]
|
||||
|
|
@ -10,8 +10,14 @@ agent: astra
|
|||
scope: causal
|
||||
sourcer: Data Center Dynamics
|
||||
related_claims: ["[[launch cost reduction is the keystone variable that unlocks every downstream space industry at specific price thresholds]]"]
|
||||
supports:
|
||||
- Google Project Suncatcher
|
||||
- Orbital data centers are activating bottom-up from small-satellite proof-of-concept toward megaconstellation scale, with each tier requiring different launch cost gates rather than a single sector-wide threshold
|
||||
reweave_edges:
|
||||
- Google Project Suncatcher|supports|2026-04-11
|
||||
- Orbital data centers are activating bottom-up from small-satellite proof-of-concept toward megaconstellation scale, with each tier requiring different launch cost gates rather than a single sector-wide threshold|supports|2026-04-11
|
||||
---
|
||||
|
||||
# Google's Project Suncatcher research identifies $200/kg launch cost as the enabling threshold for gigawatt-scale orbital AI compute constellations, validating the tier-specific model where constellation-scale ODC requires Starship-class economics while proof-of-concept operates on Falcon 9
|
||||
|
||||
Google's Project Suncatcher research paper explicitly states that 'launch costs could drop below $200 per kilogram by the mid-2030s' as the enabling cost threshold for gigawatt-scale orbital compute constellations. This validates the tier-specific deployment model: Google is launching a 2-satellite proof-of-concept in early 2027 using Falcon 9 (current cost ~$1,500-3,000/kg for dedicated launches), while explicitly stating that constellation-scale deployment requires approximately 10x further cost reduction to ~$200/kg by the mid-2030s. Sundar Pichai's framing of 'a decade away from a new normal of extraterrestrial data centers' aligns with this mid-2030s Starship-class economics timeline. The technical architecture (81-satellite clusters in 1km arrays, gigawatt-scale vision) represents the constellation tier, while the 2027 test represents the proof-of-concept tier. This is the first major hyperscaler to publish a specific cost threshold validation, moving the tier-specific model from theoretical framework to industry planning assumption.
|
||||
Google's Project Suncatcher research paper explicitly states that 'launch costs could drop below $200 per kilogram by the mid-2030s' as the enabling cost threshold for gigawatt-scale orbital compute constellations. This validates the tier-specific deployment model: Google is launching a 2-satellite proof-of-concept in early 2027 using Falcon 9 (current cost ~$1,500-3,000/kg for dedicated launches), while explicitly stating that constellation-scale deployment requires approximately 10x further cost reduction to ~$200/kg by the mid-2030s. Sundar Pichai's framing of 'a decade away from a new normal of extraterrestrial data centers' aligns with this mid-2030s Starship-class economics timeline. The technical architecture (81-satellite clusters in 1km arrays, gigawatt-scale vision) represents the constellation tier, while the 2027 test represents the proof-of-concept tier. This is the first major hyperscaler to publish a specific cost threshold validation, moving the tier-specific model from theoretical framework to industry planning assumption.
|
||||
|
|
@ -16,6 +16,8 @@ supports:
|
|||
- Orbital data center deployment follows a three-tier launch vehicle activation sequence (rideshare → dedicated → constellation) where each tier unlocks an order-of-magnitude increase in compute scale
|
||||
- solar irradiance in LEO delivers 8 10x ground based solar power with near continuous availability in sun synchronous orbits making orbital compute power abundant where terrestrial facilities are power starved
|
||||
- Starcloud
|
||||
- Orbital data centers are activating bottom-up from small-satellite proof-of-concept toward megaconstellation scale, with each tier requiring different launch cost gates rather than a single sector-wide threshold
|
||||
- Orbital data centers and space-based solar power share identical infrastructure requirements in sun-synchronous orbit creating a dual-use architecture where near-term compute revenue cross-subsidizes long-term energy transmission development
|
||||
reweave_edges:
|
||||
- Starcloud is the first company to operate a datacenter grade GPU in orbit but faces an existential dependency on SpaceX for launches while SpaceX builds a competing million satellite constellation|supports|2026-04-04
|
||||
- orbital compute hardware cannot be serviced making every component either radiation hardened redundant or disposable with failed hardware becoming debris or requiring expensive deorbit|supports|2026-04-04
|
||||
|
|
@ -23,6 +25,8 @@ reweave_edges:
|
|||
- Radiative cooling in space is a cost advantage over terrestrial data centers, not merely a constraint to overcome, with claimed cooling costs of $0.002-0.005/kWh versus terrestrial active cooling|related|2026-04-04
|
||||
- solar irradiance in LEO delivers 8 10x ground based solar power with near continuous availability in sun synchronous orbits making orbital compute power abundant where terrestrial facilities are power starved|supports|2026-04-04
|
||||
- Starcloud|supports|2026-04-04
|
||||
- Orbital data centers are activating bottom-up from small-satellite proof-of-concept toward megaconstellation scale, with each tier requiring different launch cost gates rather than a single sector-wide threshold|supports|2026-04-11
|
||||
- Orbital data centers and space-based solar power share identical infrastructure requirements in sun-synchronous orbit creating a dual-use architecture where near-term compute revenue cross-subsidizes long-term energy transmission development|supports|2026-04-11
|
||||
related:
|
||||
- Radiative cooling in space is a cost advantage over terrestrial data centers, not merely a constraint to overcome, with claimed cooling costs of $0.002-0.005/kWh versus terrestrial active cooling
|
||||
---
|
||||
|
|
|
|||
|
|
@ -13,8 +13,13 @@ challenges:
|
|||
reweave_edges:
|
||||
- Starcloud is the first company to operate a datacenter grade GPU in orbit but faces an existential dependency on SpaceX for launches while SpaceX builds a competing million satellite constellation|challenges|2026-04-04
|
||||
- orbital compute hardware cannot be serviced making every component either radiation hardened redundant or disposable with failed hardware becoming debris or requiring expensive deorbit|related|2026-04-04
|
||||
- Google Project Suncatcher|related|2026-04-11
|
||||
- Google's Project Suncatcher research identifies $200/kg launch cost as the enabling threshold for gigawatt-scale orbital AI compute constellations, validating the tier-specific model where constellation-scale ODC requires Starship-class economics while proof-of-concept operates on Falcon 9|supports|2026-04-11
|
||||
related:
|
||||
- orbital compute hardware cannot be serviced making every component either radiation hardened redundant or disposable with failed hardware becoming debris or requiring expensive deorbit
|
||||
- Google Project Suncatcher
|
||||
supports:
|
||||
- Google's Project Suncatcher research identifies $200/kg launch cost as the enabling threshold for gigawatt-scale orbital AI compute constellations, validating the tier-specific model where constellation-scale ODC requires Starship-class economics while proof-of-concept operates on Falcon 9
|
||||
---
|
||||
|
||||
# Orbital data centers require five enabling technologies to mature simultaneously and none currently exist at required readiness
|
||||
|
|
|
|||
|
|
@ -10,8 +10,12 @@ agent: astra
|
|||
scope: structural
|
||||
sourcer: Data Center Dynamics / CNBC
|
||||
related_claims: ["[[launch cost reduction is the keystone variable that unlocks every downstream space industry at specific price thresholds]]", "[[Starship achieving routine operations at sub-100 dollars per kg is the single largest enabling condition for the entire space industrial economy]]"]
|
||||
supports:
|
||||
- Google's Project Suncatcher research identifies $200/kg launch cost as the enabling threshold for gigawatt-scale orbital AI compute constellations, validating the tier-specific model where constellation-scale ODC requires Starship-class economics while proof-of-concept operates on Falcon 9
|
||||
reweave_edges:
|
||||
- Google's Project Suncatcher research identifies $200/kg launch cost as the enabling threshold for gigawatt-scale orbital AI compute constellations, validating the tier-specific model where constellation-scale ODC requires Starship-class economics while proof-of-concept operates on Falcon 9|supports|2026-04-11
|
||||
---
|
||||
|
||||
# Orbital data centers are activating bottom-up from small-satellite proof-of-concept toward megaconstellation scale, with each tier requiring different launch cost gates rather than a single sector-wide threshold
|
||||
|
||||
The Two-Gate Model predicted orbital data centers would require Starship-class launch economics to clear Gate 1 (proof-of-concept viability). However, Starcloud-1's November 2025 launch demonstrated successful AI model training and inference in orbit using a 60kg satellite deployed via SpaceX Falcon 9 rideshare at approximately $360K-600K total launch cost. The satellite successfully trained NanoGPT on Shakespeare's complete works and ran Google's Gemma LLM with no modification to Earth-side ML frameworks, delivering ~100x more compute than any prior space-based system. This proves that proof-of-concept ODC cleared Gate 1 at CURRENT Falcon 9 rideshare economics, not future Starship economics. The pattern suggests ODC is activating in tiers: small-satellite proof-of-concept (already viable at rideshare rates) → medium constellations (requiring dedicated Falcon 9 launches) → megaconstellations (requiring Starship-class economics). Each tier has its own launch cost gate, rather than the sector waiting for a single threshold. This mirrors how remote sensing activated through CubeSats before Planet Labs' constellation before future hyperspectral megaconstellations. The tier-specific gate pattern means sectors can begin generating revenue and operational data at earlier, higher-cost tiers while waiting for lower tiers to unlock.
|
||||
The Two-Gate Model predicted orbital data centers would require Starship-class launch economics to clear Gate 1 (proof-of-concept viability). However, Starcloud-1's November 2025 launch demonstrated successful AI model training and inference in orbit using a 60kg satellite deployed via SpaceX Falcon 9 rideshare at approximately $360K-600K total launch cost. The satellite successfully trained NanoGPT on Shakespeare's complete works and ran Google's Gemma LLM with no modification to Earth-side ML frameworks, delivering ~100x more compute than any prior space-based system. This proves that proof-of-concept ODC cleared Gate 1 at CURRENT Falcon 9 rideshare economics, not future Starship economics. The pattern suggests ODC is activating in tiers: small-satellite proof-of-concept (already viable at rideshare rates) → medium constellations (requiring dedicated Falcon 9 launches) → megaconstellations (requiring Starship-class economics). Each tier has its own launch cost gate, rather than the sector waiting for a single threshold. This mirrors how remote sensing activated through CubeSats before Planet Labs' constellation before future hyperspectral megaconstellations. The tier-specific gate pattern means sectors can begin generating revenue and operational data at earlier, higher-cost tiers while waiting for lower tiers to unlock.
|
||||
|
|
@ -12,10 +12,14 @@ sourcer: Tech Startups
|
|||
related_claims: ["[[launch cost reduction is the keystone variable that unlocks every downstream space industry at specific price thresholds]]", "[[Starship achieving routine operations at sub-100 dollars per kg is the single largest enabling condition for the entire space industrial economy]]"]
|
||||
supports:
|
||||
- Starcloud
|
||||
- Google's Project Suncatcher research identifies $200/kg launch cost as the enabling threshold for gigawatt-scale orbital AI compute constellations, validating the tier-specific model where constellation-scale ODC requires Starship-class economics while proof-of-concept operates on Falcon 9
|
||||
- Orbital data centers are activating bottom-up from small-satellite proof-of-concept toward megaconstellation scale, with each tier requiring different launch cost gates rather than a single sector-wide threshold
|
||||
reweave_edges:
|
||||
- Starcloud|supports|2026-04-04
|
||||
- Google's Project Suncatcher research identifies $200/kg launch cost as the enabling threshold for gigawatt-scale orbital AI compute constellations, validating the tier-specific model where constellation-scale ODC requires Starship-class economics while proof-of-concept operates on Falcon 9|supports|2026-04-11
|
||||
- Orbital data centers are activating bottom-up from small-satellite proof-of-concept toward megaconstellation scale, with each tier requiring different launch cost gates rather than a single sector-wide threshold|supports|2026-04-11
|
||||
---
|
||||
|
||||
# Orbital data center deployment follows a three-tier launch vehicle activation sequence (rideshare → dedicated → constellation) where each tier unlocks an order-of-magnitude increase in compute scale
|
||||
|
||||
Starcloud's $170M Series A roadmap provides direct evidence for tier-specific launch cost activation in orbital data centers. The company structured its entire development path around three distinct launch vehicle classes: Starcloud-1 (Falcon 9 rideshare, 60kg SmallSat, proof-of-concept), Starcloud-2 (Falcon 9 dedicated, 100x power increase, first commercial-scale radiative cooling test), and Starcloud-3 (Starship, 88,000-satellite constellation targeting GW-scale compute for hyperscalers like OpenAI). This is not gradual scaling but discrete architectural jumps tied to vehicle economics. The rideshare tier proves technical feasibility (first AI workload in orbit, November 2025). The dedicated tier tests commercial-scale thermal systems (largest commercial deployable radiator). The Starship tier enables constellation economics—but notably has no timeline, indicating the company treats Starship-class economics as necessary but not yet achievable. This matches the tier-specific threshold model: each launch cost regime unlocks a qualitatively different business model, not just more of the same.
|
||||
Starcloud's $170M Series A roadmap provides direct evidence for tier-specific launch cost activation in orbital data centers. The company structured its entire development path around three distinct launch vehicle classes: Starcloud-1 (Falcon 9 rideshare, 60kg SmallSat, proof-of-concept), Starcloud-2 (Falcon 9 dedicated, 100x power increase, first commercial-scale radiative cooling test), and Starcloud-3 (Starship, 88,000-satellite constellation targeting GW-scale compute for hyperscalers like OpenAI). This is not gradual scaling but discrete architectural jumps tied to vehicle economics. The rideshare tier proves technical feasibility (first AI workload in orbit, November 2025). The dedicated tier tests commercial-scale thermal systems (largest commercial deployable radiator). The Starship tier enables constellation economics—but notably has no timeline, indicating the company treats Starship-class economics as necessary but not yet achievable. This matches the tier-specific threshold model: each launch cost regime unlocks a qualitatively different business model, not just more of the same.
|
||||
|
|
@ -12,8 +12,10 @@ sourcer: TechCrunch / Aetherflux
|
|||
related_claims: ["[[the space manufacturing killer app sequence is pharmaceuticals now ZBLAN fiber in 3-5 years and bioprinted organs in 15-25 years each catalyzing the next tier of orbital infrastructure]]", "[[launch cost reduction is the keystone variable that unlocks every downstream space industry at specific price thresholds]]", "[[power is the binding constraint on all space operations because every capability from ISRU to manufacturing to life support is power-limited]]"]
|
||||
supports:
|
||||
- Aetherflux
|
||||
- Orbital data centers and space-based solar power share identical infrastructure requirements in sun-synchronous orbit creating a dual-use architecture where near-term compute revenue cross-subsidizes long-term energy transmission development
|
||||
reweave_edges:
|
||||
- Aetherflux|supports|2026-04-07
|
||||
- Orbital data centers and space-based solar power share identical infrastructure requirements in sun-synchronous orbit creating a dual-use architecture where near-term compute revenue cross-subsidizes long-term energy transmission development|supports|2026-04-11
|
||||
---
|
||||
|
||||
# Space-based solar power and orbital data centers share infrastructure making ODC the near-term revenue bridge to long-term SBSP
|
||||
|
|
|
|||
|
|
@ -10,8 +10,12 @@ agent: astra
|
|||
scope: structural
|
||||
sourcer: SpaceNews
|
||||
related_claims: ["[[SpaceX vertical integration across launch broadband and manufacturing creates compounding cost advantages that no competitor can replicate piecemeal]]", "[[launch cost reduction is the keystone variable that unlocks every downstream space industry at specific price thresholds]]"]
|
||||
supports:
|
||||
- Orbital data center governance gaps are activating faster than prior space sectors as astronomers challenged SpaceX's 1M satellite filing before the public comment period closed
|
||||
reweave_edges:
|
||||
- Orbital data center governance gaps are activating faster than prior space sectors as astronomers challenged SpaceX's 1M satellite filing before the public comment period closed|supports|2026-04-11
|
||||
---
|
||||
|
||||
# SpaceX's 1 million orbital data center satellite filing represents vertical integration at unprecedented scale creating captive Starship demand 200x larger than Starlink
|
||||
|
||||
SpaceX filed with the FCC on January 30, 2026 for authorization to deploy up to 1 million satellites dedicated to orbital AI inference processing. This represents a 20-200x scale increase over Starlink's 5,000-42,000 satellite constellation range. The filing's strategic rationale explicitly cites power and cooling constraints in terrestrial AI infrastructure and leverages near-continuous solar energy in LEO. The vertical integration logic mirrors Starlink: captive internal demand for Starship launches creates cost advantages through volume that external competitors cannot match. At 1 million satellites, the launch cadence required would dwarf any competitor's launch needs, creating a self-reinforcing cost moat. SpaceX was first to file for ODC megaconstellation authorization (one month before Blue Origin's Project Sunrise), suggesting strategic recognition of Starcloud's November 2025 demonstration as market validation. The 1M number either represents genuine demand forecasting for AI compute at orbital scale or spectrum grab strategy—both interpretations indicate this is a primary business line, not an exploratory hedge.
|
||||
SpaceX filed with the FCC on January 30, 2026 for authorization to deploy up to 1 million satellites dedicated to orbital AI inference processing. This represents a 20-200x scale increase over Starlink's 5,000-42,000 satellite constellation range. The filing's strategic rationale explicitly cites power and cooling constraints in terrestrial AI infrastructure and leverages near-continuous solar energy in LEO. The vertical integration logic mirrors Starlink: captive internal demand for Starship launches creates cost advantages through volume that external competitors cannot match. At 1 million satellites, the launch cadence required would dwarf any competitor's launch needs, creating a self-reinforcing cost moat. SpaceX was first to file for ODC megaconstellation authorization (one month before Blue Origin's Project Sunrise), suggesting strategic recognition of Starcloud's November 2025 demonstration as market validation. The 1M number either represents genuine demand forecasting for AI compute at orbital scale or spectrum grab strategy—both interpretations indicate this is a primary business line, not an exploratory hedge.
|
||||
|
|
@ -11,8 +11,10 @@ website:
|
|||
domain: space-development
|
||||
supports:
|
||||
- Breakthrough Energy Ventures' investment in Aetherflux's orbital solar infrastructure signals that space-based solar power has achieved credibility as a climate technology investment category at institutional investor level
|
||||
- Orbital data centers and space-based solar power share identical infrastructure requirements in sun-synchronous orbit creating a dual-use architecture where near-term compute revenue cross-subsidizes long-term energy transmission development
|
||||
reweave_edges:
|
||||
- Breakthrough Energy Ventures' investment in Aetherflux's orbital solar infrastructure signals that space-based solar power has achieved credibility as a climate technology investment category at institutional investor level|supports|2026-04-10
|
||||
- Orbital data centers and space-based solar power share identical infrastructure requirements in sun-synchronous orbit creating a dual-use architecture where near-term compute revenue cross-subsidizes long-term energy transmission development|supports|2026-04-11
|
||||
---
|
||||
|
||||
# Aetherflux
|
||||
|
|
|
|||
Loading…
Reference in a new issue