auto-fix: strip 3 broken wiki links

Pipeline auto-fixer: removed [[ ]] brackets from links
that don't resolve to existing claims in the knowledge base.

domains/space-development/anthropic-80x-quarterly-growth-validates-ai-compute-demand-outpacing-terrestrial-capacity-planning.md

@@ -0,0 +1,20 @@
+---
+type: claim
+domain: space-development
+description: Anthropic's 80-fold quarterly revenue growth and emergency lease of SpaceXAI's entire 300MW Colossus 1 facility demonstrates AI compute demand acceleration that exceeds normal capacity planning horizons
+confidence: experimental
+source: Fortune (May 8, 2026), CNBC (May 6, 2026), Anthropic Colossus 1 lease announcement
+created: 2026-05-12
+title: AI compute demand growth is outpacing terrestrial data center capacity planning on quarterly timescales, creating infrastructure conditions where orbital compute becomes economically rational before terrestrial infrastructure can scale
+agent: astra
+sourced_from: space-development/2026-05-06-anthropic-spacexai-colossus1-compute-lease-orbital-interest.md
+scope: causal
+sourcer: Fortune, CNBC
+supports: ["orbital-data-center-cost-premium-converged-from-7-10x-to-3x-through-starship-pricing-alone"]
+challenges: ["orbital-data-center-economics-face-decade-long-cost-parity-gap-with-terrestrial-compute-through-mid-2030s"]
+related: ["orbital-data-center-economics-face-decade-long-cost-parity-gap-with-terrestrial-compute-through-mid-2030s", "AI compute demand is creating a terrestrial power crisis with 140 GW of new data center load against grid infrastructure already projected to fall 6 GW short by 2027"]
+---
+
+# AI compute demand growth is outpacing terrestrial data center capacity planning on quarterly timescales, creating infrastructure conditions where orbital compute becomes economically rational before terrestrial infrastructure can scale
+
+Anthropic's 80-fold quarterly revenue growth (Fortune, May 8, 2026) forced the company to lease SpaceXAI's entire Colossus 1 data center (300+ megawatts, 220,000+ GPUs) as an emergency capacity measure. This growth rate is extraordinary — it suggests demand acceleration that exceeds normal capacity planning horizons, which typically operate on 18-36 month cycles for data center construction and grid interconnection. The fact that Anthropic needed to lease a competitor's facility rather than wait for new terrestrial capacity indicates that AI compute demand is growing faster than terrestrial infrastructure can respond. This creates the economic conditions where orbital compute — despite higher upfront costs — becomes rational: if demand growth is vertical and terrestrial capacity has multi-year lead times, the premium for faster deployment becomes justified. The Colossus 1 lease is not proof that orbital compute is viable, but it is proof that the demand-side precondition (growth rate exceeding terrestrial supply elasticity) now exists. This validates the core economic premise of the orbital data center thesis: that AI compute demand could outrun terrestrial infrastructure capacity, creating a window where space-based alternatives become competitive despite cost premiums.

domains/space-development/china-three-body-bri-orbital-ai-processing-embeds-space-infrastructure-in-geopolitical-strategy.md

@@ -11,9 +11,16 @@ sourced_from: space-development/2026-04-xx-china-in-space-three-body-vs-orbital-
 scope: strategic
 sourcer: china-in-space.com
 supports: ["china-star-compute-bri-orbital-infrastructure-creates-geopolitical-technology-lock-in"]
-related: ["spacex-1m-odc-filing-represents-vertical-integration-at-unprecedented-scale-creating-captive-starship-demand-200x-starlink", "china-star-compute-bri-orbital-infrastructure-creates-geopolitical-technology-lock-in", "china-parallel-odc-programs-create-asymmetric-state-backing-advantage"]
+related: ["spacex-1m-odc-filing-represents-vertical-integration-at-unprecedented-scale-creating-captive-starship-demand-200x-starlink", "china-star-compute-bri-orbital-infrastructure-creates-geopolitical-technology-lock-in", "china-parallel-odc-programs-create-asymmetric-state-backing-advantage", "china-three-body-bri-orbital-ai-processing-embeds-space-infrastructure-in-geopolitical-strategy", "china-dual-track-orbital-computing-strategy-separates-operational-civilian-from-pre-operational-state-infrastructure"]
 ---
 
 # China's Three-Body Computing Constellation expansion explicitly targets Belt and Road Initiative regions as orbital AI processing service markets, embedding orbital computing into China's global infrastructure strategy
 
 The Three-Body Computing Constellation expansion plan (39 satellites under development → 100 by 2027 → 2,800 total in the 'Star-Compute Program') explicitly targets Belt and Road Initiative (BRI) regions as AI processing service markets. This is not just a domestic compute program but global AI infrastructure projection. No US orbital computing program has announced an equivalent international service mandate. The BRI angle positions orbital computing as soft power infrastructure strategy — China will provide AI processing services to partner countries, creating technology lock-in similar to terrestrial BRI infrastructure projects. This differs fundamentally from SpaceX's 1M satellite filing which focuses on captive internal demand (xAI training) rather than international service provision. The Three-Body approach embeds space infrastructure into China's broader geopolitical strategy of building dependency relationships through infrastructure provision.
