ECSS Verification — Analysis Report as Evidence (space-systems/ecss/e1002-analysis-report)
Use when the task is to decide whether an analysis report discharges its
requirement under ECSS-E-ST-10-02 clause 5.3.2.2. The report's own content
is a separate question (Annex S); this is the verification question --
right baseline, whole envelope, sound roll-up.
Domain quick reference
- Three things a content check cannot see decide whether an analysis
verifies anything: was it run on the design actually being verified,
did it cover the whole envelope the requirement demands, and does the
case-by-case result roll up soundly.
- An analysis run on a superseded model configuration is evidence about
a design that no longer exists. It can be immaculate and still verify
nothing.
- An unstated baseline and a superseded one are different failures. The
first is unrecorded and might be right; the second is known-wrong.
Reporting them identically hides which one you have.
- Envelope coverage is checked against the requirement's required case
list, not against the analysis's own matrix. A matrix is complete
with respect to itself by construction; the question is whether it
covers what the requirement asks.
- A case analysed outside the required envelope is reported but is not a
defect. Extra coverage is welcome; a matrix that has quietly drifted
away from the requirement is worth seeing.
- Case verdicts roll up severity-ordered: one failure fails the
requirement, any case not run leaves it incomplete, only an all-pass
matrix verifies it.
- A case not run needs a reason, because "enveloped by the launch case"
and "we ran out of time" are both common and close very differently.
- Passing every case analysed is not verification if a required case was
never analysed. The verdict can read pass while the requirement stays
unverified, which is exactly why coverage is a separate check.
Workflow
- Confirm the report names the model baseline and that it matches the
design baseline under verification.
- Check each analysis case for a verdict, and a not-run case for its
reason; reject duplicate case identifiers.
- Compare the analysed cases against the requirement's required
envelope; report each required case with no analysis.
- Report analysed cases lying outside the required envelope.
- Roll the case verdicts up to the requirement under the severity
ordering.
- The requirement is verified only when the roll-up passes and no
finding stands.
Pitfalls
- Accepting an analysis whose model predates the last design change.
The numbers are right about the wrong article.
- Judging coverage from the analysis matrix instead of the
requirement's envelope, which is circular and always passes.
- Reading an all-pass verdict as verification while a required case was
never run. The roll-up only speaks about cases that exist.
- Treating a case outside the envelope as a defect and forcing its
removal, losing coverage that cost real effort.
- Leaving a not-run case unexplained, so a deliberate enveloping
argument is indistinguishable from a gap.
- Letting two cases share an identifier, so one verdict overwrites
another in the roll-up.
Behavior contract (gate 3)
The baseline-match, envelope-coverage, extraneous-case, case-verdict and
severity-ordered roll-up logic is exercised by the gate 3 contract test:
scripts/test_e1002_analysis_report.py against
scripts/e1002_analysis_report_logic.py (stdlib unittest, offline). Run:
python3 scripts/test_e1002_analysis_report.py
Compliance
- ECSS standards are freely downloadable (ESA); cite the source and
paraphrase per standards-map.yaml.
- compliance: STANDARDS-REF, gated: false.
1---2name: e1002-analysis-report3description: "Use when determine whether an analysis report actually verifies its requirement under ECSS-E-ST-10-02 clause 5.3.2.2: confirm the analysis was run against the design baseline under verification rather than a superseded model, confirm every case the requirement's envelope demands was analysed and flag cases that drifted outside it, confirm each case carries a verdict and that a case not run states why, and roll the case results up to a requirement verdict. Trigger: ecss, e-st-10-02c, analysis-report, verification-by-analysis, case-coverage, model-baseline, envelope, verdict-rollup."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/e1002-analysis-report15 domain: space-systems16 subdomain: ecss17 tags: [ecss, e-st-10-02c, analysis-report, verification-by-analysis, case-coverage, model-baseline, verdict-rollup]18 version: 0.1.019 author: Aero Agent Skills20---2122# ECSS Verification — Analysis Report as Evidence (space-systems/ecss/e1002-analysis-report)2324Use when the task is to decide whether an analysis report discharges its25requirement under ECSS-E-ST-10-02 clause 5.3.2.2. The report's own content26is a separate question (Annex S); this is the verification question --27right baseline, whole envelope, sound roll-up.2829## Domain quick reference3031- Three things a content check cannot see decide whether an analysis32 verifies anything: was it run on the design actually being verified,33 did it cover the whole envelope the requirement demands, and does the34 case-by-case result roll up soundly.35- An analysis run on a superseded model configuration is evidence about36 a design that no longer exists. It can be immaculate and still verify37 nothing.38- An unstated baseline and a superseded one are different failures. The39 first is unrecorded and might be right; the second is known-wrong.40 Reporting them identically hides which one you have.41- Envelope coverage is checked against the requirement's required case42 list, not against the analysis's own matrix. A matrix is complete43 with respect to itself by construction; the question is whether it44 covers what the requirement asks.45- A case analysed outside the required envelope is reported but is not a46 defect. Extra coverage is welcome; a matrix that has quietly drifted47 away from the requirement is worth seeing.48- Case verdicts roll up severity-ordered: one failure fails the49 requirement, any case not run leaves it incomplete, only an all-pass50 matrix verifies it.51- A case not run needs a reason, because "enveloped by the launch case"52 and "we ran out of time" are both common and close very differently.53- Passing every case analysed is not verification if a required case was54 never analysed. The verdict can read pass while the requirement stays55 unverified, which is exactly why coverage is a separate check.5657## Workflow58591. Confirm the report names the model baseline and that it matches the60 design baseline under verification.612. Check each analysis case for a verdict, and a not-run case for its62 reason; reject duplicate case identifiers.633. Compare the analysed cases against the requirement's required64 envelope; report each required case with no analysis.654. Report analysed cases lying outside the required envelope.665. Roll the case verdicts up to the requirement under the severity67 ordering.686. The requirement is verified only when the roll-up passes and no69 finding stands.7071## Pitfalls7273- Accepting an analysis whose model predates the last design change.74 The numbers are right about the wrong article.75- Judging coverage from the analysis matrix instead of the76 requirement's envelope, which is circular and always passes.77- Reading an all-pass verdict as verification while a required case was78 never run. The roll-up only speaks about cases that exist.79- Treating a case outside the envelope as a defect and forcing its80 removal, losing coverage that cost real effort.81- Leaving a not-run case unexplained, so a deliberate enveloping82 argument is indistinguishable from a gap.83- Letting two cases share an identifier, so one verdict overwrites84 another in the roll-up.8586## Behavior contract (gate 3)8788The baseline-match, envelope-coverage, extraneous-case, case-verdict and89severity-ordered roll-up logic is exercised by the gate 3 contract test:90scripts/test_e1002_analysis_report.py against91scripts/e1002_analysis_report_logic.py (stdlib unittest, offline). Run:92python3 scripts/test_e1002_analysis_report.py9394## Compliance9596- ECSS standards are freely downloadable (ESA); cite the source and97 paraphrase per standards-map.yaml.98- compliance: STANDARDS-REF, gated: false.