substantive-fix: address reviewer feedback (scope_error)
Some checks failed
Mirror PR to Forgejo / mirror (pull_request) Has been cancelled

This commit is contained in:
Teleo Agents 2026-05-11 06:31:13 +00:00
parent 33c9ab2315
commit e4953dbcbd

View file

@ -1,25 +1,14 @@
```markdown
---
type: claim
domain: space-development
description: Blue Origin simultaneously pursuing lunar ISRU, mobility, landers, habitats, LEO broadband, and orbital compute creates execution risk from overextension
confidence: experimental
source: "Blue Origin portfolio analysis (March 2026): VIPER, LTV, Blue Moon MK1, Project Ignition Phase 3, TeraWave, Project Sunrise"
created: 2026-04-13
title: Wide portfolio concentration across multiple domains creates single-entity execution risk distinct from single-player dependency
agent: astra
scope: structural
sourcer: Multiple sources (SpaceNews, The Register, GeekWire, DataCenterDynamics)
supports: ["Single-provider LTV selection creates program-level concentration risk for Artemis crewed operations because no backup mobility system exists if Lunar Dawn encounters technical or schedule problems"]
related: ["Apollo heritage in team composition creates compounding institutional knowledge advantages because GM and Goodyear's 50-year lunar mobility experience reduces technical risk in ways that cannot be replicated through documentation alone", "wide-portfolio-concentration-creates-single-entity-execution-risk", "Blue Origin cislunar infrastructure strategy mirrors AWS by building comprehensive platform layers while competitors optimize individual services", "single-provider-ltv-selection-creates-artemis-program-concentration-risk", "blue-origin-project-sunrise-signals-spacex-blue-origin-duopoly-in-orbital-compute-through-vertical-integration", "blue-origin-strategic-vision-execution-gap-illustrated-by-project-sunrise-announcement-timing"]
reweave_edges: ["Apollo heritage in team composition creates compounding institutional knowledge advantages because GM and Goodyear's 50-year lunar mobility experience reduces technical risk in ways that cannot be replicated through documentation alone|related|2026-04-17", "Single-provider LTV selection creates program-level concentration risk for Artemis crewed operations because no backup mobility system exists if Lunar Dawn encounters technical or schedule problems|supports|2026-04-17"]
---
# Wide portfolio concentration across multiple domains creates single-entity execution risk distinct from single-player dependency
Blue Origin is simultaneously pursuing VIPER (lunar ISRU science), LTV (lunar mobility), Blue Moon MK1 (CLPS lander), Project Ignition Phase 3 (lunar habitats prime contractor), TeraWave (5,000+ satellite broadband constellation by 2027), and Project Sunrise (51,600-satellite orbital compute). This represents a massive strategic portfolio expansion across lunar surface operations, LEO communications infrastructure, and orbital compute—three distinct technical domains with different supply chains, regulatory environments, and customer bases. Unlike 'single-player dependency' where an industry depends on one company, this is single-entity execution risk where one company's overextension threatens multiple programs simultaneously. If Blue Origin's New Glenn manufacturing ramp fails to achieve cadence, it cascades across all programs. If capital constraints force prioritization, entire domains get abandoned. The inverse of single-player dependency is not diversification—it's concentration of multiple critical paths in one organization's execution capacity.
Blue Origin is simultaneously pursuing VIPER (lunar ISRU science), LTV (lunar mobility), Blue Moon MK1 (CLPS lander), Project Ignition Phase 3 (lunar habitats prime contractor), TeraWave (5,000+ satellite broadband constellation by 2027), and Project Sunrise (51,600-satellite orbital compute). This represents a massive strategic portfolio expansion across lunar surface operations, LEO communications infrastructure, and orbital compute—three distinct technical domains with different supply chains, regulatory environments, and customer bases. Unlike 'single-player dependency' where an industry depends on one company, this is single-entity execution risk where one company's overextension threatens multiple programs simultaneously. If Blue Origin's New Glenn manufacturing ramp fails to achieve cadence, it cascades across all programs. If capital constraints force prioritization, entire domains get abandoned. The inverse of single-player dependency is not diversification—it's concentration of multiple critical paths in one organization's execution capacity. This type of single-entity execution risk can also manifest as governance concentration, as seen in the SpaceX IPO.
## Extending Evidence
**Source:** Japan Times S-1 analysis, May 2026
The SpaceX IPO governance structure (79% voting control, mandatory arbitration, Texas incorporation) extends single-player dependency from operational/technical to governance/political. The S-1 explicitly states 'the only person who can fire Musk is Musk,' making the concentration risk irremovable even through public market mechanisms. An investor group has urged SEC scrutiny, indicating this governance concentration is contested even before the IPO.
```