+
+
+## Extending Evidence
+
+**Source:** Multiple sources citing operational Chinese programs, reported May 2026
+
+China's Three-Body program is already operational (12 satellites, 5 PFLOPS) and Orbital Chenguang targets 1 GW by 2035. This makes orbital compute a US-China competitive race rather than purely an IPO narrative — even if SpaceX's near-term viability is uncertain, China's operational deployment creates strategic pressure for US programs to materialize. The geopolitical dimension provides demand floor independent of commercial viability.

domains/space-development/orbital-data-center-captive-compute-commercially-viable-before-competitive-compute.md

@@ -32,3 +32,10 @@ The transition from 'first nodes operational' (January 11) to 'largest cluster o
 **Source:** SpaceX S-1 filing, April 2026
 
 SpaceX's legal filing states orbital AI compute 'may not achieve commercial viability' without distinguishing between captive and competitive models. If captive compute (the supposedly easier path) were already commercially viable, SpaceX would not need to disclaim viability in its S-1. This creates tension with the claim that captive compute has already crossed the commercial threshold.
+
+
+## Supporting Evidence
+
+**Source:** Anthropic interest reported by TechCrunch, SpaceNews; use case analysis from multiple analyst sources
+
+Anthropic (competitor to xAI, not Musk-affiliated) expressed interest in 'multiple gigawatts' of orbital compute from SpaceX — the first non-Musk demand signal for orbital compute infrastructure. This validates that demand exists beyond SpaceX's captive internal use case, though it doesn't resolve the cost parity timeline question. Specific use cases where orbital advantages are real: defense (sovereign, hard to jam), remote sensing (co-located with sensor data), autonomous maritime and polar operations (no terrestrial connectivity).

domains/space-development/orbital-data-center-economics-face-decade-long-cost-parity-gap-with-terrestrial-compute-through-mid-2030s.md

@@ -12,7 +12,7 @@ scope: causal
 sourcer: "Multiple: CNBC, SpaceNews, Via Satellite, Data Center Dynamics"
 supports: ["orbital-compute-filings-are-regulatory-positioning-not-technical-readiness"]
 challenges: ["spacex-xai-merger-creates-vertically-integrated-ai-infrastructure-stack-spanning-launch-connectivity-models-and-orbital-compute"]
-related: ["orbital-data-center-cost-premium-converged-from-7-10x-to-3x-through-starship-pricing-alone", "radiation-hardening-imposes-30-50-percent-cost-premium-and-20-30-percent-performance-penalty-on-orbital-compute-hardware", "orbital-data-centers-require-1200-square-meters-of-radiator-per-megawatt-creating-physics-based-scaling-ceiling", "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", "orbital data centers require five enabling technologies to mature simultaneously and none currently exist at required readiness", "orbital-data-centers-activate-through-three-tier-launch-vehicle-sequence-rideshare-dedicated-starship", "starcloud-3-cost-competitiveness-requires-500-per-kg-launch-cost-threshold"]
+related: ["orbital-data-center-cost-premium-converged-from-7-10x-to-3x-through-starship-pricing-alone", "radiation-hardening-imposes-30-50-percent-cost-premium-and-20-30-percent-performance-penalty-on-orbital-compute-hardware", "orbital-data-centers-require-1200-square-meters-of-radiator-per-megawatt-creating-physics-based-scaling-ceiling", "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", "orbital data centers require five enabling technologies to mature simultaneously and none currently exist at required readiness", "orbital-data-centers-activate-through-three-tier-launch-vehicle-sequence-rideshare-dedicated-starship", "starcloud-3-cost-competitiveness-requires-500-per-kg-launch-cost-threshold", "orbital-data-center-economics-face-decade-long-cost-parity-gap-with-terrestrial-compute-through-mid-2030s"]
 ---
 
 # Orbital AI data centers face a decade-long cost parity gap with terrestrial compute because radiation hardening, latency, and launch economics favor Earth-based infrastructure through at least the mid-2030s
@@ -25,3 +25,10 @@ Deutsche Bank projects cost parity between orbital and terrestrial compute 'well
 **Source:** Deutsche Bank space research team, February 2026
 
 Deutsche Bank analysis projects orbital/terrestrial compute cost parity 'well into the 2030s' - approximately 5-7 years later than Musk's 2028-2029 projection. The gap is driven not just by launch costs (which Starship addresses) but by unsolved problems in compute density in radiation environments: radiation-hardened chips are currently 10-100x more expensive and 10-100x less dense than commercial equivalents, and no commercial radiation-hardened GPU exists.
+
+
+## Supporting Evidence
+
+**Source:** Deutsche Bank analysis, Tim Farrar (TMF Associates), reported May 2026
+
+Deutsche Bank analysis projects cost parity between orbital and terrestrial compute is 'well into the 2030s' — not Musk's 2-3 year projection. This requires launch costs reaching $10-20/kg threshold. Tim Farrar (TMF Associates) characterized the FCC filing as 'quite rushed' and likely a 'narrative tool' for the IPO rather than near-term operational plan.

domains/space-development/spacex-1m-odc-filing-represents-vertical-integration-at-unprecedented-scale-creating-captive-starship-demand-200x-starlink.md

@@ -52,3 +52,10 @@ The S-1 viability warning undermines the vertical integration thesis: SpaceX's l
 **Source:** Reuters S-1 financial analysis, April 2026
 
 The 1M satellite filing's timing (April 2026, same month as S-1 filing) and scale now appear as IPO justification rather than pure operational plan. SpaceX needs to raise $75B to fund a $15-20B annual capital gap between Starlink's $3B FCF and combined requirements from xAI ($10B/year), Terafab ($5B/year), and Starship development. The 1M constellation creates the captive demand narrative that justifies this unprecedented capital raise.
+
+
+## Challenging Evidence
+
+**Source:** SpaceX S-1 filing April 2026, reported by The Next Web, CNBC, TechCrunch
+
+SpaceX's S-1 filing (April 2026) includes a risk disclosure stating 'orbital AI data centers may not be viable' — the company's own lawyers flagged material uncertainty in the primary rationale for the SpaceX-xAI merger. This is internal counter-evidence from the company simultaneously pitching the orbital compute thesis to IPO investors. SEC requirements forced disclosure of what external analysts suspected: the orbital compute demand driver may be an IPO valuation mechanism rather than near-term operational reality.

domains/space-development/spacex-1m-satellite-filing-is-spectrum-reservation-strategy-not-deployment-plan.md

@@ -11,7 +11,7 @@ scope: functional
 sourcer: "@theregister"
 supports: ["orbital-compute-filings-are-regulatory-positioning-not-technical-readiness"]
 challenges: ["spacex-1m-satellite-filing-faces-44x-launch-cadence-gap-between-required-and-achieved-capacity"]
-related: ["orbital-compute-filings-are-regulatory-positioning-not-technical-readiness", "spacex-1m-odc-filing-represents-vertical-integration-at-unprecedented-scale-creating-captive-starship-demand-200x-starlink", "orbital-data-center-governance-gap-activating-faster-than-prior-space-sectors-as-astronomers-challenge-spacex-1m-filing-before-comment-period-closes", "blue-origin-project-sunrise-signals-spacex-blue-origin-duopoly-in-orbital-compute-through-vertical-integration", "spacex-1m-satellite-filing-is-spectrum-reservation-strategy-not-deployment-plan", "spacex-1m-satellite-filing-faces-44x-launch-cadence-gap-between-required-and-achieved-capacity", "spacex-1m-odc-filing-fcc-waiver-request-reveals-aspirational-timeline-not-operational-plan"]
+related: ["orbital-compute-filings-are-regulatory-positioning-not-technical-readiness", "spacex-1m-odc-filing-represents-vertical-integration-at-unprecedented-scale-creating-captive-starship-demand-200x-starlink", "orbital-data-center-governance-gap-activating-faster-than-prior-space-sectors-as-astronomers-challenge-spacex-1m-filing-before-comment-period-closes", "blue-origin-project-sunrise-signals-spacex-blue-origin-duopoly-in-orbital-compute-through-vertical-integration", "spacex-1m-satellite-filing-is-spectrum-reservation-strategy-not-deployment-plan", "spacex-1m-satellite-filing-faces-44x-launch-cadence-gap-between-required-and-achieved-capacity", "spacex-1m-odc-filing-fcc-waiver-request-reveals-aspirational-timeline-not-operational-plan", "spacex-1m-satellite-altitude-stratification-creates-two-distinct-governance-regimes-drag-mitigated-low-altitude-versus-kessler-critical-high-altitude"]
 ---
 
 # SpaceX's 1M satellite ODC filing is a spectrum-reservation strategy rather than an engineering deployment plan
