Claim · 2024-09 · publication · Stated in source · Supported

The 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.

One recorded claim. The claim panel gives its qualification, the source passages with their place in each source, and how it was checked.

What it connects

Why we should train AI in space → bears on → No practical repair of hardware in orbit

Where it appears

Arguments about compute in orbit →

Claim and evidence

Why we should train AI in spacebears on ↓No practical repair of hardware in orbit

Machine-checked, not reviewed by an editorStated in sourceSupported

Supporting evidence: primary · 1 source

Date: 2024-09 · publication
Wording attested: 2024-12-24. The cover prints September 2024 (v1.01). The earliest copy located is an Internet Archive capture of 24 December 2024, which the cross-family check found byte-identical to the copy retrieved for the pack and again at admission.
Role: Context
Register (kind of text): Nonfiction
Missing element: a statement that repair in orbit is impracticable: it describes a design with swappable modules

Scope and limitsContext from a proponent: a design answer to maintenance, not a statement that repair is impracticable.

The evidence 01

primary sourceSupports the claim

Why we should train AI in space (White Paper v1.01)

Lumen Orbit, Inc. (now Starcloud), via lumenorbit.github.io · 2024-09

Archived copy, captured 2024-12-24: Why we should train AI in space (White Paper v1.01)

Cite the original source

Cite the original document, not Selekoa. Check these details against it.

Source excerpt

“The data center architecture has been designed such that compute containers and other modules can be swapped out in a modular fashion. This allows for the replacement of old or faulty equipment”

Location in source PDF p. 11, "Maintenance"

How it was read Retrieved directly from the publisher

Machine-checked · 2026-10-30

Source details and check notes

Authors: Ezra Feilden; Adi Oltean; Philip Johnston
Version: 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.
Canonical address: Open the canonical source ↗
Accessed: 2026-10-28
Language: English (en)
Archive copy: Open 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.
Attribution: Ezra Feilden, Adi Oltean, Philip Johnston, “Why we should train AI in space (White Paper v1.01)”, 2024-09.
Reuse: No open redistribution licence asserted. Bibliographic metadata, editorial paraphrases and short attributed quotations (at most 50 words each). Recheck terms before wider redistribution.
Check notes: Candidate pack passage, compute, power and orbit (research/compute-power-orbit). The quotation (32 words) matched the text retrieved for the candidate pack on 2026-10-28 and again at admission on 2026-10-30, in a fresh retrieval whose SHA-256 equals the pack’s. Matching ignored differences of whitespace, case, quotation marks, dashes and Unicode compatibility forms, so the source’s typography can differ. A cross-family machine check (2026-10-29/30, item 100) re-read the record’s sources and found full support. No human editorial review.

Status and meaning

Editorial status. Not reviewed by an editor. An exploratory record that no editor has accepted. This status does not say whether a person has read any linked passage. Each evidence record above shows how it was checked.

Relation. A passage of the document bears on the proposition without meeting its criterion; the record names the missing element. It is not an articulation and implies no influence.

Date. Date of publication, as the source gives it.

Record ID cpo-orb-oc8-lumen-2024