Why we should train AI in space
White paper v1.01 of Lumen Orbit, Inc. (renamed Starcloud in 2025), by Ezra Feilden, Adi Oltean and Philip Johnston, dated September 2024 on its cover. The earliest copy located is an Internet Archive capture of 24 December 2024.
- Issued by
- Starcloud (formerly Lumen Orbit)
- Authors credited
- No authorship claim recorded yet. The source record lists Ezra Feilden, Adi Oltean and Philip Johnston.
- Dates
- Published 2024-09 issue evidence
- Exact source
- Why we should train AI in space (White Paper v1.01) Lumen Orbit, Inc. (now Starcloud), via lumenorbit.github.io · published 2024-09 · Retrieved for the candidate pack on 2026-10-28 (SHA-256 90e1bde5b01437d7778e044f8ed95df1c49a63559fc1e35177c94d6443e384f7). PDF v1.01 as served at lumenorbit.github.io/wp.pdf on 2026-10-28; cover line "White Paper v1.01, September 2024". Starcloud's current link (starcloud.com/wp) serves v1.03 (starcloudinc.github.io/wp.pdf), which adds a note that Lumen Orbit was renamed Starcloud in 2025; v1.01 is quoted here. The served file cannot authenticate when the v1.01 bytes were first published. Retrieved again at admission on 2026-10-30 (SHA-256 90e1bde5b01437d7778e044f8ed95df1c49a63559fc1e35177c94d6443e384f7, the same bytes). The cross-family check (2026-10-30) opened the Internet Archive capture linked here and found it byte-identical to this retrieval; a capture shows only what the archive held on its date.Archived copy, captured 2024-12-24: Why we should train AI in space (White Paper v1.01). An archive copy shows only what the archive retrieved on 2024-12-24. It does not prove what the page said earlier, and it can differ from the copy checked on 2026-10-28.
- Earliest located in Arguments about compute in orbit for O1 Orbital solar supply as a reason for orbital compute →
- Earliest located in Arguments about compute in orbit for O3 Terrestrial constraints as a reason for orbital compute →
- Earliest located in Arguments about compute in orbit for O4 Falling launch prices as a condition of orbital compute →
Appears in
- Arguments about compute in orbit →8 records on this document
Versions
No other versions of this document are recorded. The evidence applies to the source version listed above. Other versions, such as a preprint, working paper or journal publication, are not identified or substituted.
Issue and authorship records
Documentary relations
Each relation is listed separately. Citing, crediting and reporting the use of a method are different acts, and none of them shows agreement or influence by itself.
Articulates · 5
Propositions whose criterion a passage of this document meets. The record says what the text states, in its register; it is not evidence that the proposition is true.
- Orbital solar supply as a reason for orbital computeThe Lumen Orbit white paper (September 2024) argues that data centres in orbit can use solar power around the clock, unhindered by night, weather and the atmosphere.2024-09 · publication · Stated in source · Supported Inspect claim & evidence ↗Orbital solar supply as a reason for orbital compute: propositions page →
- Radiative cooling in orbit as an advantageThe Lumen Orbit white paper (September 2024) argues that orbital data centres can lower cooling costs by passive radiative cooling to space.2024-09 · publication · Stated in source · Supported Inspect claim & evidence ↗Radiative cooling in orbit as an advantage: propositions page →
- Terrestrial constraints as a reason for orbital computeThe Lumen Orbit white paper (September 2024) argues that orbital data centres can be scaled almost indefinitely without the physical or permitting constraints faced on Earth.2024-09 · publication · Stated in source · Supported Inspect claim & evidence ↗Terrestrial constraints as a reason for orbital compute: propositions page →
- Falling launch prices as a condition of orbital computeThe Lumen Orbit white paper (September 2024) assumes a long-term launch price of about $30 per kilogram and argues that at such prices launch is no longer a primary cost driver.2024-09 · publication · Stated in source · Supported Inspect claim & evidence ↗Falling launch prices as a condition of orbital compute: propositions page →
- Radiation effects on computing hardware in orbitThe Lumen Orbit white paper (September 2024) states that shielding is required against radiation-induced latch-up, transients and total-dose effects in sensitive components, while arguing that shielding mass per unit of compute falls with container size.2024-09 · publication · Stated in source · Supported Inspect claim & evidence ↗Radiation effects on computing hardware in orbit: propositions page →
Contests · 1
Propositions a passage of this document disputes, or a premise they depend on.
- Harm to the sky and debris risk from orbital data centresThe Lumen Orbit white paper (September 2024) argues that, if best practices are followed, terrestrial astronomy is unlikely to be affected by orbital data centres in its chosen dawn-dusk orbit, while naming debris mitigation as a key hurdle.2024-09 · publication · Stated in source · Supported Inspect claim & evidence ↗Harm to the sky and debris risk from orbital data centres: propositions page →
Bears on · 2
Propositions a passage comes close to without meeting the criterion; each record names what is missing.
- Heat rejection as a constraint on orbital computeThe Lumen Orbit white paper (September 2024) states that a gigawatt-scale orbital data centre would need radiators dissipating gigawatts of heat, by far the largest deployed in space, while estimating them at under half the solar-array size.2024-09 · publication · Stated in source · Supported Inspect claim & evidence ↗Heat rejection as a constraint on orbital compute: propositions page →
- No practical repair of hardware in orbitThe Lumen Orbit white paper (September 2024) states that its design lets compute containers and other modules be swapped out to replace old or faulty equipment.2024-09 · publication · Stated in source · Supported Inspect claim & evidence ↗No practical repair of hardware in orbit: propositions page →
Not recorded for this document: cites · cited by · explicitly credits · reports using a method from · method reported as used by · applies parts of · parts applied by · discusses · reports evaluation of. A missing record does not show that the relation does not exist.