Skip to main content

Rules of the Road

Rules of the Road is Satcat's coordination protocol. It assigns maneuver responsibility for each conjunction and lets operators exchange mitigation intent asynchronously, without needing to reach each other directly.

Operators signal intent by uploading ephemeris with a CONTEXT value, and can override automated assignments where necessary. The protocol follows the practices of the Space Safety Coalition.


Maneuver Responsibility

Satcat first assigns maneuver responsibility based on the maneuverability profile of each RSO involved in a conjunction. This assignment is used to guide coordination outcomes between operators.

Responsibility categoryCoordination Implication
Non-ManeuverableExpected to stand down
Minimally-ManeuverableMay defer unless assigned responsibility
Manually-ManeuverableExpected to coordinate and act if assigned
Auto-COLA ManeuveringExecutes COLA autonomously
CrewedRequires coordination
Unknown ManeuverabilityRequires coordination
Advisory Assignment

Responsibility categories are advisory. Operators unable to maneuver as assigned should coordinate directly via Satcat messaging or external channels.


Mitigation Intent

Mitigation Intent is an operator's declared intent to perform or defer a collision avoidance maneuver. It is declared by the Context on an uploaded operational ephemeris, and shown on the operator cards of every conjunction event that ephemeris affects.

Context is set in Asset Management > Ephemeris > Upload:

ContextUpload optionIntent shown
COLACOLA, intending to alter orbit for collision avoidanceI am intending to mitigate
MAINTENANCEMaintenance, intending to alter orbit for maintenanceI am intending to mitigate
ROUTINERoutine, not intending to alter orbitI am not intending to mitigate
NOVELNovel, uncataloged or temporary RSO entering orbitIntent undetermined
DECAYDecay, RSO expected to decay or reenter soonIntent undetermined
noneNull, no Context, intention undeterminedIntent undetermined

Selecting Null omits the field from the upload, which is not the same as ROUTINE. ROUTINE states that the operator won't maneuver; Null states that they haven't decided.

A fourth intent state, Assumed to mitigate, is never declared. Satcat infers it where the RSO is classified Auto-COLA Maneuvering, because that operator is not expected to upload an intent at all.

See Ephemeris Metadata for Context and Designation in full.


Updates and Conflicts

Intent follows the ephemeris. Every operational ephemeris upload updates intent on the conjunction events involving that RSO, based on its Context. Intent cannot be set independently of an upload, so re-declaring intent means uploading again with the Context that reflects it.

If intent metadata and ephemeris context are inconsistent, Satcat prioritizes ephemeris context to avoid coordination errors.


Auto-Generated Maneuvers and Responsibility

Organizations with Pro or Enterprise subscriptions can use auto-generated COLA maneuvers to fulfill assigned mitigation responsibilities. Satcat displays the generation status directly within each conjunction event:

StatusDescription
None generatedNo maneuver has been started or is required based on current data.
Generating...COLA maneuver generation is in progress and results will be available soon.
ReadyA complete maneuver plan is available for review and execution.
N/A (Pro)The organization is not subscribed at a tier that supports COLA planning.

Maneuver generation does not enforce action. It supports an assigned responsibility by providing a ready-to-use solution, which the operator reviews against mission constraints in Maneuver Designer.


For related details, see: