A mission begins with a useful orbit
Choose the path.
Read the tradeoff.
Select an objective and an orbital profile. The local planner updates coverage, delay, fuel window, and action language without contacting any real mission system.
Mission planner / local
Align the objective
with the orbit.
The action becomes available only after both decisions are visible.
1. Mission objective
2. Orbital profile
An action with context
The CTA should know
what it is asking.
Objective, mode, operating metrics, and risk stay visible before the button changes from generic intent to a specific local action.
Name the outcome
The action begins with what the mission should make possible.
Expose the tradeoff
Coverage, latency, duration, and complexity move together.
Say what happens
The CTA describes the next local artifact instead of implying a real launch.
Orbis CTA interaction study
Make the next move
specific.
Original implementation for the Web Motion Archive.