ECSS Verification Levels (space-systems/ecss/e1002-levels)
Use when the task is defining the verification-level hierarchy of a
product tree and assigning every requirement to a level under
ECSS-E-ST-10-02C, ahead of verification-method selection
(E-ST-10-02 clause 5.2.2) and stage planning (E-ST-10-02 clause 5.2.4).
Domain quick reference
- ECSS-E-ST-10-02C clause 5.2.3 organises verification bottom-up along
the product tree into five levels: equipment, subsystem, element,
segment, system. Each component in the product tree sits at exactly
one level and integrates into a parent component at a higher level.
- A requirement allocated to a single component is verified at that
component's level (see the sibling e10-req-allocation leaf for how a
requirement reaches a component in the first place).
- A requirement that spans more than one component -- an interface or
emergent-behaviour requirement -- is verified at the lowest level
where those components are first integrated together: the closest
common ancestor in the product tree, not each component's own level.
- Verification proceeds bottom-up: a level is not ready to close out
while any requirement assigned to it, or to a level beneath it, is
still unverified.
Workflow
- Model the product tree: every component with its verification level
and its parent component (the root, typically system-level, has no
parent). Validate the tree -- no unknown level, no missing parent,
and every parent strictly above its child in the hierarchy -- before
assigning requirements.
- For each requirement, record the component(s) it is allocated to. A
single component gives that component's level directly.
- For an interface or emergent-behaviour requirement spanning two or
more components, walk each component's ancestry up to the root and
take the closest ancestor common to all of them; that ancestor's
level is the requirement's verification level.
- Build the level matrix: one level per requirement id, and confirm no
requirement id from the input set is missing -- every requirement
needs a level, not a sample.
- Before reporting a level ready to close out, confirm every
requirement assigned to that level or to any level beneath it in the
equipment-to-system hierarchy has already been verified; list any
that have not as the blockers.
- Hand the level matrix to method selection (E-ST-10-02 clause 5.2.2,
the sibling e10-req-verif-methods leaf) and to the Verification Plan
/ VCD (E-ST-10-02 clause 5.2.8).
Pitfalls
- Assigning an interface requirement to one of its component's own
levels instead of the level where the components are actually
integrated together -- it under-states how far the system has to be
assembled before compliance is observable.
- Treating a product tree as valid without checking that every parent
sits strictly above its child -- a flat or inverted tree silently
breaks every level assignment computed from it.
- Declaring a level closed while a requirement at a lower level is
still open, breaking the bottom-up verification sequence.
- Dropping requirements from the level matrix -- an incomplete matrix
fails the "every requirement gets a level" mandate even if the
requirements present are assigned correctly.
Behavior contract (gate 3)
The level-hierarchy, product-tree validation, level-assignment, and
level-closure logic is exercised by the gate 3 contract test:
scripts/test_e1002_levels.py against scripts/e1002_levels_logic.py
(stdlib unittest, offline). Run:
python3 scripts/test_e1002_levels.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-levels3description: "Use when a product tree needs its verification levels defined and every requirement needs a verification level assigned before verification planning under ECSS-E-ST-10-02C: build the equipment/subsystem/element/segment/system hierarchy, assign each requirement to the level of the component(s) it is allocated to, and check whether a level is ready to close out. Trigger: verification level, verification levels, equipment subsystem element segment system, product tree, common ancestor, level closure, level close-out, E-ST-10-02, ecss, e-st-10c."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-levels15 domain: space-systems16 subdomain: ecss17 tags: [ecss, e-st-10-02c, verification-level, product-tree, requirements-engineering]18 version: 0.1.019 author: Aero Agent Skills20---2122# ECSS Verification Levels (space-systems/ecss/e1002-levels)2324Use when the task is defining the verification-level hierarchy of a25product tree and assigning every requirement to a level under26ECSS-E-ST-10-02C, ahead of verification-method selection27(E-ST-10-02 clause 5.2.2) and stage planning (E-ST-10-02 clause 5.2.4).2829## Domain quick reference3031- ECSS-E-ST-10-02C clause 5.2.3 organises verification bottom-up along32 the product tree into five levels: equipment, subsystem, element,33 segment, system. Each component in the product tree sits at exactly34 one level and integrates into a parent component at a higher level.35- A requirement allocated to a single component is verified at that36 component's level (see the sibling e10-req-allocation leaf for how a37 requirement reaches a component in the first place).38- A requirement that spans more than one component -- an interface or39 emergent-behaviour requirement -- is verified at the lowest level40 where those components are first integrated together: the closest41 common ancestor in the product tree, not each component's own level.42- Verification proceeds bottom-up: a level is not ready to close out43 while any requirement assigned to it, or to a level beneath it, is44 still unverified.4546## Workflow47481. Model the product tree: every component with its verification level49 and its parent component (the root, typically system-level, has no50 parent). Validate the tree -- no unknown level, no missing parent,51 and every parent strictly above its child in the hierarchy -- before52 assigning requirements.532. For each requirement, record the component(s) it is allocated to. A54 single component gives that component's level directly.553. For an interface or emergent-behaviour requirement spanning two or56 more components, walk each component's ancestry up to the root and57 take the closest ancestor common to all of them; that ancestor's58 level is the requirement's verification level.594. Build the level matrix: one level per requirement id, and confirm no60 requirement id from the input set is missing -- every requirement61 needs a level, not a sample.625. Before reporting a level ready to close out, confirm every63 requirement assigned to that level or to any level beneath it in the64 equipment-to-system hierarchy has already been verified; list any65 that have not as the blockers.666. Hand the level matrix to method selection (E-ST-10-02 clause 5.2.2,67 the sibling e10-req-verif-methods leaf) and to the Verification Plan68 / VCD (E-ST-10-02 clause 5.2.8).6970## Pitfalls7172- Assigning an interface requirement to one of its component's own73 levels instead of the level where the components are actually74 integrated together -- it under-states how far the system has to be75 assembled before compliance is observable.76- Treating a product tree as valid without checking that every parent77 sits strictly above its child -- a flat or inverted tree silently78 breaks every level assignment computed from it.79- Declaring a level closed while a requirement at a lower level is80 still open, breaking the bottom-up verification sequence.81- Dropping requirements from the level matrix -- an incomplete matrix82 fails the "every requirement gets a level" mandate even if the83 requirements present are assigned correctly.8485## Behavior contract (gate 3)8687The level-hierarchy, product-tree validation, level-assignment, and88level-closure logic is exercised by the gate 3 contract test:89scripts/test_e1002_levels.py against scripts/e1002_levels_logic.py90(stdlib unittest, offline). Run:91python3 scripts/test_e1002_levels.py9293## Compliance9495- ECSS standards are freely downloadable (ESA); cite the source and96 paraphrase per standards-map.yaml.97- compliance: STANDARDS-REF, gated: false.