Gonçalo Esteves / building capable systems Field Notes →
Space Race 3.0 · the book, taken apart

I'm going to space.

This is what we need to be aware of on Earth.

I'm reading Red Moon Rising and building what it only describes. The book is about how the space race with China gets won. It was written before AI was everywhere, so I'm adding that layer: what AI changes on every line between Earth and space, and where the business is.

I'm not an AI engineer. I'm a systems person and a business person, with years of implementing change inside large companies and of teaching people to keep themselves safe. That's the view this is written from.

For owners of small companies, even companies of one, who are diving into space and want to know what to do, and how to build it so it holds.

0 · The rules of the game: treaties, doctrines, who is allowed to do what EARTH SPACE 1 · Earth → Earth · Paper 3 what breaks on the ground when space is hit 2 · Earth → Space · Paper 1 missiles, jamming, lasers, code sent up through a ground station 1 of 9 publish an ingredients list (SBOM) open-source space software repos · checked 15 Oct 2026 3 · Space → Earth a nuclear detonation in orbit, spoofed signals, debris coming down 4 · Space → Space · Paper 2 satellite against satellite: inspecting, docking, moving close on every line: what AI changes · where the money is · one original number
Four lines between Earth and space, inside the rules of the game. The one line measured so far is Earth → Space: of nine open-source space software repositories checked on 15 Oct 2026, one publishes an ingredients list (an SBOM).

Show the thing

The repositories below are public open-source space software: the flight software, the ground control, and the link-security libraries. We checked each one on 15 Oct 2026, from public GitHub data. The data and the simulation are not on this page yet. The simulation is paper 3, and it is not done.

An ingredients list for software, called an SBOM, lists the parts a program is built from. A security policy is the page where a project says how to report a hole in its code.

Project Repository SBOM published Security policy
cFS nasa/cFS
NASA Core Flight System (bundle)
No Yes
cFS nasa/cFE
cFS core executive
No Yes
cFS nasa/osal
cFS OS abstraction layer
No Yes
F Prime nasa/fprime
NASA JPL flight software framework
At build only Yes
Yamcs yamcs/yamcs
Mission control / ground
No Yes
OpenC3 COSMOS OpenC3/cosmos
Command and control / ground
Yes Yes
CryptoLib nasa/CryptoLib
CCSDS Space Data Link Security library
No No
SLE tools yamcs/jsle
Java Space Link Extension library
No No
SLE tools visionspacetec/sle-provider (archived)
SLE provider (archived)
No No

Checked 15 Oct 2026: 1 of 9 publishes an SBOM · of 9 generates one at build and does not publish it · 6 of 9 has a security policy.

One cell could not be checked. visionspacetec/sle-provider is archived, so GitHub would not show its private reporting setting, and we could not read that cell. Could not check is not the same as no.

Paper 2 · Transparency for manoeuvring objects

The tracker: a satellite's declared purpose, set against what it does in orbit.

Not built yet

Paper 3 · Resilient compute for the AI era

The belt simulation: radiation in the belt, run on a constellation shell.

Not built yet

The papers: 1 of 3 numbers done

Each paper carries one original number. The ledger shows which numbers the desk has checked and which it has not.

Paper Connection Original number Status
Paper 1
Encrypt the links, inventory the code
Earth to Space SBOM inventory: 1 of 9 public space-software repos publishes one (15 Oct 2026) Done, checked 15 Oct 2026
Paper 2
Transparency for manoeuvring objects
Space to Space Declared purpose vs observed behaviour tracker Not done yet
Paper 3
Resilient compute for the AI era
Earth to Earth Radiation-belt simulation on a constellation shell Not done yet

Ledger: 1 done · 2 not done.

The ten weeks

  1. Week 1 · 16 Oct
    • 16 Oct First newsletter; Friday chapter block (Ch 15)
      Show scheduled
    • 18 Oct Paper 1 interview target (request sent by him)
      Paper 1 scheduled
    • 20 Oct Paper 1 draft v1
      Paper 1 scheduled
    • 22 Oct Paper 1 draft v2 · Paper 3 simulation scoping note
      Paper 1 scheduled
  2. Week 2 · 23 Oct
    • 23 Oct Live 01: the opener (proposed)
      Show proposed
  3. Week 3 · 30 Oct
    • 2 Nov SPACEFOR-SOC activation ceremony, MacDill (public date)
      Field external
    • 3 Nov The Spacecraft Hacker's Handbook publishes (retailers list 3 Nov; the publisher's page says Sept 2026)
      Field external-unconfirmed
  4. Week 4 · 6 Nov
    • 10 Nov NASA TechLeap entry due (the other build)
      Field external
  5. Week 5 · 13 Nov
    • planned Inventory v2: more projects, maintainers' replies in
      Inventory
  6. Week 6 · 20 Nov
    • planned Paper 2 tracker v0: declared purpose vs observed behaviour
      Paper 2
  7. Week 7 · 27 Nov
    • planned Paper 3: the belt simulation runs (or who runs it, decided)
      Paper 3
  8. Week 8 · 4 Dec
    • planned Paper 1 to its venue (AIAA subcommittee, his ask)
      Paper 1
  9. Week 9 · 11 Dec
    • planned Paper 2 draft v1 with its interview
      Paper 2
  10. Week 10 · 18 Dec
    • planned Inventory v3; the three papers' ledgers reviewed in public
      Inventory

