ECSS Pre-tailoring (space-systems/ecss/e10-pretailoring)
Use when the task is applying the ECSS-E-ST-10C clause 7 pre-tailoring
matrix: deciding, for the project's space product type, which of the
standard's clause-5 requirements apply, are optional, or do not apply,
before the project runs its own tailoring pass.
Domain quick reference
- ECSS-E-ST-10C clause 7 pre-tailors the standard's requirements by
space product type before a project applies its own project-specific
tailoring (criticality, risk, budget) under ECSS-S-ST-00-01.
- A pre-tailoring matrix maps each clause id to a status per product
type: applicable (mandatory for that product type), optional (a
project decision to include or drop, recorded elsewhere), or
not_applicable (excluded for that product type).
- Common space product type categories used for pre-tailoring are the
space segment, the ground segment, and the launch service segment;
a given project element declares which one it is.
- Pre-tailoring happens once, ahead of and independent from the
project-specific tailoring step; a project must not skip pre-tailoring
and jump straight to project-specific tailoring, because
project-specific tailoring only adjusts the applicable/optional set
pre-tailoring already produced, it does not decide product-type
scope from scratch.
- Carrying forward a requirement whose clause is marked not_applicable
for the declared product type, or dropping a clause marked
applicable, without a recorded justification, breaks pre-tailoring.
Workflow
- Assemble the pre-tailoring matrix as a mapping of clause id to a
per-product-type status (applicable/optional/not_applicable),
covering every product type in scope for the programme.
- Validate the matrix: every clause has an entry for every product
type in scope, every status is one of the three allowed values, and
no clause is missing or has an unrecognised product type key.
- Declare the product type for the project element being tailored
(space segment, ground segment, launch service segment, or another
agreed category).
- Resolve applicability for that product type: the set of applicable
(mandatory), optional, and not-applicable clause ids.
- Compare the project's carried-forward requirement clause ids against
the resolved sets: flag applicable clauses with no carried-forward
requirement (missing mandatory), carried-forward clauses that
resolve to not_applicable (out-of-scope), and carried-forward clause
ids absent from the matrix entirely (unknown clause).
- Treat pre-tailoring as complete only when there are no missing
mandatory, out-of-scope, or unknown-clause findings; only then hand
the resolved applicable/optional set to project-specific tailoring.
Pitfalls
- Reusing a pre-tailoring matrix built for one product type (e.g.
ground segment) against a project element of a different product
type (e.g. space segment) without re-resolving applicability.
- Treating an optional clause as either mandatory or excluded by
default — optional clauses need an explicit project decision, not an
assumption in either direction.
- Silently dropping an applicable (mandatory) clause instead of
surfacing it as a missing-mandatory finding.
- Running project-specific tailoring against a matrix that has not
been validated for completeness (a clause missing a product-type
entry resolves to nothing and hides a scope decision).
Behavior contract (gate 3)
The matrix-validation, applicability-resolution, and compliance-check
logic is exercised by the gate 3 contract test:
scripts/test_e10_pretailoring.py against
scripts/e10_pretailoring_logic.py (stdlib unittest, offline). Run:
python3 scripts/test_e10_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: e10-pretailoring3description: "Use when applying the ECSS-E-ST-10C clause 7 pre-tailoring matrix to a space project: for the project's declared space product type (e.g. space segment, ground segment, launch service segment element), determine which clause-5 system-engineering requirements are applicable, optional, or not applicable, before project-specific tailoring per ECSS-S-ST-00-01. Checks the matrix itself is complete and well-formed, and checks the project's carried-forward requirement clauses against the resolved applicability (missing mandatory clauses, out-of-scope clauses kept without justification, unknown clause ids). Trigger: ecss, e-st-10c, pre-tailoring, pretailoring matrix, tailoring matrix, product type, applicability, clause 7."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/e10-pretailoring15 domain: space-systems16 subdomain: ecss17 tags: [ecss, e-st-10c, pre-tailoring, tailoring-matrix, product-type, systems-engineering]18 version: 0.1.019 author: Aero Agent Skills20---2122# ECSS Pre-tailoring (space-systems/ecss/e10-pretailoring)2324Use when the task is applying the ECSS-E-ST-10C clause 7 pre-tailoring25matrix: deciding, for the project's space product type, which of the26standard's clause-5 requirements apply, are optional, or do not apply,27before the project runs its own tailoring pass.2829## Domain quick reference3031- ECSS-E-ST-10C clause 7 pre-tailors the standard's requirements by32 space product type before a project applies its own project-specific33 tailoring (criticality, risk, budget) under ECSS-S-ST-00-01.34- A pre-tailoring matrix maps each clause id to a status per product35 type: applicable (mandatory for that product type), optional (a36 project decision to include or drop, recorded elsewhere), or37 not_applicable (excluded for that product type).38- Common space product type categories used for pre-tailoring are the39 space segment, the ground segment, and the launch service segment;40 a given project element declares which one it is.41- Pre-tailoring happens once, ahead of and independent from the42 project-specific tailoring step; a project must not skip pre-tailoring43 and jump straight to project-specific tailoring, because44 project-specific tailoring only adjusts the applicable/optional set45 pre-tailoring already produced, it does not decide product-type46 scope from scratch.47- Carrying forward a requirement whose clause is marked not_applicable48 for the declared product type, or dropping a clause marked49 applicable, without a recorded justification, breaks pre-tailoring.5051## Workflow52531. Assemble the pre-tailoring matrix as a mapping of clause id to a54 per-product-type status (applicable/optional/not_applicable),55 covering every product type in scope for the programme.562. Validate the matrix: every clause has an entry for every product57 type in scope, every status is one of the three allowed values, and58 no clause is missing or has an unrecognised product type key.593. Declare the product type for the project element being tailored60 (space segment, ground segment, launch service segment, or another61 agreed category).624. Resolve applicability for that product type: the set of applicable63 (mandatory), optional, and not-applicable clause ids.645. Compare the project's carried-forward requirement clause ids against65 the resolved sets: flag applicable clauses with no carried-forward66 requirement (missing mandatory), carried-forward clauses that67 resolve to not_applicable (out-of-scope), and carried-forward clause68 ids absent from the matrix entirely (unknown clause).696. Treat pre-tailoring as complete only when there are no missing70 mandatory, out-of-scope, or unknown-clause findings; only then hand71 the resolved applicable/optional set to project-specific tailoring.7273## Pitfalls7475- Reusing a pre-tailoring matrix built for one product type (e.g.76 ground segment) against a project element of a different product77 type (e.g. space segment) without re-resolving applicability.78- Treating an optional clause as either mandatory or excluded by79 default — optional clauses need an explicit project decision, not an80 assumption in either direction.81- Silently dropping an applicable (mandatory) clause instead of82 surfacing it as a missing-mandatory finding.83- Running project-specific tailoring against a matrix that has not84 been validated for completeness (a clause missing a product-type85 entry resolves to nothing and hides a scope decision).8687## Behavior contract (gate 3)8889The matrix-validation, applicability-resolution, and compliance-check90logic is exercised by the gate 3 contract test:91scripts/test_e10_pretailoring.py against92scripts/e10_pretailoring_logic.py (stdlib unittest, offline). Run:93python3 scripts/test_e10_pretailoring.py9495## Compliance9697- ECSS standards are freely downloadable (ESA); cite the source and98 paraphrase per standards-map.yaml.99- compliance: STANDARDS-REF, gated: false.