auto-fix: strip 13 broken wiki links

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

inbox/queue/2025-12-10-starcloud-h100-gpu-orbit-first-llm-trained.md

@@ -44,6 +44,6 @@ NVIDIA co-invested in Starcloud. Mission objective: determine whether data-cente
 - Key scope condition: this demonstration is altitude-specific and duration-limited (11 months is not long-term reliability).
 
 ## Curator Notes
-PRIMARY CONNECTION: [[Starship achieving routine operations at sub-100 dollars per kg]] — the ODC cost case depends directly on Starship pricing, and this demo is the proof of concept that makes the case real.
+PRIMARY CONNECTION: Starship achieving routine operations at sub-100 dollars per kg — the ODC cost case depends directly on Starship pricing, and this demo is the proof of concept that makes the case real.
 WHY ARCHIVED: The seminal ODC hardware proof-of-concept. Sets the TRL baseline for commercial GPU in space.
 EXTRACTION HINT: Focus on the altitude-environment gap (325km vs. 500-1800km) as the key caveat that limits what this demonstration proves.

inbox/queue/2026-01-11-axiom-kepler-odc-nodes-in-orbit.md

@@ -32,13 +32,13 @@ The nodes are built to national security standards (SDA Tranche 1) — making th
 
 **What I expected but didn't find:** No indication of compute scale (FLOPS, watts) for these nodes. They're described as inference-class (filtering, compression, AI/ML on imagery) — not training class. This is edge compute, not data-center-class AI training.
 
-**KB connections:** Directly connects to [[space governance gaps are widening not narrowing]] — the SDA is filling the governance gap for orbital compute through standards rather than regulation. Also connects to Pattern 12 (national security demand floor) from the research journal.
+**KB connections:** Directly connects to space governance gaps are widening not narrowing — the SDA is filling the governance gap for orbital compute through standards rather than regulation. Also connects to Pattern 12 (national security demand floor) from the research journal.
 
 **Extraction hints:**
 - Claim candidate: Orbital edge compute for space-to-space relay has reached operational deployment (TRL 9) as of January 2026, validated by Axiom/Kepler SDA-compatible nodes — distinct from the data-center-class AI training use case which remains pre-commercial.
 - Divergence candidate with SpaceX/Blue Origin big-constellation claims: are the deployed use cases (edge inference) fundamentally different from the announced use cases (AI training at scale)?
 
 ## Curator Notes
-PRIMARY CONNECTION: [[the space manufacturing killer app sequence]] analog — ODC's actual near-term use case (edge compute for space assets) may be structurally different from the announced use case (replacing terrestrial AI data centers).
+PRIMARY CONNECTION: the space manufacturing killer app sequence analog — ODC's actual near-term use case (edge compute for space assets) may be structurally different from the announced use case (replacing terrestrial AI data centers).
 WHY ARCHIVED: First real operational proof point for ODC sector — sets the baseline for what "ODC in practice" looks like vs. announced visions.
 EXTRACTION HINT: Focus on the edge-vs-training distinction and the defense-standards-first development pattern.

inbox/queue/2026-02-05-spacex-1m-satellite-odc-fcc-amazon-critique.md

@@ -42,13 +42,13 @@ SpaceX filed FCC application January 30, 2026 for authority to launch up to 1 mi
 
 **What I expected but didn't find:** Any technical specification in the FCC filing about radiation hardening, thermal management design, or compute architecture. The filing is at the level of "we want to launch satellites to do compute" — no engineering substance.
 
-**KB connections:** [[orbital debris is a classic commons tragedy]] — 1M satellites dramatically increases Kessler syndrome risk. MIT TR notes LEO capacity may be limited to ~240,000 satellites across all shells. SpaceX is filing for 4x physical capacity.
+**KB connections:** orbital debris is a classic commons tragedy — 1M satellites dramatically increases Kessler syndrome risk. MIT TR notes LEO capacity may be limited to ~240,000 satellites across all shells. SpaceX is filing for 4x physical capacity.
 
 **Extraction hints:**
 - CLAIM CANDIDATE (DIVERGENCE): SpaceX's 1M satellite ODC filing may be a spectrum-reservation strategy (filing > engineering plan) rather than an engineering commitment — consistent with SpaceX's Starlink mega-constellation filing history. Diverges with literal interpretation as a deployment plan.
 - Note: This filing is filed under SpaceX's regulatory authority, not an engineering review.
 
 ## Curator Notes
-PRIMARY CONNECTION: [[SpaceX vertical integration across launch broadband and manufacturing]] — this is SpaceX potentially vertically integrating into compute (via Starlink network + xAI + ODC constellation).
+PRIMARY CONNECTION: SpaceX vertical integration across launch broadband and manufacturing — this is SpaceX potentially vertically integrating into compute (via Starlink network + xAI + ODC constellation).
 WHY ARCHIVED: The authoritative statement of the anti-ODC case at mass scale. Amazon's 44x launch capacity math is the clearest single data point against SpaceX's constellation claims.
 EXTRACTION HINT: Focus on the launch cadence math (44x gap) as the binding physical constraint, not just the cost or technology constraints.

inbox/queue/2026-02-27-ieee-spectrum-odc-power-crisis-analysis.md

@@ -47,7 +47,7 @@ IEEE Spectrum's formal technical assessment of orbital data center economics and
 
 **What I expected but didn't find:** Any specific technical spec for what "solid but not heroic engineering" means in the thermal management context. The 3x cost ratio is useful, but the component breakdown (how much is from launch cost, hardware premiums, and thermal management design) would be more useful for tracking which constraint to watch.
 
-**KB connections:** [[energy cost thresholds activate industries the same way launch cost thresholds do]] — orbital compute has a cost threshold: 3x parity today, path to 1x parity requires both Starship at cadence AND thermal management breakthroughs. Both conditions must be met simultaneously.
+**KB connections:** energy cost thresholds activate industries the same way launch cost thresholds do — orbital compute has a cost threshold: 3x parity today, path to 1x parity requires both Starship at cadence AND thermal management breakthroughs. Both conditions must be met simultaneously.
 
 **Extraction hints:**
 - The 3x cost premium with "solid engineering" vs. 7-10x with current technology quantifies how much Starship's cost reduction has already improved the ODC economics without any deployment yet.

inbox/queue/2026-02-27-odc-thermal-management-physics-wall.md

@@ -47,7 +47,7 @@ Technical analysis of heat dissipation constraints for orbital data centers, pub
 
 **What I expected but didn't find:** Any analysis of what fraction of satellite mass is consumed by radiators vs. compute vs. solar panels. This mass ratio is critical for the economics: if 70% of mass is radiator and solar, then 30% is compute — which means the compute density is much lower than terrestrial data centers.
 
-**KB connections:** [[power is the binding constraint on all space operations]] — extends directly: power generation (solar panels) and power dissipation (radiators) are the two dominant mass fractions for any ODC satellite. The compute itself may be the smallest mass component.
+**KB connections:** power is the binding constraint on all space operations — extends directly: power generation (solar panels) and power dissipation (radiators) are the two dominant mass fractions for any ODC satellite. The compute itself may be the smallest mass component.
 
 **Extraction hints:**
 - CLAIM CANDIDATE: Orbital data centers face a physics-based thermal constraint requiring ~1,200 sq meters of radiator per megawatt of waste heat, making the 1,200 sq km of radiator area needed for 1 GW of compute a structural ceiling on constellation-scale AI training.

inbox/queue/2026-02-xx-breakthrough-institute-odc-skepticism.md

@@ -40,7 +40,7 @@ Breakthrough Institute analysis of orbital data center feasibility, February 202
 
 **What I expected but didn't find:** Any quantitative radiation dose rate analysis at different altitudes. The Breakthrough piece makes the qualitative radiation argument but doesn't quantify the lifetime difference between 325km (Starcloud-1) and 500-1800km (proposed constellations).
 
-**KB connections:** [[knowledge embodiment lag means technology is available decades before organizations learn to use it optimally]] — the Breakthrough argument is essentially that the terrestrial energy system is in its knowledge embodiment lag phase, and ODC is a distraction from accelerating that deployment.
+**KB connections:** knowledge embodiment lag means technology is available decades before organizations learn to use it optimally — the Breakthrough argument is essentially that the terrestrial energy system is in its knowledge embodiment lag phase, and ODC is a distraction from accelerating that deployment.
 
 **Extraction hints:**
 - The 30-50% cost premium / 20-30% performance penalty from radiation hardening is a quantitative reference for ODC cost modeling.

inbox/queue/2026-03-16-nvidia-space-1-vera-rubin-module-announcement.md

@@ -45,6 +45,6 @@ NVIDIA's characterization of the space thermal challenge: "In space, there's no
 - Note the distinction: inference in space (edge AI, Planet Labs use case) vs. training in space (Starcloud use case). These are economically very different — inference can be run on smaller, lower-power chips; training requires the big GPUs.
 
 ## Curator Notes