Ten weeks, from 16 Oct 2026. Dated rows are scheduled or public; the rest are planned and move.

The four connections, lane by lane.

Read it as a grid. The rows are where a line starts, the columns are where it ends. Each box is one connection, with its question and the chapters that sit on it.

To Earth
To Space
From Earth
From Earth to Earth

Earth to Earth

What breaks on the ground when space is hit, and what on the ground is the way in

If the satellites go dark for a day, what stops here?

What AI changes:When the grid, timing and data centres run on AI, what fails first when space goes dark, and can AI route around it?

Paper 3: Resilient compute for the AI era

From Earth to Space

Earth to Space

Hitting orbit from the ground: missiles, jamming, lasers, and code sent up through a ground station

Who can reach a satellite from the ground, and how cheaply?

What AI changes:AI finds flaws in shared code faster, for both sides. Does that favour the defender who patches or the attacker who scans?

Paper 1: Encrypt the links, inventory the code

From Space
From Space to Earth

Space to Earth

What orbit can do to the ground: a nuclear detonation in orbit, spoofed signals, debris coming down

What is the worst thing a satellite can do to us?

What AI changes:Can AI tell a spoofed signal from a real one fast enough to matter?

From Space to Space

Space to Space

Satellite against satellite: inspecting, docking, refuelling, moving close, saying one thing and doing another

Can we tell what a satellite is for by watching what it does?

What AI changes:Can AI watch every manoeuvring object and say, in public, what it is for?

Paper 2: Transparency for manoeuvring objects

Lane 0 sits beneath all four. The rules apply to every line above it.

The chapters (the reading list)

Each chapter is tagged with the connection it sits on and the paper it feeds. Chapter notes are not published yet, so each row links to its own place on this page.

  1. 00 Framing: three space races
    The rules of the game
  2. 01 Starfish Prime and Operation Fishbowl (1962)
    Earth to Earth Paper 3
  3. 02 February 2024: the Russian nuclear ASAT revelation
    Earth to SpaceSpace to Earth Paper 1
  4. 03 Doctrines: Russia and China
    Space to Earth
  5. 04 The treaty gap
    The rules of the game
  6. 05 China's 2045 ambition
    The rules of the game
  7. 06 Current vulnerabilities: the AI bill of materials
    Earth to Earth Paper 3
  8. 07 Threat matrix: weapon x actor x layer
    The rules of the game
  9. 08 Shooting satellites down: ASAT tests and the Kessler cascade
    Earth to SpaceSpace to EarthSpace to Space Paper 1Paper 2
  10. 09 Dual use: servicing, debris removal, uncooperative docking and spaceplanes
    Space to Space Paper 2
  11. 10 Jamming, lasers, watching the watchers, and what to do
    Earth to SpaceSpace to Space Paper 1Paper 2
  12. 11 Directed energy: lasers and microwaves, by engagement geometry
    Earth to SpaceSpace to Space Paper 1Paper 2
  13. 12 Thought experiments: orbital nukes, unknown objects, and what AI can do
    Space to EarthSpace to Space Paper 2
  14. 13 Defending the system: avoiding objects and cyber attacks
    Earth to EarthEarth to Space Paper 3Paper 1
  15. 14 Links, spoofing and AI without guardrails: what it means for nations and individuals
    Earth to EarthSpace to Earth Paper 3
  16. 15 Staying ahead: capability gaps, white-hat testing and 'Log4j in space'
    Earth to Space Paper 1

Episode resources: EP00 · The map · EP01 · What is inside open-source space software · EP03 · The View from Above.

Resources

The findings behind the episode

The rules

If you're building on this, come in here

The open calls for space work are on the opportunities page. The list gets the next chapter, paper and repository check as they go up.

Every week: the open calls, the numbers, and the chapter I'm on.