ECSS System Engineering — Design Justification File DRD (space-systems/ecss/e10-djf-drd)
Use when the task is to assemble or review the Design Justification File
of ECSS-E-ST-10C Annex K -- the record that shows, requirement by
requirement, why the design is believed to meet its Technical
Specification, and what evidence carries that belief.
Domain quick reference
- A justification record has three parts, and all three are graded: the
method that produced the evidence (analysis, test, similarity,
inspection, review of design), the document the evidence lives in,
and the review status the evidence reached.
- The document reference is not metadata. The DJF is an index into the
evidence, so a record citing nothing has not filed evidence at all --
it is flagged whatever its status, accepted included.
- Requirement status is severity-ordered and the order matters: a
rejected record dominates, because rejected evidence must be
dispositioned rather than out-voted by an accepted record beside it.
Only then does an accepted record justify the requirement; draft-only
evidence leaves it open.
- A requirement with no record at all is its own outcome, distinct from
one whose evidence exists but is unfinished. The first is a planning
gap, the second an execution backlog, and they are closed by
different work.
- Similarity is a legitimate Annex K method, but a requirement whose
entire accepted argument is similarity carries no evidence about
this design. That is surfaced rather than passed -- it is a
judgement for a reviewer, not a defect the file can resolve itself.
- Method and status are validated before anything is graded. An
unrecognized value cannot be placed in the severity order at all, so
it stops the review instead of landing in a bucket.
- The file is complete only when the open, rejected and no-evidence
lists and the finding list are all empty.
Workflow
- Validate the method and review status of every justification record.
- Confirm each record cites the document holding its evidence; record
a traceability finding for any that does not.
- Resolve each requirement's status from its records under the
severity ordering: rejected, then justified, then open, then no
evidence.
- For each requirement whose accepted records are all similarity,
record a finding for the reviewer.
- Partition every requirement into exactly one status bucket,
rejecting a duplicate requirement identifier.
- The DJF supports the design only when nothing is open, rejected or
unevidenced and no finding stands.
Pitfalls
- Letting an accepted record cancel a rejected one on the same
requirement. The rejection is the finding; it closes through an
explicit disposition, not by being outnumbered.
- Accepting a record because the analysis was done, without a document
reference. An unlocatable analysis cannot be reviewed, which is the
whole function of the file.
- Filing a requirement with no evidence under "open". That buries a
planning gap inside an execution backlog.
- Treating similarity as equivalent to analysis or test when it is the
sole accepted method. Heritage says the previous design worked, not
that this one does.
- Reporting a percentage of requirements justified as the DJF verdict.
Annex K completeness is all-or-nothing across the specification.
- Grading a record whose method or status is unrecognized by guessing
the nearest known value; the review must stop and have the record
corrected.
Behavior contract (gate 3)
The method/status validation, record traceability, severity-ordered
requirement status, method-diversity, similarity-only and partition
logic is exercised by the gate 3 contract test:
scripts/test_e10_djf_drd.py against scripts/e10_djf_drd_logic.py
(stdlib unittest, offline). Run:
python3 scripts/test_e10_djf_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-djf-drd3description: "Use when assemble or review a product Design Justification File against the ECSS-E-ST-10C Annex K Document Requirements Definition: validate each justification record's method and review status, confirm every record cites the document its evidence lives in, resolve each requirement to justified, open, rejected-evidence or no-evidence under a severity ordering, surface a requirement whose accepted argument rests on similarity alone, and decide whether the file supports the design. Trigger: ecss, e-st-10-system-scope, design-justification-file, djf, annex-k-drd, justification-evidence, similarity-heritage, evidence-traceability."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-djf-drd15 domain: space-systems16 subdomain: ecss17 tags: [ecss, e-st-10-system-scope, design-justification-file, annex-k-drd, justification-evidence, evidence-traceability]18 version: 0.1.019 author: Aero Agent Skills20---2122# ECSS System Engineering — Design Justification File DRD (space-systems/ecss/e10-djf-drd)2324Use when the task is to assemble or review the Design Justification File25of ECSS-E-ST-10C Annex K -- the record that shows, requirement by26requirement, why the design is believed to meet its Technical27Specification, and what evidence carries that belief.2829## Domain quick reference3031- A justification record has three parts, and all three are graded: the32 method that produced the evidence (analysis, test, similarity,33 inspection, review of design), the document the evidence lives in,34 and the review status the evidence reached.35- The document reference is not metadata. The DJF is an index into the36 evidence, so a record citing nothing has not filed evidence at all --37 it is flagged whatever its status, accepted included.38- Requirement status is severity-ordered and the order matters: a39 rejected record dominates, because rejected evidence must be40 dispositioned rather than out-voted by an accepted record beside it.41 Only then does an accepted record justify the requirement; draft-only42 evidence leaves it open.43- A requirement with no record at all is its own outcome, distinct from44 one whose evidence exists but is unfinished. The first is a planning45 gap, the second an execution backlog, and they are closed by46 different work.47- Similarity is a legitimate Annex K method, but a requirement whose48 entire accepted argument is similarity carries no evidence about49 *this* design. That is surfaced rather than passed -- it is a50 judgement for a reviewer, not a defect the file can resolve itself.51- Method and status are validated before anything is graded. An52 unrecognized value cannot be placed in the severity order at all, so53 it stops the review instead of landing in a bucket.54- The file is complete only when the open, rejected and no-evidence55 lists and the finding list are all empty.5657## Workflow58591. Validate the method and review status of every justification record.602. Confirm each record cites the document holding its evidence; record61 a traceability finding for any that does not.623. Resolve each requirement's status from its records under the63 severity ordering: rejected, then justified, then open, then no64 evidence.654. For each requirement whose accepted records are all similarity,66 record a finding for the reviewer.675. Partition every requirement into exactly one status bucket,68 rejecting a duplicate requirement identifier.696. The DJF supports the design only when nothing is open, rejected or70 unevidenced and no finding stands.7172## Pitfalls7374- Letting an accepted record cancel a rejected one on the same75 requirement. The rejection is the finding; it closes through an76 explicit disposition, not by being outnumbered.77- Accepting a record because the analysis was done, without a document78 reference. An unlocatable analysis cannot be reviewed, which is the79 whole function of the file.80- Filing a requirement with no evidence under "open". That buries a81 planning gap inside an execution backlog.82- Treating similarity as equivalent to analysis or test when it is the83 sole accepted method. Heritage says the previous design worked, not84 that this one does.85- Reporting a percentage of requirements justified as the DJF verdict.86 Annex K completeness is all-or-nothing across the specification.87- Grading a record whose method or status is unrecognized by guessing88 the nearest known value; the review must stop and have the record89 corrected.9091## Behavior contract (gate 3)9293The method/status validation, record traceability, severity-ordered94requirement status, method-diversity, similarity-only and partition95logic is exercised by the gate 3 contract test:96scripts/test_e10_djf_drd.py against scripts/e10_djf_drd_logic.py97(stdlib unittest, offline). Run:98python3 scripts/test_e10_djf_drd.py99100## Compliance101102- ECSS standards are freely downloadable (ESA); cite the source and103 paraphrase per standards-map.yaml.104- compliance: STANDARDS-REF, gated: false.