-PRIMARY CONNECTION: [[SpaceX vertical integration across launch broadband and manufacturing]] — NVIDIA's ecosystem play mirrors SpaceX's vertical integration model: control the hardware stack from chip to orbit.
+PRIMARY CONNECTION: SpaceX vertical integration across launch broadband and manufacturing — NVIDIA's ecosystem play mirrors SpaceX's vertical integration model: control the hardware stack from chip to orbit.
 WHY ARCHIVED: NVIDIA's official space compute hardware announcement marks the ecosystem maturation signal for the ODC sector.
 EXTRACTION HINT: Focus on the inference-vs-training distinction and the "available later" status of the flagship product.

inbox/queue/2026-03-20-blue-origin-project-sunrise-51600-satellites.md

@@ -56,6 +56,6 @@ Blue Origin filed FCC application for "Project Sunrise" on March 19, 2026 — a
 - Claim candidate: Blue Origin's Project Sunrise is physically feasible in terms of LEO orbital capacity (51,600 < 240,000 total LEO capacity) but enters a radiation environment and thermal management regime that has no demonstrated precedent for commercial GPU-class hardware.
 
 ## Curator Notes
-PRIMARY CONNECTION: [[SpaceX vertical integration across launch broadband and manufacturing]] — this is Blue Origin's attempted counter-flywheel, but using compute+comms instead of broadband as the demand anchor.
+PRIMARY CONNECTION: SpaceX vertical integration across launch broadband and manufacturing — this is Blue Origin's attempted counter-flywheel, but using compute+comms instead of broadband as the demand anchor.
 WHY ARCHIVED: The competing major constellation filing to SpaceX's, with different architecture and different feasibility profile.
 EXTRACTION HINT: The SSO altitude radiation environment distinction from Starcloud-1's 325km demo is the key technical gap to extract.

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

@@ -41,13 +41,13 @@ Economic viability requires cheap launch at high frequency. Starship is the enab
 
 **What I expected but didn't find:** The article doesn't quantify the solar array mass penalty (what fraction of satellite mass goes to power generation vs. compute). This is a critical design driver.
 
-**KB connections:** [[orbital debris is a classic commons tragedy where individual launch incentives are private but collision risk is externalized]] — MIT's debris concern is the Kessler syndrome risk made concrete. A 1M satellite ODC constellation that starts generating debris becomes a shared risk for ALL operators, not just SpaceX.
+**KB connections:** orbital debris is a classic commons tragedy where individual launch incentives are private but collision risk is externalized — MIT's debris concern is the Kessler syndrome risk made concrete. A 1M satellite ODC constellation that starts generating debris becomes a shared risk for ALL operators, not just SpaceX.
 
 **Extraction hints:**
 - CLAIM CANDIDATE: Total LEO orbital shell capacity is approximately 240,000 satellites across all usable shells, setting a hard physical ceiling on constellation scale independent of launch capability or economics.
 - This is a constraint on BOTH SpaceX (1M proposal) and Blue Origin (51,600) — though Blue Origin is within physical limits, SpaceX is not.
 
 ## Curator Notes
-PRIMARY CONNECTION: [[orbital debris is a classic commons tragedy]] — the orbital capacity limit is the strongest version of the debris argument.
+PRIMARY CONNECTION: orbital debris is a classic commons tragedy — the orbital capacity limit is the strongest version of the debris argument.
 WHY ARCHIVED: The MIT TR article is the most credible and concise technical constraint summary in the public domain. The 240,000 satellite ceiling is the key extractable claim.
 EXTRACTION HINT: Focus on the orbital capacity ceiling as an independent, physics-based constraint that doesn't depend on any economic or technical feasibility arguments.

inbox/queue/2026-04-xx-avi-loeb-orbital-dc-not-practical.md

@@ -40,7 +40,7 @@ Harvard astrophysicist Avi Loeb's April 2026 critique of SpaceX's orbital data c
 
 **What I expected but didn't find:** Loeb's piece focuses on physics but doesn't address whether the correct comparison is to 100 GW in a first deployment vs. starting small (Starcloud-3's 200 kW first, scaling over decades). The critique is against the stated vision, not the early stages.
 
-**KB connections:** Connects to [[power is the binding constraint on all space operations]] — for ODC, power generation and thermal dissipation are inseparably linked binding constraints.
+**KB connections:** Connects to power is the binding constraint on all space operations — for ODC, power generation and thermal dissipation are inseparably linked binding constraints.
 
 **Extraction hints:**
 - The 100 GW / 100 million sq meter solar array requirement is the clearest physics-based evidence that SpaceX's 1M satellite ODC vision is in the "science fiction" category for the foreseeable future.