ECSS System Engineering — Requirements Justification File DRD (space-systems/ecss/e10-rjf-drd)
Use when the task is to compile or audit the Requirements Justification
File of ECSS-E-ST-10C Annex O -- the record of why each requirement
reads as it does, so that a later reviewer can re-derive the choice
rather than inherit it.
Domain quick reference
- Every requirement carries three things: a derivation basis (a parent
requirement, an analysis, an applicable standard, heritage, or a
stated mission need), a rationale in its own words, and an attributed
author.
- The basis and the requirement's level must agree. A requirement
derived from a parent must name that parent. A top-level requirement
cannot derive from one -- there is nothing above it -- so a
parent-derived top-level row hides an unjustified requirement behind
a trace that cannot exist.
- A top-level requirement rests on something external: an applicable
standard or a stated mission need. Heritage is not enough at the
apex, because "we did it this way before" explains a choice inside a
design, not the existence of a system-level requirement.
- A parent recorded alongside a non-parent basis is fine -- an analysis
that refined an inherited requirement legitimately has both -- so
that combination is not a finding.
- The characteristic failure of this file is not a blank field: it is a
rationale that restates the requirement. Every column is populated,
nothing is explained, and a presence check passes it. A rationale
identical to the requirement, or wholly contained in its wording,
justifies nothing.
- Attribution matters because the file exists to be questioned later. A
rationale nobody signed cannot be taken up with anyone.
- The file is complete only when no requirement carries a finding.
Workflow
- Confirm requirement identifiers are present and unique.
- Validate each requirement's derivation basis against the recognized
set.
- Check the rationale: present, long enough to carry an argument, and
not a restatement of the requirement itself. A missing rationale
short-circuits the rest -- there is nothing to inspect.
- Check the basis against the requirement's level: parent basis needs
a named parent, a top-level requirement needs an external basis.
- Confirm each rationale is attributed to an author.
- Aggregate; a requirement is justified only when it carries no
finding, and the file is complete only when all are.
Pitfalls
- Grading the file on field completeness. A restating rationale fills
every field and explains nothing, which is precisely how an RJF
decays into a formality.
- Accepting a top-level requirement derived from a parent. The trace
points at something that does not exist, and the requirement is
effectively unjustified.
- Treating heritage as a sufficient basis at system level. It explains
a design choice, not why the requirement is there at all.
- Flagging a requirement that records a parent alongside an analysis
basis. Refining an inherited requirement legitimately has both, and
flagging it trains reviewers to ignore findings.
- Reporting a missing rationale and a too-short rationale as two
findings on the same row; absence is one defect, checked first.
- Leaving a rationale unattributed on the grounds that the team wrote
it. The file's purpose is to let a later reviewer ask someone.
Behavior contract (gate 3)
The basis validation, restatement detection, rationale, basis/level
agreement and attribution logic is exercised by the gate 3 contract
test: scripts/test_e10_rjf_drd.py against scripts/e10_rjf_drd_logic.py
(stdlib unittest, offline). Run:
python3 scripts/test_e10_rjf_drd.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-rjf-drd3description: "Use when compile or audit a Requirements Justification File against the ECSS-E-ST-10C Annex O Document Requirements Definition: validate each requirement's derivation basis, confirm a parent-derived requirement names its parent and that a top-level requirement rests on a standard or mission need instead, detect a rationale that merely restates the requirement it is meant to justify, confirm each rationale is attributed, and decide whether every requirement is justified. Trigger: ecss, e-st-10-system-scope, requirements-justification-file, rjf, annex-o-drd, derivation-basis, requirement-rationale, attribution."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-rjf-drd15 domain: space-systems16 subdomain: ecss17 tags: [ecss, e-st-10-system-scope, requirements-justification-file, annex-o-drd, derivation-basis, requirement-rationale]18 version: 0.1.019 author: Aero Agent Skills20---2122# ECSS System Engineering — Requirements Justification File DRD (space-systems/ecss/e10-rjf-drd)2324Use when the task is to compile or audit the Requirements Justification25File of ECSS-E-ST-10C Annex O -- the record of *why* each requirement26reads as it does, so that a later reviewer can re-derive the choice27rather than inherit it.2829## Domain quick reference3031- Every requirement carries three things: a derivation basis (a parent32 requirement, an analysis, an applicable standard, heritage, or a33 stated mission need), a rationale in its own words, and an attributed34 author.35- The basis and the requirement's level must agree. A requirement36 derived from a parent must name that parent. A top-level requirement37 cannot derive from one -- there is nothing above it -- so a38 parent-derived top-level row hides an unjustified requirement behind39 a trace that cannot exist.40- A top-level requirement rests on something external: an applicable41 standard or a stated mission need. Heritage is not enough at the42 apex, because "we did it this way before" explains a choice inside a43 design, not the existence of a system-level requirement.44- A parent recorded alongside a non-parent basis is fine -- an analysis45 that refined an inherited requirement legitimately has both -- so46 that combination is not a finding.47- The characteristic failure of this file is not a blank field: it is a48 rationale that restates the requirement. Every column is populated,49 nothing is explained, and a presence check passes it. A rationale50 identical to the requirement, or wholly contained in its wording,51 justifies nothing.52- Attribution matters because the file exists to be questioned later. A53 rationale nobody signed cannot be taken up with anyone.54- The file is complete only when no requirement carries a finding.5556## Workflow57581. Confirm requirement identifiers are present and unique.592. Validate each requirement's derivation basis against the recognized60 set.613. Check the rationale: present, long enough to carry an argument, and62 not a restatement of the requirement itself. A missing rationale63 short-circuits the rest -- there is nothing to inspect.644. Check the basis against the requirement's level: parent basis needs65 a named parent, a top-level requirement needs an external basis.665. Confirm each rationale is attributed to an author.676. Aggregate; a requirement is justified only when it carries no68 finding, and the file is complete only when all are.6970## Pitfalls7172- Grading the file on field completeness. A restating rationale fills73 every field and explains nothing, which is precisely how an RJF74 decays into a formality.75- Accepting a top-level requirement derived from a parent. The trace76 points at something that does not exist, and the requirement is77 effectively unjustified.78- Treating heritage as a sufficient basis at system level. It explains79 a design choice, not why the requirement is there at all.80- Flagging a requirement that records a parent alongside an analysis81 basis. Refining an inherited requirement legitimately has both, and82 flagging it trains reviewers to ignore findings.83- Reporting a missing rationale and a too-short rationale as two84 findings on the same row; absence is one defect, checked first.85- Leaving a rationale unattributed on the grounds that the team wrote86 it. The file's purpose is to let a later reviewer ask someone.8788## Behavior contract (gate 3)8990The basis validation, restatement detection, rationale, basis/level91agreement and attribution logic is exercised by the gate 3 contract92test: scripts/test_e10_rjf_drd.py against scripts/e10_rjf_drd_logic.py93(stdlib unittest, offline). Run:94python3 scripts/test_e10_rjf_drd.py9596## Compliance9798- ECSS standards are freely downloadable (ESA); cite the source and99 paraphrase per standards-map.yaml.100- compliance: STANDARDS-REF, gated: false.