ECSS System Engineering — Legacy Data Pack Mapping (space-systems/ecss/e10-ddp-mapping)
Use when the task is to bring a heritage programme's existing design data
pack onto the ECSS document set, following the informative mapping
guidance of ECSS-E-ST-10C Annex R.
Domain quick reference
- A heritage conversion loses content in two ways, and they are found by
walking the mapping in opposite directions. Item-by-item finds content
that was dropped. Document-by-document finds an owed ECSS document that
nothing feeds. One walk cannot see the other's defect: every item can
be mapped and a required document still end up empty.
- Every legacy item gets an explicit disposition. Retiring content is a
legitimate outcome -- heritage packs carry material the ECSS set
genuinely does not want -- but it is a decision that must be recorded,
not an omission.
- A retired item carries a reason. Without one the conversion cannot be
reviewed, because nobody can tell deliberate retirement from content
that was simply missed.
- A retired item must claim no target. Content cannot be both carried
forward and dropped; that combination means two people dispositioned
the same item differently and neither saw the other.
- A carried-forward item must name at least one recognized target
document. An unrecognized target is rejected outright rather than
recorded, because it cannot be checked for coverage later.
- Annex R is informative. It guides the conversion; it does not relax the
normative DRDs the target documents must still satisfy once populated.
- The retired fraction is worth reporting on its own. A conversion that
retires most of a heritage pack may be correct, but it is a decision a
reviewer should see stated rather than infer.
Workflow
- Confirm legacy item identifiers are present and unique.
- Validate each item's disposition, and each target against the
recognized ECSS document set.
- For carried-forward items, confirm at least one target is named.
- For retired items, confirm a reason is recorded and no target is
claimed.
- Collect the documents that receive content, then walk the owed
document list and report each one nothing feeds.
- Report the retired fraction alongside the findings.
- The conversion is sound only when nothing was dropped without a
reason and no owed document was left unsourced.
Pitfalls
- Auditing the mapping only item-by-item. That proves nothing was
dropped and says nothing about whether the ECSS set came out complete.
- Treating an unmapped item as implicitly retired. Retirement is a
decision with a reason attached; silence is just lost content.
- Accepting an item marked retired that still lists a target, on the
assumption one field is stale. Both were written by someone, and the
disagreement is the finding.
- Recording a free-text target name. If it does not resolve to a
document in the set, coverage can never be computed against it.
- Reading Annex R's informative status as permission to skip the target
documents' own DRDs. The mapping says where content goes, not what the
destination must contain.
- Reporting a high mapped-item count as success while a required
document has no source at all.
Behavior contract (gate 3)
The disposition validation, target validation, per-item mapping,
reverse coverage walk and retired-fraction logic is exercised by the
gate 3 contract test: scripts/test_e10_ddp_mapping.py against
scripts/e10_ddp_mapping_logic.py (stdlib unittest, offline). Run:
python3 scripts/test_e10_ddp_mapping.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-ddp-mapping3description: "Use when convert a heritage programme's legacy design data pack onto the ECSS document set following the ECSS-E-ST-10C Annex R mapping guidance: validate each legacy item's disposition, confirm a carried-forward item names at least one recognized ECSS target document, confirm a retired item states why and claims no target, and walk the mapping in the opposite direction to find any owed ECSS document that no legacy content feeds. Trigger: ecss, e-st-10-system-scope, legacy-data-pack, annex-r-mapping, heritage-conversion, document-set, content-retirement, coverage."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-ddp-mapping15 domain: space-systems16 subdomain: ecss17 tags: [ecss, e-st-10-system-scope, legacy-data-pack, annex-r-mapping, heritage-conversion, document-set]18 version: 0.1.019 author: Aero Agent Skills20---2122# ECSS System Engineering — Legacy Data Pack Mapping (space-systems/ecss/e10-ddp-mapping)2324Use when the task is to bring a heritage programme's existing design data25pack onto the ECSS document set, following the informative mapping26guidance of ECSS-E-ST-10C Annex R.2728## Domain quick reference2930- A heritage conversion loses content in two ways, and they are found by31 walking the mapping in opposite directions. Item-by-item finds content32 that was dropped. Document-by-document finds an owed ECSS document that33 nothing feeds. One walk cannot see the other's defect: every item can34 be mapped and a required document still end up empty.35- Every legacy item gets an explicit disposition. Retiring content is a36 legitimate outcome -- heritage packs carry material the ECSS set37 genuinely does not want -- but it is a decision that must be recorded,38 not an omission.39- A retired item carries a reason. Without one the conversion cannot be40 reviewed, because nobody can tell deliberate retirement from content41 that was simply missed.42- A retired item must claim no target. Content cannot be both carried43 forward and dropped; that combination means two people dispositioned44 the same item differently and neither saw the other.45- A carried-forward item must name at least one recognized target46 document. An unrecognized target is rejected outright rather than47 recorded, because it cannot be checked for coverage later.48- Annex R is informative. It guides the conversion; it does not relax the49 normative DRDs the target documents must still satisfy once populated.50- The retired fraction is worth reporting on its own. A conversion that51 retires most of a heritage pack may be correct, but it is a decision a52 reviewer should see stated rather than infer.5354## Workflow55561. Confirm legacy item identifiers are present and unique.572. Validate each item's disposition, and each target against the58 recognized ECSS document set.593. For carried-forward items, confirm at least one target is named.604. For retired items, confirm a reason is recorded and no target is61 claimed.625. Collect the documents that receive content, then walk the owed63 document list and report each one nothing feeds.646. Report the retired fraction alongside the findings.657. The conversion is sound only when nothing was dropped without a66 reason and no owed document was left unsourced.6768## Pitfalls6970- Auditing the mapping only item-by-item. That proves nothing was71 dropped and says nothing about whether the ECSS set came out complete.72- Treating an unmapped item as implicitly retired. Retirement is a73 decision with a reason attached; silence is just lost content.74- Accepting an item marked retired that still lists a target, on the75 assumption one field is stale. Both were written by someone, and the76 disagreement is the finding.77- Recording a free-text target name. If it does not resolve to a78 document in the set, coverage can never be computed against it.79- Reading Annex R's informative status as permission to skip the target80 documents' own DRDs. The mapping says where content goes, not what the81 destination must contain.82- Reporting a high mapped-item count as success while a required83 document has no source at all.8485## Behavior contract (gate 3)8687The disposition validation, target validation, per-item mapping,88reverse coverage walk and retired-fraction logic is exercised by the89gate 3 contract test: scripts/test_e10_ddp_mapping.py against90scripts/e10_ddp_mapping_logic.py (stdlib unittest, offline). Run:91python3 scripts/test_e10_ddp_mapping.py9293## Compliance9495- ECSS standards are freely downloadable (ESA); cite the source and96 paraphrase per standards-map.yaml.97- compliance: STANDARDS-REF, gated: false.