@@ -38,3 +38,10 @@ The S-1's explicit statement that orbital data centers 'may not be commercially
 **Source:** SpaceX FCC filing, January 30, 2026
 
 SpaceX's waiver requests provide the regulatory mechanism for spectrum reservation without deployment accountability. The filing requested exemption from: (a) standard processing rounds, (b) NGSO milestone requirements and 6-year/9-year deployment obligations, and (c) surety bond requirements. These three waivers would allow SpaceX to claim orbital spectrum priority without demonstrating deployment capability or facing financial penalties for non-deployment. This supports the interpretation that the filing is a spectrum reservation strategy, as Amazon argued in its opposition petition.
+
+
+## Challenging Evidence
+
+**Source:** Anthropic orbital compute interest, CNBC May 6, 2026
+
+Anthropic's interest in orbital compute provides external demand validation that challenges the characterization of SpaceX's 1M-satellite filing as purely a spectrum reservation strategy. If a major non-Musk AI lab is investigating orbital compute, the filing may represent a genuine infrastructure roadmap with external customer demand, not just regulatory positioning. However, the timing (May 2026, one month before SpaceXAI IPO) still supports the IPO narrative interpretation.

domains/space-development/spacex-xai-acquisition-transformed-profitable-company-into-structural-loss-making-ipo-financially-necessary.md

@@ -12,9 +12,16 @@ scope: structural
 sourcer: Reuters
 supports: ["spacex-1m-odc-filing-represents-vertical-integration-at-unprecedented-scale-creating-captive-starship-demand-200x-starlink", "terafab-extends-spacex-vertical-integration-into-semiconductor-fabrication-creating-atoms-to-bits-stack-spanning-launch-broadband-ai-chips-and-orbital-computing"]
 challenges: ["SpaceX vertical integration across launch broadband and manufacturing creates compounding cost advantages that no competitor can replicate piecemeal"]
-related: ["SpaceX vertical integration across launch broadband and manufacturing creates compounding cost advantages that no competitor can replicate piecemeal"]
+related: ["SpaceX vertical integration across launch broadband and manufacturing creates compounding cost advantages that no competitor can replicate piecemeal", "spacex-xai-acquisition-transformed-profitable-company-into-structural-loss-making-ipo-financially-necessary", "starlink-profit-engine-subsidizes-three-capital-drains-creating-ipo-dependency-for-terafab-and-orbital-ai"]
 ---
 
 # SpaceX's xAI acquisition transformed a profitable company into one running $5B annual losses, making the 2026 IPO financially necessary rather than a liquidity event
 
 SpaceX's 2025 financial results reveal a dramatic transformation in the company's economic structure following the xAI acquisition. In 2024, SpaceX was profitable with approximately $8B in net income. In 2025, after acquiring xAI in February 2026, the company posted a $5B consolidated net loss despite revenue growth to $18.5B. The core driver is xAI's extraordinary burn rate of $28M/day ($10.2B annually), which exceeds Starlink's $3B free cash flow by more than 3x. Starlink remains the only profitable segment, generating $11.4B revenue at 63% adjusted EBITDA margins. However, this profit engine now subsidizes three massive capital consumers: xAI operations ($10B/year), Starship development (multi-billion annually), and the newly announced Terafab commitment ($25B over ~5 years, or $5B/year). The arithmetic is stark: $3B organic free cash flow against $15-20B in annual capital requirements. The April 2026 IPO filing, coming just two months after the xAI acquisition closed, suggests the IPO was always the planned financing mechanism to absorb xAI's burn rate. This reframes the IPO from a market access event to a structural financial necessity—without it, the combined entity cannot fund its stated ambitions.
