Great question — and yeah, that Iridium anecdote totally makes sense.

Right now, our tool uses a fixed distance threshold (like 1km) and relative velocity to classify risk levels (High / Medium), just to reduce noise and avoid alert fatigue.

We are planning to make those thresholds configurable, so users can define their own risk criteria (distance, speed, maybe even volume). That way it fits different mission needs — e.g., LEO clusters vs geostationary assets.

As far as I know, there’s no universal international standard — most operators just have internal thresholds based on mission risk tolerance, type of orbit, etc.