diff --git a/domains/space-development/sun-synchronous-orbit-enables-continuous-solar-power-for-orbital-compute-infrastructure.md b/domains/space-development/sun-synchronous-orbit-enables-continuous-solar-power-for-orbital-compute-infrastructure.md
new file mode 100644
index 00000000..5725d3d8
--- /dev/null
+++ b/domains/space-development/sun-synchronous-orbit-enables-continuous-solar-power-for-orbital-compute-infrastructure.md
@@ -0,0 +1,17 @@
+---
+type: claim
+domain: space-development
+description: Blue Origin's Project Sunrise uses sun-synchronous orbit (500-1,800 km) specifically to optimize for power availability rather than communications coverage
+confidence: experimental
+source: Blue Origin FCC Filing SAT-LOA-20260319-00032, March 19, 2026
+created: 2026-04-04
+title: Sun-synchronous orbit architecture enables continuous solar power exposure for orbital compute infrastructure by maintaining constant sun angle throughout the orbit
+agent: astra
+scope: functional
+sourcer: Blue Origin / FCC Filing
+related_claims: ["[[power is the binding constraint on all space operations because every capability from ISRU to manufacturing to life support is power-limited]]"]
+---
+
+# Sun-synchronous orbit architecture enables continuous solar power exposure for orbital compute infrastructure by maintaining constant sun angle throughout the orbit
+
+Most megaconstellations (Starlink, Project Kuiper) use polar or inclined orbits optimized for global communications coverage. Blue Origin's Project Sunrise explicitly chooses sun-synchronous orbit (500-1,800 km altitude) for its 51,600 satellite orbital data center constellation. Sun-synchronous orbit maintains a constant angle relative to the sun throughout the orbit, providing continuous solar exposure without eclipse periods. This is a power architecture, not a communications architecture. The FCC filing explicitly frames the purpose as 'relocating energy and water-intensive AI compute away from terrestrial data centers' — the orbital design directly addresses the power constraint. For compute workloads (unlike communications), continuous power availability is the primary design driver because compute operations cannot be interrupted during eclipse periods without significant performance degradation. This represents a novel application of sun-synchronous orbit: previous uses focused on Earth observation (consistent lighting for imaging), but Project Sunrise uses it as an orbital power infrastructure solution for continuous high-power operations.
diff --git a/domains/space-development/vertical-integration-solves-demand-threshold-problem-through-captive-internal-demand.md b/domains/space-development/vertical-integration-solves-demand-threshold-problem-through-captive-internal-demand.md
new file mode 100644
index 00000000..1df35893
--- /dev/null
+++ b/domains/space-development/vertical-integration-solves-demand-threshold-problem-through-captive-internal-demand.md
@@ -0,0 +1,17 @@
+---
+type: claim
+domain: space-development
+description: SpaceX used Starlink to create captive Falcon 9 demand; Blue Origin's Project Sunrise attempts the same pattern with New Glenn and orbital data centers
+confidence: experimental
+source: Blue Origin FCC Filing SAT-LOA-20260319-00032, March 19, 2026
+created: 2026-04-04
+title: Vertical integration solves the demand threshold problem in commercial space by creating captive internal demand rather than waiting for independent commercial markets to emerge
+agent: astra
+scope: structural
+sourcer: Blue Origin / FCC Filing
+related_claims: ["[[SpaceX vertical integration across launch broadband and manufacturing creates compounding cost advantages that no competitor can replicate piecemeal]]"]
+---
+
+# Vertical integration solves the demand threshold problem in commercial space by creating captive internal demand rather than waiting for independent commercial markets to emerge
+
+The demand threshold problem in commercial space is that launch providers need high cadence to achieve cost reduction through economies of scale, but external commercial demand is insufficient to sustain that cadence. SpaceX solved this through vertical integration: Starlink created captive internal demand for Falcon 9 launches (5,000+ satellites deployed), enabling the launch cadence necessary for cost reduction and operational refinement. Blue Origin's Project Sunrise FCC filing (March 19, 2026) represents an explicit attempt to replicate this mechanism: 51,600 orbital data center satellites would create massive captive demand for New Glenn launches, bypassing the need to wait for independent commercial customers. The filing comes during a period when Blue Origin faces cadence challenges (NG-3's 5th consecutive non-launch session), suggesting capital constraints from insufficient external demand. The strategic logic is identical to SpaceX/Starlink: create your own demand to achieve the operational tempo required for cost competitiveness. This is not gradual market development but deliberate architectural integration to solve a structural chicken-and-egg problem.