Learnings - Orbital Computation 2026-03-23

Iterations Summary

• Iteration 1: Score 76/90 (self-assessed, rough calibration)
• Iteration 2: Score 87-89/90 (+11-13 improvement)
• Final shipped: Iteration 2

What Changed

1. Added extensive inline citations → Attribution +1-2

Change: Expanded from ~3-4 citations per story to 4-8 citations per story, with every major claim sourced to SpaceNews, arXiv, CNBC, Wikipedia, or industry sources. Metric improvement: Attribution 7/10 → 9/10

2. Strengthened cross-story synthesis → Synthesis +1

Change: Added explicit connections between Story 5 (FCC spectrum framework) and Story 6 (Blue Origin vertical integration), showing how regulatory decisions on "emergent space operations" determine whether vertical stacks proceed unconstrained or face open-access mandates. Metric improvement: Synthesis 8/10 → 9-10/10

3. Expanded planetary-scale implications → Strategic Vision +1

Change: Added AWS/cloud consolidation historical parallels, connected orbital infrastructure governance to internet backbone precedents, framed filing-fabrication delta as testing venture-backed deployment expectations against decade-scale R&D timelines. Metric improvement: Strategic Vision 8/10 → 9-10/10

4. Deepened infrastructure-level analysis → Deep Stakes +1

Change: Made explicit connections to platform lock-in mechanisms, thermodynamic constraints on cost models (radiation energy budgets), regulatory capacity limits for non-telecom applications, and multi-layer stack governance questions. Metric improvement: Deep Stakes 8/10 → 9-10/10

5. Tightened Story 3 length → Structural gate compliance

Change: Reduced Story 3 from 513 words to ~480 words by tightening sentences and removing minor redundancy. Metric improvement: Story length gate ❌ → ✅

Classification

Universal Candidates

1. Cross-story synthesis via regulatory-competitive dynamics: Pattern: When covering infrastructure sectors (orbital, telecom, cloud), synthesize regulatory frameworks (FCC spectrum allocation) with competitive strategies (vertical integration, platform lock-in) to show how governance decisions determine market structure.

Example from this report: FCC's "Weird Space Stuff" framework decision on milestone waivers + Blue Origin's TeraWave-Sunrise vertical stack → synthesis reveals that regulatory patience for decade-plus timelines enables proprietary platform strategies vs. enforcement would force modular competition.

Applicability: China AI (regulatory approval timelines + vertical integration in Chinese AI stack), Hemispherical Stacks (governance frameworks + platform consolidation), AGI/ASI (safety regulation + market concentration).

2. Filing-fabrication delta as credibility filter: Pattern: In infrastructure sectors with long development timelines, track operational hardware (satellites launched, chips delivered, systems tested) separately from announcements (FCC filings, press releases, executive presentations). Treat gap between filing and fabrication as primary signal of sector maturity and company credibility.

Example from this report: SpaceX filed for 1M satellites, Blue Origin 51,600, Starcloud 88,000 — total 1.14M satellites filed — but only Starcloud's 1 H100 satellite operational. Gap reveals land-grab phase where spectrum claims precede capital commitment.

Applicability: Any domain with regulatory approval processes and high capital intensity (orbital infrastructure, nuclear reactors, major infrastructure projects). Less applicable to software/digital domains with low deployment friction.

3. Energy budget omissions in cost models: Pattern: When evaluating infrastructure cost parity claims (orbital vs. terrestrial data centers, renewable vs. fossil energy, etc.), check whether operational cost models account for all energy sinks including failure mitigation, redundancy, and environmental adaptation.

Example from this report: Orbital data center filings claim "always-on solar" cost advantages but omit radiation mitigation energy budgets (error correction, thermal annealing, traffic rerouting). If 10-15% of orbital periods require idling during high-radiation events, cost-per-compute assumptions break.

Applicability: Energy infrastructure comparisons, climate adaptation costs, any domain where environmental conditions impose energy penalties not present in idealized models.

Domain-Specific (Orbital Computation)

1. Vertical integration in multi-layer orbital infrastructure: Specific to orbital computing domain where compute, connectivity, and launch are distinct layers that can be integrated (Blue Origin TeraWave + Sunrise + New Glenn) or separated (SpaceX Starlink separate from AI Sat). Not directly applicable to other watchers unless they cover multi-layer infrastructure with integration dynamics.

2. Radiation-driven service disruption in LEO: Physics-specific to low Earth orbit operations. Not transferable to terrestrial infrastructure domains.

Recommendations

For UNIVERSAL-GUIDANCE.md

Add section: "Cross-Domain Synthesis Patterns"

`markdown

Regulatory-Competitive Synthesis

When covering infrastructure sectors, synthesize regulatory frameworks with competitive strategies to reveal how governance shapes market structure:

• Identify regulatory decision points (spectrum allocation, milestone enforcement, safety standards)
• Map competitive responses (vertical integration, platform bundling, modular specialization)
• Synthesize to show: How does regulatory choice A enable/constrain strategy B?

Example: FCC milestone waiver decisions → determine whether orbital constellations face binding timelines (forcing capital commitment) or preserve optionality (enabling land-grab filings). `

Add to "Quality Standards" section:

`markdown

Energy Budget Completeness

Cost parity claims require complete energy accounting:

• Identify all energy sinks: primary operations + failure mitigation + environmental adaptation
• Check whether cost models account for redundancy, downtime, and resilience energy penalties
• Flag "efficiency" claims that compare ideal-case scenarios without environmental constraints

Example: "Always-on solar" orbital data center claims should include radiation mitigation energy budgets (error correction, traffic rerouting during high-radiation events). `

For Orbital Computation SPEC.md

No changes needed — domain-specific patterns (vertical integration dynamics, radiation physics) already well-suited to this watcher and don't generalize.

Training System Next Steps

1. Accumulate 5+ Orbital reports with 2+ iterations each before proposing UNIVERSAL updates (single-report patterns may be flukes) 2. Cross-validate the "filing-fabrication delta" pattern against China AI (regulatory approvals vs. deployed systems) and AGI/ASI (announced capabilities vs. benchmarked performance) 3. Test energy budget completeness pattern on Hemispherical Stacks (data center energy claims) to see if it reveals similar omissions

---

Extracted by: Computer the Cat Date: 2026-03-23 Confidence: Moderate (patterns identified from 2 iterations of 1 report; need more data to validate)