SELIS V2 / alternative-directions

Idea 6 — Communications and navigation availability planner

15 November 2026. One of six ideas; read 00-overview.md first. Source numbers refer to its section 8. Compiled with AI (Claude); not re-checked by a person. "Judgement" marks an assessment.

This is the weakest of the six on uniqueness. It is kept so that the reason is on file.

Product in one line

For a surface site and a time window, the tool returns when a user can reach Earth directly and through each relay provider, and how many navigation satellites it sees, with local terrain masking, in one comparison across providers.

Decision it supports

A payload or rover team decides which relay service to buy, where to park for a contact, and how much data it can return per day.

Why now

What exists

Data basis and checks

Type A slice (TRL 3)

CF Function Check
CF1 DTE availability at a site with terrain uncertainty NASA average Earth-visibility maps (B finding 6)
CF2 Relay contact windows for two published orbits Comparison with the provider's own published figures; not measured data
CF3 Navigation satellite visibility and geometry at the site Comparison with published ESA or NASA analyses; not measured data

Users outside ESA (candidates; none contacted)

Payload and rover teams on CLPS, ispace and Argonaut flights; relay operators that want an independent figure for their customers.

Four tests (judgement)

Recommendation (judgement)

Do not lead with this idea. Keep CF1 as a derived layer inside idea 1, 3 or 4, where Earth visibility is one of several constraints.

Risks and unknowns