ECSS System Engineering — Coordinate Systems Document Maintenance (space-systems/ecss/e1009-documentation)
Use when the task is to maintain the Coordinate Systems Document (CSD) across
the spacecraft project life cycle under ECSS-E-ST-10C §5.2.2 — establishing
and updating each coordinate system definition, enforcing documentation
completeness and lifecycle discipline, and verifying phase coverage.
Domain quick reference
- The CSD is the single controlled reference listing every coordinate system
used in the spacecraft project. Each entry covers one coordinate system:
a unique identifier, a descriptive name, an origin description, axis
definitions for the x/y/z triad, the parent reference frame, the project
phases in which that system is applicable, and an entry status.
- Entry status follows a fixed path: draft (under preparation) →
review (under verification) → approved (controlled baseline) →
superseded (replaced by a later revision). Skipping states or reversing
to a prior state without a rework step is a documentation non-conformance.
- The CSD document itself has a lifecycle state that mirrors the entry
maturity: the document may not be declared approved while it still carries
draft or review-status entries that govern active project phases.
- Phase coverage means that for each project phase (A through E), at least
one coordinate system entry must list that phase in its applicable_phases
field. A phase with no applicable coordinate system is a gap that indicates
either missing entries or incorrect phase attribution.
Workflow
- Collect the current list of coordinate systems in use across all subsystems.
For each system, assign a unique identifier, capture the origin description,
define each axis of the right-hand triad with a non-empty prose description,
record the parent reference frame, and list the project phases for which
the definition is applicable.
- Validate every entry against the required field set. Reject entries with
missing fields, empty axis descriptions, unknown status values, or empty
applicable-phase lists before they enter the controlled document.
- Check identifier uniqueness across all entries. Duplicate identifiers
indicate either a split definition that must be merged or a transcription
error; resolve before issuing the document revision.
- For each entry whose status is changing, verify the transition is on the
permitted path: draft -> review, review -> approved, review -> draft
(rework), or approved -> superseded. Reject any other direction.
- Check that every project phase listed in the programme's scope is covered
by at least one approved or review-status entry. Report missing phases as
documentation gaps.
- Compute the CSD readiness score to track overall maturity. Score factors
are document-level field completeness, lifecycle state, and the fraction
of entries that individually pass validation. A score below 80 signals
that the CSD is not ready for a controlled-document release.
- Produce a consolidated findings list: entry-level issues keyed by
identifier, document-level issues, duplicate identifiers, missing phase
coverage gaps, and the readiness score. The CSD revision may only be
issued when all findings are resolved.
Pitfalls
- Approving the document while individual entries remain in draft state —
the document lifecycle state must reflect the lowest maturity of its
active entries; a premature approval is a traceability non-conformance.
- Accepting an empty or whitespace-only axis definition as satisfactory —
an axis without a prose description cannot be verified against drawings
or models, making the entry effectively unusable for design checks.
- Treating phase coverage as optional when a phase is not yet active —
coordinate system definitions must be in place before the phase begins,
not after; missing coverage at phase entry is a late capture.
- Merging two coordinate system definitions under one identifier to reduce
the entry count — each coordinate system must have its own unique
identifier; combined entries create ambiguity in interface documents and
data packages.
Behavior contract (gate 3)
The entry validation, identifier uniqueness, lifecycle transition, phase
coverage, and readiness scoring logic is exercised by the gate 3 contract
test: scripts/test_e1009_documentation.py against
scripts/e1009_documentation_logic.py (stdlib unittest, offline). Run:
python3 scripts/test_e1009_documentation.py
Compliance
- ECSS standards are freely downloadable (ESA); cite the source and
paraphrase per standards-map.yaml.
- compliance: STANDARDS-REF, gated: false.
1---2name: e1009-documentation3description: "Use when maintain the Coordinate Systems Document (CSD) across the4 spacecraft project life cycle under ECSS-E-ST-10C §5.2.2: define each coordinate5 system with a unique identifier, origin, axis triad, and reference frame; validate6 entry completeness; enforce permissible lifecycle state transitions (draft -> review7 -> approved -> superseded); verify that required project phases each carry at least8 one applicable coordinate system; and compute a CSD readiness score to track documentation9 maturity. Trigger: ecss, e-st-10-system-scope, coordinate-systems-document, csd,10 reference-frame, axis-definition, lifecycle, project-phases, documentation-maturity."11license: Apache-2.012compliance: STANDARDS-REF13standards:14 - id: ecss15 reference-only: true16gated: false17domain: space-systems18pack: space-systems19compatibility: "agentskills.io SKILL.md; any SKILL.md host (Claude Code, Hermes, OpenClaw)"20metadata:21 source: https://skillmd.com/skills/ashfordeou/e1009-documentation22 domain: space-systems23 subdomain: ecss24 tags: [ecss, e-st-10-system-scope, coordinate-systems-document, csd, reference-frame, axis-definition, lifecycle, project-phases]25 version: 0.1.026 author: Aero Agent Skills27---2829# ECSS System Engineering — Coordinate Systems Document Maintenance (space-systems/ecss/e1009-documentation)3031Use when the task is to maintain the Coordinate Systems Document (CSD) across32the spacecraft project life cycle under ECSS-E-ST-10C §5.2.2 — establishing33and updating each coordinate system definition, enforcing documentation34completeness and lifecycle discipline, and verifying phase coverage.3536## Domain quick reference3738- The CSD is the single controlled reference listing every coordinate system39 used in the spacecraft project. Each entry covers one coordinate system:40 a unique identifier, a descriptive name, an origin description, axis41 definitions for the x/y/z triad, the parent reference frame, the project42 phases in which that system is applicable, and an entry status.43- Entry status follows a fixed path: draft (under preparation) →44 review (under verification) → approved (controlled baseline) →45 superseded (replaced by a later revision). Skipping states or reversing46 to a prior state without a rework step is a documentation non-conformance.47- The CSD document itself has a lifecycle state that mirrors the entry48 maturity: the document may not be declared approved while it still carries49 draft or review-status entries that govern active project phases.50- Phase coverage means that for each project phase (A through E), at least51 one coordinate system entry must list that phase in its applicable_phases52 field. A phase with no applicable coordinate system is a gap that indicates53 either missing entries or incorrect phase attribution.5455## Workflow56571. Collect the current list of coordinate systems in use across all subsystems.58 For each system, assign a unique identifier, capture the origin description,59 define each axis of the right-hand triad with a non-empty prose description,60 record the parent reference frame, and list the project phases for which61 the definition is applicable.622. Validate every entry against the required field set. Reject entries with63 missing fields, empty axis descriptions, unknown status values, or empty64 applicable-phase lists before they enter the controlled document.653. Check identifier uniqueness across all entries. Duplicate identifiers66 indicate either a split definition that must be merged or a transcription67 error; resolve before issuing the document revision.684. For each entry whose status is changing, verify the transition is on the69 permitted path: draft -> review, review -> approved, review -> draft70 (rework), or approved -> superseded. Reject any other direction.715. Check that every project phase listed in the programme's scope is covered72 by at least one approved or review-status entry. Report missing phases as73 documentation gaps.746. Compute the CSD readiness score to track overall maturity. Score factors75 are document-level field completeness, lifecycle state, and the fraction76 of entries that individually pass validation. A score below 80 signals77 that the CSD is not ready for a controlled-document release.787. Produce a consolidated findings list: entry-level issues keyed by79 identifier, document-level issues, duplicate identifiers, missing phase80 coverage gaps, and the readiness score. The CSD revision may only be81 issued when all findings are resolved.8283## Pitfalls8485- Approving the document while individual entries remain in draft state —86 the document lifecycle state must reflect the lowest maturity of its87 active entries; a premature approval is a traceability non-conformance.88- Accepting an empty or whitespace-only axis definition as satisfactory —89 an axis without a prose description cannot be verified against drawings90 or models, making the entry effectively unusable for design checks.91- Treating phase coverage as optional when a phase is not yet active —92 coordinate system definitions must be in place before the phase begins,93 not after; missing coverage at phase entry is a late capture.94- Merging two coordinate system definitions under one identifier to reduce95 the entry count — each coordinate system must have its own unique96 identifier; combined entries create ambiguity in interface documents and97 data packages.9899## Behavior contract (gate 3)100101The entry validation, identifier uniqueness, lifecycle transition, phase102coverage, and readiness scoring logic is exercised by the gate 3 contract103test: scripts/test_e1009_documentation.py against104scripts/e1009_documentation_logic.py (stdlib unittest, offline). Run:105python3 scripts/test_e1009_documentation.py106107## Compliance108109- ECSS standards are freely downloadable (ESA); cite the source and110 paraphrase per standards-map.yaml.111- compliance: STANDARDS-REF, gated: false.