ECSS GSE Design Assurance (space-systems/ecss/q20-gse-design)
Use when the task is the clause 5.8.1 quality assurance of ground support
equipment design, development and verification in ECSS-Q-ST-20C: a GSE design
is being reviewed, and the question is whether its requirements trace, whether
the verification actually closed them, and whether the design may be used.
Domain quick reference
- GSE is not flight hardware, but it holds, lifts, powers and tests flight
hardware, so its requirement set is traced with the same discipline. A GSE
requirement with no source requirement behind it was invented inside the GSE
design, and nobody outside that design agreed to it.
- Traceability runs both ways. Upward, every GSE requirement names a parent in
the source set; downward, every GSE requirement has a verification record
that closes it. A record pointing at a requirement that does not exist is a
finding in the other direction.
- The method is part of the requirement, not a free choice at verification
time. A requirement planned for test and closed by analysis has not been
verified as agreed, whatever the analysis says.
- Criticality decides what a method may be. A requirement protecting personnel
or the flight hardware the GSE touches is closed by test; review of design
and analysis show intent, not behaviour.
- Coverage is a set property, not a per-requirement one. A requirement with a
passing record and a later failing one is not closed, and the coverage
fraction has to say so.
- The review outcome separates what stops the design from what follows it. An
open record on a non-critical requirement is an action; an untraced
requirement or a failed verification is not.
Workflow
- Validate the requirement set: unique identifiers, a criticality and a
planned method from the closed vocabularies, and a parent identifier where
one is claimed.
- Validate the verification records the same way, refusing a duplicated record
identifier and an unknown result state.
- Trace upward, separating a requirement that names no parent from one whose
parent is not in the declared source set.
- Trace downward: name each requirement with no record, each method
substitution, each failed record and each open record as its own finding.
- Grade method adequacy against criticality independently of whether the
verification happened at all.
- Compute closure coverage, counting a requirement closed only when it has a
passing record and no failing or open one, and compare it with the required
value through a named tolerance.
- Sort the findings into blocking and actions, then return the review verdict.
Pitfalls
- Counting records instead of requirements. Three records against one
requirement leaves the other two requirements unverified, and a record count
hides that.
- Accepting a method substitution because the substitute passed. The planned
method is what the requirement was agreed against; changing it is a change to
the requirement, and it goes through the same approval.
- Closing a lifting or mating requirement on review of design. The GSE holds
flight hardware, and a drawing review does not show what the fixture does
under load.
- Treating a passing record as permanent. A later failure on the same
requirement reopens it, and the coverage figure has to fall accordingly.
- Folding every finding into one verdict. An open record on a non-critical item
is an action the review carries; an untraced requirement is not.
- Reading an empty verification set as nothing to report. No records means no
requirement is closed, which is the loudest finding the review can make.
Behavior contract (gate 3)
The requirement and record validation, upward and downward traceability,
method-substitution detection, criticality-based method adequacy, closure
coverage and the review verdict are exercised by the gate 3 contract test:
scripts/test_q20_gse_design.py against scripts/q20_gse_design_logic.py (stdlib
unittest, offline). Run:
python3 scripts/test_q20_gse_design.py
Compliance
- ECSS standards are freely downloadable (ESA); cite the source and
paraphrase per standards-map.yaml.
- compliance: STANDARDS-REF, gated: false.
1---2name: q20-gse-design3description: "Audit the design, development and verification of ground support equipment under ECSS-Q-ST-20C clause 5.8.1: trace each GSE requirement up to a source requirement that actually exists and down to a verification record, compare the method a record used with the method the requirement planned, refuse a paper closure on a requirement that protects flight hardware or people, compute the closure coverage of the set, and return approved, approved-with-actions or not-approved. Use when a GSE design has to be reviewed before it goes near flight hardware. Trigger: ecss, q-st-20c-clause-5-8-1, gse-requirement-traceability, gse-verification-record, gse-verification-method-substitution, gse-closure-coverage, gse-design-review-verdict."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)"13metadata:14 source: https://skillmd.com/skills/ashfordeou/q20-gse-design15 domain: space-systems16 subdomain: ecss17 tags: [ecss, q-st-20c-quality-assurance-scope, q20-gse-design, gse-requirement-traceability, gse-verification-record, gse-verification-method-substitution, gse-closure-coverage, gse-design-review-verdict]18 version: 0.1.019 author: Aero Agent Skills20---2122# ECSS GSE Design Assurance (space-systems/ecss/q20-gse-design)2324Use when the task is the clause 5.8.1 quality assurance of ground support25equipment design, development and verification in ECSS-Q-ST-20C: a GSE design26is being reviewed, and the question is whether its requirements trace, whether27the verification actually closed them, and whether the design may be used.2829## Domain quick reference3031- GSE is not flight hardware, but it holds, lifts, powers and tests flight32 hardware, so its requirement set is traced with the same discipline. A GSE33 requirement with no source requirement behind it was invented inside the GSE34 design, and nobody outside that design agreed to it.35- Traceability runs both ways. Upward, every GSE requirement names a parent in36 the source set; downward, every GSE requirement has a verification record37 that closes it. A record pointing at a requirement that does not exist is a38 finding in the other direction.39- The method is part of the requirement, not a free choice at verification40 time. A requirement planned for test and closed by analysis has not been41 verified as agreed, whatever the analysis says.42- Criticality decides what a method may be. A requirement protecting personnel43 or the flight hardware the GSE touches is closed by test; review of design44 and analysis show intent, not behaviour.45- Coverage is a set property, not a per-requirement one. A requirement with a46 passing record and a later failing one is not closed, and the coverage47 fraction has to say so.48- The review outcome separates what stops the design from what follows it. An49 open record on a non-critical requirement is an action; an untraced50 requirement or a failed verification is not.5152## Workflow53541. Validate the requirement set: unique identifiers, a criticality and a55 planned method from the closed vocabularies, and a parent identifier where56 one is claimed.572. Validate the verification records the same way, refusing a duplicated record58 identifier and an unknown result state.593. Trace upward, separating a requirement that names no parent from one whose60 parent is not in the declared source set.614. Trace downward: name each requirement with no record, each method62 substitution, each failed record and each open record as its own finding.635. Grade method adequacy against criticality independently of whether the64 verification happened at all.656. Compute closure coverage, counting a requirement closed only when it has a66 passing record and no failing or open one, and compare it with the required67 value through a named tolerance.687. Sort the findings into blocking and actions, then return the review verdict.6970## Pitfalls7172- Counting records instead of requirements. Three records against one73 requirement leaves the other two requirements unverified, and a record count74 hides that.75- Accepting a method substitution because the substitute passed. The planned76 method is what the requirement was agreed against; changing it is a change to77 the requirement, and it goes through the same approval.78- Closing a lifting or mating requirement on review of design. The GSE holds79 flight hardware, and a drawing review does not show what the fixture does80 under load.81- Treating a passing record as permanent. A later failure on the same82 requirement reopens it, and the coverage figure has to fall accordingly.83- Folding every finding into one verdict. An open record on a non-critical item84 is an action the review carries; an untraced requirement is not.85- Reading an empty verification set as nothing to report. No records means no86 requirement is closed, which is the loudest finding the review can make.8788## Behavior contract (gate 3)8990The requirement and record validation, upward and downward traceability,91method-substitution detection, criticality-based method adequacy, closure92coverage and the review verdict are exercised by the gate 3 contract test:93scripts/test_q20_gse_design.py against scripts/q20_gse_design_logic.py (stdlib94unittest, offline). Run:95python3 scripts/test_q20_gse_design.py9697## Compliance9899- ECSS standards are freely downloadable (ESA); cite the source and100 paraphrase per standards-map.yaml.101- compliance: STANDARDS-REF, gated: false.