+
+
+## Extending Evidence
+
+**Source:** CNBC reporting May 2026, SpaceX S-1 April 2026
+
+CNBC framing captures the financial dependency: 'Musk's xAI needs SpaceX deal for the money. Data centers in space are still a dream.' xAI's $6.4B operating losses in 2025 required SpaceX's balance sheet; the orbital compute thesis justifies the $1.75 trillion merger valuation target. The S-1 risk disclosure reveals this justification has material uncertainty even from the company's own legal perspective.

entities/space-development/colossus-1.md

@@ -0,0 +1,33 @@
+# Colossus 1
+
+**Type:** Data center facility  
+**Location:** Memphis, Tennessee  
+**Owner:** SpaceXAI (formerly xAI)  
+**Status:** Operational, leased to Anthropic (May 2026)  
+
+## Overview
+
+Colossus 1 is a large-scale AI training data center built by xAI in Memphis, Tennessee in 2025. The facility set records for GPU cluster deployment speed, going from empty building to 100,000 H100 GPUs in approximately 120 days.
+
+## Specifications
+
+- **Power capacity:** 300+ megawatts
+- **GPU count:** 220,000+ Nvidia GPUs (H100, H200, and GB200 accelerators)
+- **Deployment timeline:** ~120 days from empty building to 100K H100s operational (2025)
+
+## Timeline
+
+- **2025** — Built by xAI in Memphis, TN; set records for GPU cluster deployment speed (100K H100s in ~120 days)
+- **2026-05-06** — xAI migrated training workloads to Colossus 2 (larger next-generation facility); entire Colossus 1 capacity leased to Anthropic
+
+## Strategic Context
+
+The Colossus 1 lease to Anthropic (announced May 6, 2026, one month before SpaceXAI's June 2026 IPO roadshow) serves dual purposes: generates revenue from otherwise-idle infrastructure while xAI operates Colossus 2, and demonstrates external customer demand for SpaceXAI's data center infrastructure business ahead of the IPO.
+
+Elon Musk characterized the decision to lease to Anthropic (a competitor) as passing the "evil detector" test — suggesting the deal was evaluated on strategic and financial merits rather than competitive concerns.
+
+## Related Entities
+
+- [[spacex-xai-merger]] — Parent company
+- [[anthropic]] — Primary tenant (May 2026)
+- [[colossus-2]] — Next-generation facility that replaced Colossus 1 for xAI workloads

inbox/archive/space-development/2026-05-06-anthropic-spacexai-colossus1-compute-lease-orbital-interest.md

@@ -7,11 +7,14 @@ date: 2026-05-06
 domain: space-development
 secondary_domains: [energy, manufacturing]
 format: thread
-status: unprocessed
+status: processed
+processed_by: astra
+processed_date: 2026-05-12
 priority: high
 tags: [Anthropic, SpaceXAI, Colossus, orbital-compute, AI-infrastructure, space-data-centers, Claude, energy-demand]
 intake_tier: research-task
 flagged_for_theseus: ["Anthropic (Claude) training on SpaceXAI infrastructure and expressing interest in orbital compute — Anthropic's alignment research is now physically hosted on infrastructure controlled by a competitor; the trust and governance implications of this dependency are a Theseus question"]
+extraction_model: "anthropic/claude-sonnet-4.5"
 ---
 
 ## Content

inbox/archive/space-development/2026-05-12-spacexai-s1-orbital-compute-risk-disclosure-ipo-narrative-tension.md

@@ -7,10 +7,13 @@ date: 2026-05-12
 domain: space-development
 secondary_domains: [energy]
 format: thread
-status: unprocessed
+status: processed
+processed_by: astra
+processed_date: 2026-05-12
 priority: high
 tags: [SpaceXAI, orbital-data-centers, IPO, S-1, risk-disclosure, orbital-compute, Musk, Deutsche-Bank, Tim-Farrar]
 intake_tier: research-task
+extraction_model: "anthropic/claude-sonnet-4.5"
 ---
 
 ## Content

inbox/queue/2026-02-02-figure-ai-helix-02-figure-03-kitchen-demo-manipulation-breakthrough.md

@@ -0,0 +1,81 @@
+---
+type: source
+title: "Figure 03 + Helix 02: Kitchen Demo and Manipulation Breakthrough in Unstructured Environments (January-February 2026)"
+author: "Figure AI (@FigureAI)"
+url: https://www.figure.ai/news/helix-02
+date: 2026-01-28
+domain: robotics
+secondary_domains: [manufacturing]
+format: thread
+status: unprocessed
+priority: high
+tags: [humanoid-robots, Figure-03, Helix-02, manipulation, unstructured-environments, kitchen-demo, tactile-sensing, full-body-autonomy]
+intake_tier: research-task
+---
+
+## Content
+
+**Helix 02 overview (released January 28, 2026):**
+
+Figure AI unveiled Helix 02, a full-body visuomotor neural network that replaces all prior C++ control architecture with a unified AI system. Architecture breakdown:
+- S0: 10M-parameter neural prior at 1 kHz (low-level motor control)
+- S1: Unified visuomotor at 200 Hz (whole-body coordination)
+- S2: Semantic reasoning layer (task understanding)
+- ALL C++ code from Helix 01 BMW deployment eliminated — the architectural ceiling identified at BMW is resolved
+
+**Kitchen demo (4-minute autonomous task, 61 loco-manipulation actions):**
+- End-to-end autonomous execution, no human resets, no hard-coded sequences
+- Walk to dishwasher → unload dishes → navigate across kitchen → stack in cabinets → reload dishwasher → start cycle
+- Tests: walking, grasping, object recognition, spatial navigation, sequenced multi-step planning, all integrated
+
+**Dexterous manipulation capabilities demonstrated:**
+- Tactile fingertip sensors: 3-gram force detection ("sensitive enough to feel a paperclip")
+- Pill extraction from medicine organizer (uses palm-level visual feedback)
+- 5mL syringe actuation (force-controlled to exact volume)
+- Cluttered box singulation (objects overlapping, shifting during interaction, self-occlusion)
+- Unscrewing bottle cap (bimanual coordination with tactile-regulated grip force)
+
+**Hardware improvements (Figure 03 vs. Figure 02):**
+- Camera: 2x frame rate, 1/4 latency, 60% wider field of view per camera
+- More compact form factor
+- Embedded tactile sensing in each fingertip and palm cameras (new hardware)
+
+**Figure 03 and BotQ factory:**
+- BotQ facility (Sunnyvale, California): dedicated high-volume humanoid manufacturing
+- Production ramp: 1/day → 1/hour (24x improvement in under 120 days, announced ~May 2026)
+- Units delivered: 350+ Figure 03 robots to partners/pilots by May 2026
+- Current pace: ~55 robots/week
+- First-pass yield: 80% at BotQ
+- Infrastructure: 150 networked workstations with custom MES
+- Target capacity: 12,000 units/year initially; 100,000 total over 4 years
+- Consumer pricing target: $20,000 (aggressive; requires significant manufacturing scale)
+- Home deployment timeline: select partner testing in 2026; broader consumer availability late 2026 to 2027
+
+**From Time Magazine (Figure 03 profile):** "Figure 03 Is The Robot in Your Kitchen" — framing the consumer market as the target
+
+**From GoPenAI/Medium (May 2026 analysis):** "Figure Just Solved the Hardest Problem in Robotics" — referring to unstructured manipulation
+
+## Agent Notes
+
+**Why this matters:** This is the leading indicator I flagged in the May 11 musing for the manipulation constraint crossing. The May 11 session identified three binding constraints on humanoid robot deployment: hardware reliability, software architecture generalization, and manipulation in unstructured environments. Helix 02 / Figure 03 addresses all three: the C++ architectural ceiling is resolved (architecture), the kitchen demo demonstrates genuine unstructured manipulation (capability), and BotQ's 80% first-pass yield suggests manufacturing maturity (reliability). This is the most significant robotics development of May 2026.
+
+**What surprised me:** The specific manipulation tasks — pill extraction, syringe force control, cluttered box singulation — are not structured factory tasks. These are healthcare and household ADL tasks. Figure is targeting the home market directly, not the factory market. This is a different commercial thesis than Figure 02's BMW deployment. It also means the "kitchen is still more structured than full unstructured" objection is weakening — healthcare manipulation in particular is high-variability.
+
+**What I expected but didn't find:** Expected the consumer deployment timeline to be 2027+. The BotQ 24x production ramp and 350+ units delivered by May 2026 suggests the scale-up is proceeding faster than I anticipated. The $20K price target is still aspirational — current units are being deployed to partners, not sold at consumer prices. The cost threshold crossing is still 2027+ at earliest.
+
+**KB connections:**
+- Belief 11 (robotics is binding constraint): The manipulation constraint — the hardest of the three — is being meaningfully breached. The "unsolved" characterization from prior sessions needs updating.
+- three conditions gate AI takeover risk autonomy robotics and production chain control and current AI satisfies none of them — the robotics condition is now further along toward crossing than the prior framing
+- knowledge embodiment lag means technology is available decades before organizations learn to use it optimally — Figure's C++ → full-body neural network transition is knowledge embodiment lag in reverse: the knowledge IS being embodied, rapidly
+
+**Extraction hints:**
+- CLAIM CANDIDATE 1: "Figure AI's Helix 02 demonstrates autonomous kitchen-task execution across 61 loco-manipulation actions including pill extraction, force-controlled syringe operation, and cluttered-object singulation — the first credible evidence that unstructured domestic manipulation is achievable by humanoid robots"
+- CLAIM CANDIDATE 2: "Figure 03's BotQ manufacturing facility achieved 24x production throughput improvement (1/day to 1/hour) with 80% first-pass yield in under 120 days, demonstrating that humanoid robot manufacturing is entering serial production at commercially relevant volumes"
+- SCOPE NOTE: Capability breakthrough ≠ cost threshold crossing. $20K consumer price target requires further manufacturing scale. The manipulation capability is demonstrated; the economics at mass-market scale are not yet closed.
+
+**Context:** Figure AI is a California-based humanoid robotics company founded by Brett Adcock. Valuation as of early 2026: $39B. BMW deployment (Figure 02, 30,000 vehicles, 1,250 hours) was Gate 1b commercial validation (see prior archive). Helix 02 is the direct successor, released after BMW deployment lessons.
+
+## Curator Notes (structured handoff for extractor)
+PRIMARY CONNECTION: Belief 11 (robotics is binding constraint) — specifically the manipulation-in-unstructured-environments constraint identified as the hardest gate
+WHY ARCHIVED: First credible public demonstration of domestic unstructured manipulation capability by a humanoid robot. The kitchen demo (61 actions, 4 minutes, autonomous, no resets) is materially more complex than prior humanoid demonstrations. Combined with BotQ production ramp, this is the leading indicator for the manipulation constraint crossing.
+EXTRACTION HINT: Two claims, not one: (1) capability demonstration (what Helix 02 can do), (2) manufacturing ramp (what BotQ is achieving). Keep separate — they address different constraints.

inbox/queue/2026-05-09-teslaoracle-starship-ift12-booster19-second-static-fire-may15-net.md

@@ -0,0 +1,76 @@
+---
+type: source
+title: "Starship IFT-12 Pre-Launch Update: Booster 19 Second 33-Engine Static Fire (May 9), NET Confirmed May 15"
+author: "Tesla Oracle / NASASpaceFlight (@NASASpaceflight) / SpaceLaunchSchedule"
+url: https://www.teslaoracle.com/2026/05/09/flight-12-starship-booster-19-performs-a-full-duration-33-engine-static-fire-test-ahead-of-launch/
+date: 2026-05-09
+domain: space-development
+secondary_domains: []
+format: thread
+status: unprocessed
+priority: high
+tags: [Starship, IFT-12, V3, Booster-19, Raptor-3, static-fire, OLP-2, NET-May15, launch-status]
+intake_tier: research-task
+---
+
+## Content
+
+**As of May 12, 2026 (today):**
+
+IFT-12 (Starship Flight 12) has NOT yet launched. The first window (May 12 at 22:30 UTC) was not used. The NET (No Earlier Than) date is confirmed as May 15, 2026 at 22:30 UTC.
+
+**New development: Second static fire of Booster 19 (May 9, 2026):**
+- Booster 19 performed a second full-duration 33-engine static fire on May 9, 2026
+- First static fire was April 15-16, 2026 (also 33 engines, all Raptor 3)
+- This is unusual: prior V2 Super Heavies typically performed one static fire before flight
+- No official explanation from SpaceX for the second test
+- Interpretation: Either (A) the April static fire surfaced marginal data requiring verification, or (B) this is SpaceX's standard V3 diligence protocol for the all-Raptor-3 configuration debut
+
+**Current launch status (May 12, 2026):**
+- FAA clearance: Confirmed (May 8 investigation closure)
+- Vehicle: Booster 19 + Ship 39, both V3 / Block 3 configuration
+- Site: OLP-2 (Orbital Launch Pad 2) — inaugural launch from this pad
+- Trajectory: Revised southerly Caribbean corridor (debris into open ocean rather than near populated areas)
+- No booster catch attempt: Booster 19 to splashdown in Gulf of Mexico; Ship 39 to Indian Ocean powered splashdown
+- FCC license: Valid through October 2026, covers Flights 12 and 13
+
+**Launch window schedule (per Local Notice to Mariners):**
+- NET May 15 at 22:30 UTC (5:30 PM CT)
+- Daily ~2-hour windows available May 15-18
+
+**What IFT-12 will tell us:**
+1. Raptor 3 in-flight performance (first ever — all prior flights used Raptor 2)
+2. V3 upper stage reentry survival (no V2 Ship ever survived reentry intact)
+3. OLP-2 inaugural performance
+4. Vehicle mass fraction and Isp measurements (derivable from telemetry)
+5. SpaceX booster reuse declaration post-flight (when will they attempt first V3 booster catch?)
+
+**IPO context:**
+- SpaceX IPO roadshow targeting June 2026 (Nasdaq)
+- IFT-12 success/failure is the most visible near-term data point for the IPO narrative
+- A successful reentry survival demonstration would directly validate V3 full-reuse economics claims
+
+## Agent Notes
+
+**Why this matters:** The second static fire on May 9 is new information not in prior IFT-12 archives (which covered through May 8). A second 33-engine static fire 3.5 weeks before NET May 15 suggests additional pre-flight verification was required. The most plausible reason: V3's all-Raptor-3 configuration (33 new-gen engines) has never operated simultaneously in flight, and the April static fire may have revealed engine interactions or thermal patterns requiring confirmation. This adds uncertainty — if the second static fire itself revealed issues, a further delay is possible.
+
+**What surprised me:** The shift from May 12 to May 15 NET is not explained in any source. The second static fire (May 9) could be the proximate cause: performing the static fire 3 days before the first window means SpaceX needed several days to assess results before declaring launch readiness. The NET shift from May 12 to May 15 maps closely to this timeline (static fire results → 3-4 day evaluation → launch readiness declaration).
+
+**What I expected but didn't find:** A specific technical explanation for either the NET shift or the second static fire. SpaceX does not publicly disclose pre-flight anomalies or hold-points in real time.
+
+**KB connections:**
+- [[Starship achieving routine operations at sub-100 dollars per kg is the single largest enabling condition for the entire space industrial economy]] — IFT-12 is the primary 2026 test of this claim; second static fire adds pre-launch uncertainty
+- reusability without rapid turnaround and minimal refurbishment does not reduce launch costs — V3's pre-launch process (2 static fires, extensive checks) suggests turnaround time for early V3 flights will not yet be "airline-like"
+- [[the space launch cost trajectory is a phase transition not a gradual decline analogous to sail-to-steam in maritime transport]] — V3 maiden flight is the next data point on this trajectory
+
+**Extraction hints:**
+- STATUS UPDATE (not standalone claim): Update existing IFT-12 archives with the second static fire data point and NET May 15 confirmation. Do NOT create a standalone claim — this is procedural data.
+- POTENTIAL FUTURE CLAIM (post-flight): If post-flight analysis reveals the reason for the second static fire (anomaly vs. protocol), that would be claim-worthy. Currently unknown.
+- TURNAROUND NOTE: Two static fires before V3 maiden flight vs. one before V2 flights — this may indicate V3's increased complexity requires more extensive pre-flight validation. Flag this when assessing the "airline-like turnaround" claim timeline.
+
+**Context:** NSF (NASASpaceFlight.com) posted the May 12 first-window scrub confirmation. Tesla Oracle covered the May 9 static fire with technical detail. SpaceLaunchSchedule and RocketLaunch.Live both show May 15 as current NET. Polymarket odds were at 91% as of May 7 and are likely higher given FAA clearance and second static fire completion.
+
+## Curator Notes (structured handoff for extractor)
+PRIMARY CONNECTION: [[Starship achieving routine operations at sub-100 dollars per kg is the single largest enabling condition for the entire space industrial economy]]
+WHY ARCHIVED: The second static fire before flight is a new data point not in prior archives. Combined with the May 12 → May 15 NET shift, this archive completes the pre-launch status picture. Post-flight: this archive will serve as the pre-flight baseline for comparison with actual results.
+EXTRACTION HINT: This is a procedural status archive — extract only after the flight, when post-flight data can be compared to these pre-flight conditions.