From b4da966b41aade24248fc6fde09a918a15236755 Mon Sep 17 00:00:00 2001 From: Teleo Agents Date: Fri, 8 May 2026 06:19:24 +0000 Subject: [PATCH] auto-fix: strip 2 broken wiki links Pipeline auto-fixer: removed [[ ]] brackets from links that don't resolve to existing claims in the knowledge base. --- ...01-30-faa-44-starship-launches-lc39a-kennedy-space-center.md | 2 +- .../2026-frspt-frontiers-adr-thresholds-60-objects-year-leo.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/inbox/queue/2026-01-30-faa-44-starship-launches-lc39a-kennedy-space-center.md b/inbox/queue/2026-01-30-faa-44-starship-launches-lc39a-kennedy-space-center.md index b04cae53d..f1ea383da 100644 --- a/inbox/queue/2026-01-30-faa-44-starship-launches-lc39a-kennedy-space-center.md +++ b/inbox/queue/2026-01-30-faa-44-starship-launches-lc39a-kennedy-space-center.md @@ -56,7 +56,7 @@ The FAA publicly released its final environmental impact statement and record of **Extraction hints:** - **CLAIM CANDIDATE:** "FAA's approval of 44 Starship launches and 88 landings per year at LC-39A combined with 25 per year at Starbase creates a 69-launch annual regulatory ceiling that removes the regulatory constraint on Starship cadence and shifts the binding bottleneck to technical execution" - This is a specific, falsifiable claim with a clear confidence level: likely (regulatory fact, but LC-39A launch date is contingent on infrastructure) -- **UPDATE needed on launch cost claims:** The regulatory ceiling expansion is a material fact that strengthens the cadence economics argument in [[Starship economics depend on cadence and reuse rate]] +- **UPDATE needed on launch cost claims:** The regulatory ceiling expansion is a material fact that strengthens the cadence economics argument in Starship economics depend on cadence and reuse rate **Context:** This approval was January 30, 2026 — before IFT-12 which hasn't flown yet. The Florida pad represents SpaceX's planned redundancy for Starship operations. Historical context: LC-39A is the same pad that launched Apollo 11 and the Space Shuttle; SpaceX already uses it for Falcon 9 and Falcon Heavy. Starship will co-locate with Falcon operations initially. diff --git a/inbox/queue/2026-frspt-frontiers-adr-thresholds-60-objects-year-leo.md b/inbox/queue/2026-frspt-frontiers-adr-thresholds-60-objects-year-leo.md index d1e652ac1..4fdad8105 100644 --- a/inbox/queue/2026-frspt-frontiers-adr-thresholds-60-objects-year-leo.md +++ b/inbox/queue/2026-frspt-frontiers-adr-thresholds-60-objects-year-leo.md @@ -50,7 +50,7 @@ intake_tier: research-task **KB connections:** - [[orbital debris is a classic commons tragedy where individual launch incentives are private but collision risk is externalized to all operators]] — the ADR financing gap ($3-6B/year required vs. $1.2B current market) is the dollar value of the commons tragedy externalization - [[space governance gaps are widening not narrowing because technology advances exponentially while institutional design advances linearly]] — the ADR capacity gap (1-2 objects/year vs 60 needed) is a specific, quantified instance of this governance gap -- [[Ostrom proved communities self-govern shared resources when eight design principles are met]] — ADR as government-funded rather than operator-funded means Ostrom's "proportional allocation of costs and benefits" principle is violated: operators profit from launches but taxpayers fund cleanup +- Ostrom proved communities self-govern shared resources when eight design principles are met — ADR as government-funded rather than operator-funded means Ostrom's "proportional allocation of costs and benefits" principle is violated: operators profit from launches but taxpayers fund cleanup **Extraction hints:** - **CLAIM CANDIDATE:** "Active debris removal of approximately 60 large objects per year represents the scenario-dependent threshold at which LEO debris growth becomes negative, but current ADR capacity of 1-2 objects per year creates a 30-60x scale-up gap that is primarily a market structure and financing problem, not an engineering problem"