ECSS Requirement Characteristic — Justification (space-systems/ecss/e1006-char-justification)
Use when the task is verifying that each system requirement carries a recorded
justification (rationale) per ECSS-E-ST-10C §8.2.2: confirm the justification
field is populated, confirm it references a traceable source, and flag any
requirement where either record is missing.
Domain quick reference
- §8.2.2 of ECSS-E-ST-10C stipulates that each requirement shall have its
rationale documented — stating the reason the requirement exists. The
justification is not the requirement itself; it is the answer to "why does
this requirement exist at all?"
- A valid justification must be traceable to one of the recognised source
categories: a stakeholder need, a mission objective, a parent standard
clause, a derived engineering rationale, a safety argument, an interface
requirement, or an operational concept. A justification that exists but
cites an unrecognised category is still a finding.
- A requirement may be technically correct and internally consistent yet still
be non-compliant if no one has recorded the reason it was imposed. Both the
justification text and its source reference must be on record.
- Duplicate requirement IDs in the assessment set are themselves a finding
because they prevent unambiguous traceability of justification records.
Workflow
- Collect the full list of requirements to be assessed. Reject the assessment
if the list is empty — an empty set produces no meaningful verdict.
- For each requirement, check the requirement ID field first. An absent or
whitespace-only ID is non-compliant immediately; record it with the
placeholder
<missing-id> and continue to the next requirement.
- Check the justification text field. If it is absent or contains only
whitespace, record a non-compliant finding for that requirement with the
reason "justification field is absent or empty".
- Check the justification source reference field. If it is absent or
whitespace-only, record "justification source reference is absent or empty".
If the field is populated but the source category does not match any
recognised source kind (stakeholder_need, mission_objective, standard_clause,
derived, safety_argument, interface_requirement, operational_concept), record
the unrecognised category name in the finding.
- If duplicate requirement IDs are encountered, record the second and
subsequent occurrences as non-compliant with the reason "duplicate
requirement id" and skip their detailed justification check — a duplicated
ID makes the justification record ambiguous.
- Aggregate per-requirement findings into a report. Count compliant and
non-compliant items. The set is fully compliant only when no non-compliant
findings remain.
Pitfalls
- Treating a justification field that contains the requirement text itself as
a valid justification — the rationale must explain why, not repeat what.
The logic module checks presence and source traceability, not semantic
adequacy; a separate review step is needed to catch self-referential entries.
- Accepting a populated justification_source field without checking that the
source category is one of the recognised kinds — an ad-hoc or invented
category does not satisfy the traceability requirement.
- Skipping the duplicate-ID check and allowing two requirements with the same
ID to each carry a different justification — the traceability of which
justification belongs to which instance becomes undefined.
- Reading "no non-compliant count" as "fully compliant" on an empty input —
the assess function raises on empty input precisely to prevent a vacuous pass.
Behavior contract (gate 3)
The requirement-ID check, justification-text check, source-reference check,
source-category check, duplicate-ID check, and set-level compliance logic are
exercised by the gate 3 contract test:
scripts/test_e1006_char_justification.py against
scripts/e1006_char_justification_logic.py (stdlib unittest, offline). Run:
python3 scripts/test_e1006_char_justification.py
Compliance
- ECSS standards are freely downloadable (ESA); cite the source and paraphrase
per standards-map.yaml.
- compliance: STANDARDS-REF, gated: false.
1---2name: e1006-char-justification3description: "Use when verify that every system requirement in the requirements4 database carries a recorded justification explaining why the requirement exists,5 per ECSS-E-ST-10C §8.2.2. For each requirement, determine whether the6 justification field is populated and whether the justification cites a traceable7 source — such as a stakeholder need, mission objective, standard clause, derived8 rationale, or safety argument. Flag any requirement whose justification text is9 absent or empty, and any requirement whose justification source reference is not10 recorded or belongs to an unrecognised source category. Produce a per-requirement11 verdict and a summary count of non-compliant items across the set.12 Trigger: ecss, e-st-10-system-scope, requirement-justification, rationale,13 char-justification, traceability, requirements-management, §8.2.2."14license: Apache-2.015compliance: STANDARDS-REF16standards:17 - id: ecss18 reference-only: true19gated: false20domain: space-systems21pack: space-systems22compatibility: "agentskills.io SKILL.md; any SKILL.md host (Claude Code, Hermes, OpenClaw)"23metadata:24 source: https://skillmd.com/skills/ashfordeou/e1006-char-justification25 domain: space-systems26 subdomain: ecss27 tags: [ecss, e-st-10-system-scope, requirement-justification, rationale, char-justification, traceability, requirements-management]28 version: 0.1.029 author: Aero Agent Skills30---3132# ECSS Requirement Characteristic — Justification (space-systems/ecss/e1006-char-justification)3334Use when the task is verifying that each system requirement carries a recorded35justification (rationale) per ECSS-E-ST-10C §8.2.2: confirm the justification36field is populated, confirm it references a traceable source, and flag any37requirement where either record is missing.3839## Domain quick reference4041- §8.2.2 of ECSS-E-ST-10C stipulates that each requirement shall have its42 rationale documented — stating the reason the requirement exists. The43 justification is not the requirement itself; it is the answer to "why does44 this requirement exist at all?"45- A valid justification must be traceable to one of the recognised source46 categories: a stakeholder need, a mission objective, a parent standard47 clause, a derived engineering rationale, a safety argument, an interface48 requirement, or an operational concept. A justification that exists but49 cites an unrecognised category is still a finding.50- A requirement may be technically correct and internally consistent yet still51 be non-compliant if no one has recorded the reason it was imposed. Both the52 justification text and its source reference must be on record.53- Duplicate requirement IDs in the assessment set are themselves a finding54 because they prevent unambiguous traceability of justification records.5556## Workflow57581. Collect the full list of requirements to be assessed. Reject the assessment59 if the list is empty — an empty set produces no meaningful verdict.602. For each requirement, check the requirement ID field first. An absent or61 whitespace-only ID is non-compliant immediately; record it with the62 placeholder `<missing-id>` and continue to the next requirement.633. Check the justification text field. If it is absent or contains only64 whitespace, record a non-compliant finding for that requirement with the65 reason "justification field is absent or empty".664. Check the justification source reference field. If it is absent or67 whitespace-only, record "justification source reference is absent or empty".68 If the field is populated but the source category does not match any69 recognised source kind (stakeholder_need, mission_objective, standard_clause,70 derived, safety_argument, interface_requirement, operational_concept), record71 the unrecognised category name in the finding.725. If duplicate requirement IDs are encountered, record the second and73 subsequent occurrences as non-compliant with the reason "duplicate74 requirement id" and skip their detailed justification check — a duplicated75 ID makes the justification record ambiguous.766. Aggregate per-requirement findings into a report. Count compliant and77 non-compliant items. The set is fully compliant only when no non-compliant78 findings remain.7980## Pitfalls8182- Treating a justification field that contains the requirement text itself as83 a valid justification — the rationale must explain *why*, not repeat *what*.84 The logic module checks presence and source traceability, not semantic85 adequacy; a separate review step is needed to catch self-referential entries.86- Accepting a populated justification_source field without checking that the87 source category is one of the recognised kinds — an ad-hoc or invented88 category does not satisfy the traceability requirement.89- Skipping the duplicate-ID check and allowing two requirements with the same90 ID to each carry a different justification — the traceability of which91 justification belongs to which instance becomes undefined.92- Reading "no non-compliant count" as "fully compliant" on an empty input —93 the assess function raises on empty input precisely to prevent a vacuous pass.9495## Behavior contract (gate 3)9697The requirement-ID check, justification-text check, source-reference check,98source-category check, duplicate-ID check, and set-level compliance logic are99exercised by the gate 3 contract test:100scripts/test_e1006_char_justification.py against101scripts/e1006_char_justification_logic.py (stdlib unittest, offline). Run:102python3 scripts/test_e1006_char_justification.py103104## Compliance105106- ECSS standards are freely downloadable (ESA); cite the source and paraphrase107 per standards-map.yaml.108- compliance: STANDARDS-REF, gated: false.