Assess whether an inter-spacecraft network really reports its exceptions to the entity that manages it, per ECSS-E-ST-50C clause 5.7.4.4. Follow one exception through the three places it is lost: reporting latency against the allowance its severity group carries, the store needed to hold exceptions raised while the path to the manager is down, and a rate limiter that discards whatever it will not pass. Show where one limiter shared across severity groups lets a storm of routine reports crowd out an alarm. Use when reviewing fault reporting on a formation or relay network. Trigger: ecss, e-st-50c-clause-5-7-4-4, inter-spacecraft-exception-reporting, exception-reporting-lat…
