ECSS Verification — Pre-tailoring Matrix (space-systems/ecss/e1002-pretailoring)
Use when the task is applying the ECSS-E-ST-10-02C §6 pre-tailoring matrix
to a declared space product type — determining which clause-5 verification
requirements are applicable, recommended, optional, or not applicable for
that category, and checking the project's captured requirement set for
coverage gaps.
Domain quick reference
- ECSS-E-ST-10-02C §6 defines a fixed pre-tailoring matrix that maps
each clause-5 verification requirement to an applicability level for
four product categories: space system (the complete, top-level space
system), segment (space, ground, or launch segment within that system),
equipment (unit or assembly at equipment level), and payload (science
or mission payload).
- The four applicability levels are: applicable (the requirement must be
complied with for this product type), recommended (the requirement
should be included unless the project records a justified deviation),
optional (a project decision to include or omit, not requiring a
deviation rationale), and not_applicable (excluded for this product
type; carrying it forward without justification is itself a finding).
- Pre-tailoring resolves applicability for the declared product type
before project-specific tailoring adjusts individual requirements for
risk, criticality, or programme constraints. Pre-tailoring output is
the input to project-specific tailoring, not a substitute for it.
- A project's captured requirement set must contain every requirement
whose applicability resolves to "applicable" for the declared product
type. Requirements at "recommended" level that are omitted require a
recorded justification. Requirements at "optional" or "not_applicable"
that are included do not require justification, but any "not_applicable"
requirement included without one is flagged as a scope anomaly.
Workflow
- Declare the space product type for the element under assessment:
space_system, segment, equipment, or payload. Reject any product type
outside the four recognized categories before proceeding.
- Apply the §6 pre-tailoring matrix for that product type: retrieve the
applicability level for each clause-5 verification requirement. The
result is the resolved applicability record — one row per requirement.
- Identify the applicable subset: all requirements whose resolved level
is "applicable". These are mandatory for the declared product type and
must each appear in the project's captured requirement set.
- Check the project's captured requirement set against the applicable
subset: flag every applicable requirement that is absent (a
missing-applicable finding). Reject any captured requirement ID that
is not recognized in the clause-5 set (an unknown-requirement finding).
- Optionally check for scope anomalies: flag any captured requirement
whose resolved level is "not_applicable" (a carried-forward-out-of-
scope finding), since including it without justification is a
pre-tailoring deviation.
- Aggregate findings. Pre-tailoring is complete only when there are no
missing-applicable findings and no unknown-requirement findings.
Recommended-level omissions and scope anomalies are advisory findings
that require recorded justification, not blockers.
Pitfalls
- Skipping the product-type declaration and applying the matrix for the
wrong category — the applicability levels differ substantially between
space_system and equipment; using the wrong row understates or overstates
mandatory scope.
- Treating a "recommended" level as either fully mandatory or fully
optional — it sits between the two: it must be included unless the
project records a specific deviation, which distinguishes it from an
"optional" requirement that needs no justification to omit.
- Treating pre-tailoring as the final tailoring step — §6 pre-tailoring
produces the starting applicable/recommended set for project-specific
tailoring, which must then run separately to adjust for risk,
criticality, and programme constraints under ECSS-S-ST-00-01.
- Accepting a captured set with unknown requirement IDs without raising
a finding — an ID absent from the clause-5 set indicates either a
transcription error or a reference to a requirement outside the matrix
scope, both of which must be resolved before tailoring is considered
complete.
Behavior contract (gate 3)
The product-type validation, applicability lookup, full-matrix
application, and pretailoring-violations check logic is exercised by the
gate 3 contract test: scripts/test_e1002_pretailoring.py against
scripts/e1002_pretailoring_logic.py (stdlib unittest, offline). Run:
python3 scripts/test_e1002_pretailoring.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-pretailoring3description: "Use when apply the ECSS-E-ST-10-02C §6 pre-tailoring matrix to a space product type: determine the applicability level (applicable, recommended, optional, or not applicable) for each clause-5 verification requirement for the product category under assessment, identify every applicable requirement that must be covered, flag any applicable verification requirement absent from the project's captured requirement set, and produce the per-requirement applicability record for engineering review. Product categories cover space system, segment, equipment, and payload. Trigger: ecss, e-st-10-02c, pretailoring, verification-matrix, product-type, verification-requirements, clause-5, requirements-applicability."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-pretailoring15 domain: space-systems16 subdomain: ecss17 tags: [ecss, e-st-10-02c, pretailoring, verification-matrix, product-type, verification-requirements, clause-5, requirements-applicability]18 version: 0.1.019 author: Aero Agent Skills20---2122# ECSS Verification — Pre-tailoring Matrix (space-systems/ecss/e1002-pretailoring)2324Use when the task is applying the ECSS-E-ST-10-02C §6 pre-tailoring matrix25to a declared space product type — determining which clause-5 verification26requirements are applicable, recommended, optional, or not applicable for27that category, and checking the project's captured requirement set for28coverage gaps.2930## Domain quick reference3132- ECSS-E-ST-10-02C §6 defines a fixed pre-tailoring matrix that maps33 each clause-5 verification requirement to an applicability level for34 four product categories: space system (the complete, top-level space35 system), segment (space, ground, or launch segment within that system),36 equipment (unit or assembly at equipment level), and payload (science37 or mission payload).38- The four applicability levels are: applicable (the requirement must be39 complied with for this product type), recommended (the requirement40 should be included unless the project records a justified deviation),41 optional (a project decision to include or omit, not requiring a42 deviation rationale), and not_applicable (excluded for this product43 type; carrying it forward without justification is itself a finding).44- Pre-tailoring resolves applicability for the declared product type45 before project-specific tailoring adjusts individual requirements for46 risk, criticality, or programme constraints. Pre-tailoring output is47 the input to project-specific tailoring, not a substitute for it.48- A project's captured requirement set must contain every requirement49 whose applicability resolves to "applicable" for the declared product50 type. Requirements at "recommended" level that are omitted require a51 recorded justification. Requirements at "optional" or "not_applicable"52 that are included do not require justification, but any "not_applicable"53 requirement included without one is flagged as a scope anomaly.5455## Workflow56571. Declare the space product type for the element under assessment:58 space_system, segment, equipment, or payload. Reject any product type59 outside the four recognized categories before proceeding.602. Apply the §6 pre-tailoring matrix for that product type: retrieve the61 applicability level for each clause-5 verification requirement. The62 result is the resolved applicability record — one row per requirement.633. Identify the applicable subset: all requirements whose resolved level64 is "applicable". These are mandatory for the declared product type and65 must each appear in the project's captured requirement set.664. Check the project's captured requirement set against the applicable67 subset: flag every applicable requirement that is absent (a68 missing-applicable finding). Reject any captured requirement ID that69 is not recognized in the clause-5 set (an unknown-requirement finding).705. Optionally check for scope anomalies: flag any captured requirement71 whose resolved level is "not_applicable" (a carried-forward-out-of-72 scope finding), since including it without justification is a73 pre-tailoring deviation.746. Aggregate findings. Pre-tailoring is complete only when there are no75 missing-applicable findings and no unknown-requirement findings.76 Recommended-level omissions and scope anomalies are advisory findings77 that require recorded justification, not blockers.7879## Pitfalls8081- Skipping the product-type declaration and applying the matrix for the82 wrong category — the applicability levels differ substantially between83 space_system and equipment; using the wrong row understates or overstates84 mandatory scope.85- Treating a "recommended" level as either fully mandatory or fully86 optional — it sits between the two: it must be included unless the87 project records a specific deviation, which distinguishes it from an88 "optional" requirement that needs no justification to omit.89- Treating pre-tailoring as the final tailoring step — §6 pre-tailoring90 produces the starting applicable/recommended set for project-specific91 tailoring, which must then run separately to adjust for risk,92 criticality, and programme constraints under ECSS-S-ST-00-01.93- Accepting a captured set with unknown requirement IDs without raising94 a finding — an ID absent from the clause-5 set indicates either a95 transcription error or a reference to a requirement outside the matrix96 scope, both of which must be resolved before tailoring is considered97 complete.9899## Behavior contract (gate 3)100101The product-type validation, applicability lookup, full-matrix102application, and pretailoring-violations check logic is exercised by the103gate 3 contract test: scripts/test_e1002_pretailoring.py against104scripts/e1002_pretailoring_logic.py (stdlib unittest, offline). Run:105python3 scripts/test_e1002_pretailoring.py106107## Compliance108109- ECSS standards are freely downloadable (ESA); cite the source and110 paraphrase per standards-map.yaml.111- compliance: STANDARDS-REF, gated: false.