EventHelix’s fictional Terminus RFP asks how an AI could give settlements on Proxima b continuous access to an interactive language model from orbit—without landing, teaching, or directly intervening. It is an engineering prompt, not a proposed or validated mission: its value is in the requirements it sets and the trade-offs it makes explicit.
What the RFP asks a system to do
In the scenario, the civilization is roughly 400 years from inventing the printing press. The observing AI can manufacture spacecraft and parachute self-contained terminals to the surface, but its rules prohibit landing or teaching. The proposed service would put interactive LLM inference in space and make it continuously available to settlements along an inhabited band.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Red Rising | $9.97 | Buy on Amazon |
| 2 |
|
Project Hail Mary: A Novel | $13.88 | Buy on Amazon |
| 3 |
|
Artemis | $9.95 | Buy on Amazon |
| 4 |
|
Masterpieces: The Best Science Fiction of the 20th Century | $11.03 | Buy on Amazon |
| 5 |
|
Dark Matter: A Novel | $11.65 | Buy on Amazon |
As an Amazon Associate I earn from qualifying purchases.
The RFP sets an initial deployment of 10,000 terminals, with a growth path to one million without redesign. Those are authored requirements from EventHelix’s 2026 scenario, not forecasts of actual demand or proof that the scale is technically achievable. The RFP solicits proposals and evaluates them on considerations including total mass, power, latency margin, robustness, and credible scaling; it does not choose a spacecraft or network architecture.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Read EventHelix’s Terminus RFP. The piece is the first entry in a series presented as a bridge between science fiction and system design; later chapters are slated to examine planetary modeling, orbital trades, constellation geometry, compute placement, radio design, beams, acquisition, and compliance. The DEV Community repost credits Sandeep Ahluwalia and identifies EventHelix as the original publisher.
#1 Best Overall
How the latency and availability targets work
The RFP distinguishes a normal conversation from a conversation that continues after a link failure. In failure-free operation, the first token must arrive within 300 ms at the 95th percentile. During rerouting around a failed link, the allowance rises to 600 ms. The RFP says its proposal showed that rerouting adds more round-trip time than the original single 300 ms budget allowed, prompting the amendment. These are requirements, not reported test results.
The amendment also defines availability in a way that treats degraded service as functioning: a session counts if it meets either the normal or degraded latency budget. The target is 99.9% availability per settlement. Separately, token stalls must remain under 100 ms at the 99th percentile; a satellite handover may interrupt service for no more than 100 ms; and no single failure should silence a settlement for more than one minute.
Rank #2
That distinction matters for evaluating a proposal. A service can remain available while delivering slower first tokens during recovery, provided it stays within the degraded limit. The RFP therefore does not equate every performance loss with an outage, but it also does not claim that any design has met its limits.
Recommended Free Tools
What the surface terminals must handle
Users connect through their own Wi-Fi devices, while each delivered terminal acts as their local base station. The terminal is expected to operate for ten years without attention, arrive by parachute, become service-ready within 15 minutes of a cold start without an almanac, clock, or position, and return to air within 30 seconds after an outage.
Rank #3
- Autonomous startup: Initial service cannot depend on preloaded navigation or time data, according to the RFP’s cold-start condition.
- Long unattended service: The ten-year requirement makes maintenance assumptions central to a proposal, not an afterthought.
- Recovery: The 30-second terminal recovery target is distinct from the one-minute limit on a single failure silencing a settlement.
- Local access: The terminal supplies the Wi-Fi access point; it is not merely a user handset or a conventional ground station.
Why the fictional radio environment is difficult
EventHelix’s scenario assumes coherent stellar radio bursts at approximately 1–3 GHz, overlapping the L and S bands that the RFP says a terrestrial engineer might first consider. It calls for degraded operation during major flares and a navigation alert within ten seconds. These frequencies and requirements are premises of the fictional brief, not independently established measurements of Proxima b or its star.
The implication for a bidder is that radio resilience and navigation cannot be treated as separate from the service promise: interference could affect the same links used for access and continuity. But the RFP does not establish how often such bursts occur, how severe their effects would be, or whether a particular mitigation would work. It asks for proposals under its assumptions.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Planetary conditions are scenario inputs, not verified facts
The RFP places settlements within 20 degrees of the terminator—the boundary between day and night—on a tidally locked fictional planet. It assigns the planet an 11.2-Earth-day rotation period and year and assumes persistent dayward surface winds of approximately 5–15 m/s. These numbers are authored by EventHelix for the scenario; they should not be read as independently verified measurements or as proof that the planet is habitable.
The geography gives the network problem its shape: proposals must serve an inhabited band rather than assume uniform settlement across the globe. The specific coverage geometry, orbital design, and effects of the assumed winds remain questions for the engineering work the series says it will explore.
Best Value
What this RFP does—and does not—establish
The Terminus opening is useful as a requirements exercise: it connects service scale, interaction latency, failure recovery, unattended terminals, autonomous acquisition, and a hostile assumed radio environment. The normal-versus-degraded latency amendment is especially important because it makes the service definition explicit when a link fails.
It is not evidence that an orbital LLM service for Proxima b is feasible, that the stated latency and reliability targets can be achieved, or that the fictional planet has the described climate and radio conditions. Those are open validation questions, not results of the RFP. The piece should be read as a fictional design challenge whose requested architecture and performance remain for proposals—and later analysis—to address.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitches
