ECSS Communications — Failure Modes (space-systems/ecss/e50-failure-modes)
Use when the task is the single obligation of ECSS-E-ST-50C clause 5.6.11.4 —
that the communications link performance requirements are stated for, and hold
in, the failure modes declared for the mission — and the question is what a
link budget must show beyond its nominal column.
Domain quick reference
- The nominal case is the easy case and it is not the requirement. The
requirement is that performance survives the declared failure modes, so
a budget that only proves the undegraded link has proved the wrong
thing.
- A declared mode with no figure against it is unassessed, not passing.
Absence of a number is absence of evidence; grading it green because
nothing was written is how a missing analysis becomes a signed-off one.
- Degradation contributors inside one mode are concurrent and add. A mode
built from three one-and-a-half decibel losses is worse than a mode
built from one three decibel loss, which is why the largest single
contributor is a poor guide to which mode governs.
- The governing mode is whichever applicable mode leaves the least
margin. It has to be found by grading every mode, not guessed from the
failure that sounds most severe.
- Direction matters. An uplink receiver failure does not degrade the
downlink, and grading it against the downlink requirement both wastes
margin and hides the mode that actually constrains that link.
- Recovery by redundancy changes how long a mode lasts, not whether the
link works while it lasts. A redundancy-recovered mode still has to be
graded, because the switchover is not instantaneous.
- Decibel margins add and subtract exactly on every host. Taking a power
of ten or a logarithm to reach the same answer introduces host-dependent
rounding for no benefit, so the arithmetic stays in decibels and the
compliance comparison carries an explicit tolerance.
Workflow
- Normalise the declared modes, refusing a duplicate name and a negative
degradation, and sort them so the grading order is deterministic.
- Sum each mode's concurrent contributors in a fixed order and subtract
the sum from the nominal margin to get that mode's margin.
- Decide which modes apply to the link direction under assessment and
grade only those against the requirement.
- Compare each margin with the requirement inclusively, so a mode that
lands exactly on the bound is met rather than a coin toss.
- Name the applicable mode that leaves the least margin as the governing
case.
- Compare the declared modes with the modes the mission requires — a
set that always holds, at least, the link lost outright, the margin
reduced while the link still closes, and a carrier that is acquired
only sporadically — and return any absentee as uncovered, which
makes the whole assessment unassessed rather than compliant.
Obligations
| Item |
Step |
| ECSS-E-ST-50C Rev.2 5.6.11.4a |
6 |
Pitfalls
- Reporting compliance from the nominal margin alone. The clause exists
precisely because that column always looks fine.
- Treating a required mode nobody analysed as a pass. An empty cell is an
open action, and the verdict has to say so rather than round it up.
- Grading contributors one at a time inside a mode. They occur together,
so the mode's real cost is their sum, and a per-contributor grade lets a
stack-up through.
- Assuming the loudest failure governs. Three modest concurrent losses
routinely beat one large loss, and only a full grading finds it.
- Applying a one-direction failure to both links. It overstates the
downlink case, understates the uplink case, and moves the governing mode
to the wrong place.
- Excusing a mode because redundancy recovers it. The link still has to
work during the failure and through the switchover.
- Using a strict comparison on a margin that lands on the requirement.
The answer then depends on the last bit of a floating-point sum, and
two hosts disagree about a compliant design.
Behavior contract (gate 3)
The decibel and direction validation, mode normalisation with duplicate
and negative-degradation rejection, concurrent contributor summation, the
per-mode margin, the inclusive margin comparison, direction filtering,
governing-mode selection, uncovered-mode detection and the three-way
met / not-met / unassessed verdict are exercised by the gate 3 contract
test: scripts/test_e50_failure_modes.py against
scripts/e50_failure_modes_logic.py (stdlib unittest, offline). Run:
python3 scripts/test_e50_failure_modes.py
Compliance
- ECSS standards are freely downloadable (ESA); cite the source and
paraphrase per standards-map.yaml.
- compliance: STANDARDS-REF, gated: false.
1---2name: e50-failure-modes3description: "Evaluate whether a communications link still meets its performance requirement in every failure mode the mission declares, per ECSS-E-ST-50C clause 5.6.11.4: sum each mode's concurrent decibel contributors, subtract them from the nominal margin, grade every mode against the required margin, name the mode that governs, and return any required mode the budget never covered as unassessed rather than as passing. Use when a link budget shows a healthy nominal column and the failure-mode columns are empty, optimistic, or graded one contributor at a time. Trigger: ecss, e-st-50c-communications-scope, link-performance-failure-modes, degraded-link-margin, governing-worst-case-link-mode, redundancy-recovered-link-failure, uncovered-failure-mode, concurrent-degradation-stack-up."4license: Apache-2.05compliance: STANDARDS-REF6standards:7 - id: ecss8 reference-only: true9gated: false10domain: space-systems11pack: space-systems12compatibility: "agentskills.io SKILL.md; any SKILL.md host (Claude Code, Hermes, OpenClaw)"13clauses:14 - standard: ECSS-E-ST-50C Rev.215 clause: 5.6.11.416 items: [a]17 relation: verifies18metadata:19 source: https://skillmd.com/skills/ashfordeou/e50-failure-modes20 domain: space-systems21 subdomain: ecss22 tags: [ecss, e-st-50c-communications-scope, e50-failure-modes, link-performance-failure-modes, degraded-link-margin, governing-worst-case-link-mode, redundancy-recovered-link-failure, uncovered-failure-mode, concurrent-degradation-stack-up]23 version: 0.1.024 author: Aero Agent Skills25---2627# ECSS Communications — Failure Modes (space-systems/ecss/e50-failure-modes)2829Use when the task is the single obligation of ECSS-E-ST-50C clause 5.6.11.4 —30that the communications link performance requirements are stated for, and hold31in, the failure modes declared for the mission — and the question is what a32link budget must show beyond its nominal column.3334## Domain quick reference3536- The nominal case is the easy case and it is not the requirement. The37 requirement is that performance survives the declared failure modes, so38 a budget that only proves the undegraded link has proved the wrong39 thing.40- A declared mode with no figure against it is unassessed, not passing.41 Absence of a number is absence of evidence; grading it green because42 nothing was written is how a missing analysis becomes a signed-off one.43- Degradation contributors inside one mode are concurrent and add. A mode44 built from three one-and-a-half decibel losses is worse than a mode45 built from one three decibel loss, which is why the largest single46 contributor is a poor guide to which mode governs.47- The governing mode is whichever applicable mode leaves the least48 margin. It has to be found by grading every mode, not guessed from the49 failure that sounds most severe.50- Direction matters. An uplink receiver failure does not degrade the51 downlink, and grading it against the downlink requirement both wastes52 margin and hides the mode that actually constrains that link.53- Recovery by redundancy changes how long a mode lasts, not whether the54 link works while it lasts. A redundancy-recovered mode still has to be55 graded, because the switchover is not instantaneous.56- Decibel margins add and subtract exactly on every host. Taking a power57 of ten or a logarithm to reach the same answer introduces host-dependent58 rounding for no benefit, so the arithmetic stays in decibels and the59 compliance comparison carries an explicit tolerance.6061## Workflow62631. Normalise the declared modes, refusing a duplicate name and a negative64 degradation, and sort them so the grading order is deterministic.652. Sum each mode's concurrent contributors in a fixed order and subtract66 the sum from the nominal margin to get that mode's margin.673. Decide which modes apply to the link direction under assessment and68 grade only those against the requirement.694. Compare each margin with the requirement inclusively, so a mode that70 lands exactly on the bound is met rather than a coin toss.715. Name the applicable mode that leaves the least margin as the governing72 case.736. Compare the declared modes with the modes the mission requires — a74 set that always holds, at least, the link lost outright, the margin75 reduced while the link still closes, and a carrier that is acquired76 only sporadically — and return any absentee as uncovered, which77 makes the whole assessment unassessed rather than compliant.7879## Obligations8081| Item | Step |82|---|---|83| ECSS-E-ST-50C Rev.2 5.6.11.4a | 6 |8485## Pitfalls8687- Reporting compliance from the nominal margin alone. The clause exists88 precisely because that column always looks fine.89- Treating a required mode nobody analysed as a pass. An empty cell is an90 open action, and the verdict has to say so rather than round it up.91- Grading contributors one at a time inside a mode. They occur together,92 so the mode's real cost is their sum, and a per-contributor grade lets a93 stack-up through.94- Assuming the loudest failure governs. Three modest concurrent losses95 routinely beat one large loss, and only a full grading finds it.96- Applying a one-direction failure to both links. It overstates the97 downlink case, understates the uplink case, and moves the governing mode98 to the wrong place.99- Excusing a mode because redundancy recovers it. The link still has to100 work during the failure and through the switchover.101- Using a strict comparison on a margin that lands on the requirement.102 The answer then depends on the last bit of a floating-point sum, and103 two hosts disagree about a compliant design.104105## Behavior contract (gate 3)106107The decibel and direction validation, mode normalisation with duplicate108and negative-degradation rejection, concurrent contributor summation, the109per-mode margin, the inclusive margin comparison, direction filtering,110governing-mode selection, uncovered-mode detection and the three-way111met / not-met / unassessed verdict are exercised by the gate 3 contract112test: scripts/test_e50_failure_modes.py against113scripts/e50_failure_modes_logic.py (stdlib unittest, offline). Run:114python3 scripts/test_e50_failure_modes.py115116## Compliance117118- ECSS standards are freely downloadable (ESA); cite the source and119 paraphrase per standards-map.yaml.120- compliance: STANDARDS-REF, gated: false.