ECSS System Engineering — Product User Manual DRD (space-systems/ecss/e10-pum-drd)
Use when the task is to produce or check the Product User Manual of
ECSS-E-ST-10C Annex P -- the document delivered with a product so that
someone who did not build it can operate, maintain and handle it safely.
Domain quick reference
- A manual is written against one configuration of one product and must
say which. A manual whose declared configuration differs from what was
delivered is not a documentation defect to be corrected in review --
it describes a different article, and the operator following it is
working from the wrong book.
- A declared-but-absent configuration and a mismatched one are separate
findings, because they are fixed differently: one is filled in, the
other means the wrong manual shipped.
- The required sections are fixed. An empty section and an absent one
are the same defect -- there is nothing to read either way -- so the
check looks at content, not at headings.
- Operators follow procedures by step number. A duplicate number or a
gap in the sequence is an execution hazard, not a typographic one:
under load, the reader jumps to a number that is ambiguous or absent.
- A hazard warning must precede the step it protects. A warning placed
after has already failed, because the operator reads it having
already acted. Position is the substance of the check, not presence.
- Hazard classes are a closed set. An unrecognized class cannot be
matched to a warning convention, so it stops the review.
- A maintenance task needs both an interval and its required resources.
Without an interval it is never scheduled; without stated tooling or
consumables it cannot be prepared for, and both turn planned
maintenance into unplanned downtime.
Workflow
- Confirm the manual declares a product configuration and that it
matches the delivered article.
- Check every required section for real content, reporting empty
sections alongside absent ones.
- For each procedure, check step numbering for duplicates and for a
sequence that does not run contiguously from one.
- For each hazardous step, confirm its warning is placed before the
step; reject an unrecognized hazard class outright.
- For each maintenance task, confirm both the interval and the
required resources are stated.
- The manual may ship only when the finding list is empty.
Pitfalls
- Checking that section headings exist rather than that they contain
anything. A manual of empty headings passes a structural check and
helps nobody.
- Accepting a hazard warning anywhere in the procedure. Placed after
the step, it documents the accident rather than preventing it.
- Treating step numbering as formatting. It is the operator's index
into the procedure, and a repeat or a gap is read under time pressure.
- Shipping a manual whose configuration was never updated after a
design change. It looks complete, and every limit in it may belong to
a different build.
- Recording a maintenance task with a resource list but no interval, so
it is well specified and never scheduled.
- Silently accepting a hazard class the warning convention does not
cover, which lets an unanalyzed hazard through with no warning rule
applied to it.
Behavior contract (gate 3)
The section-completeness, configuration-match, step-numbering,
hazard-warning-placement and maintenance-task logic is exercised by the
gate 3 contract test: scripts/test_e10_pum_drd.py against
scripts/e10_pum_drd_logic.py (stdlib unittest, offline). Run:
python3 scripts/test_e10_pum_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-pum-drd3description: "Use when produce or review a Product User Manual against the ECSS-E-ST-10C Annex P Document Requirements Definition: confirm the manual declares the product configuration it describes and that it matches what was delivered, confirm every required section is present and not empty, confirm procedure steps are numbered contiguously without repeats, confirm every hazardous step carries its warning ahead of the step, and confirm each maintenance task states its interval and required resources. Trigger: ecss, e-st-10-system-scope, product-user-manual, pum, annex-p-drd, operating-procedures, hazard-warnings, maintenance-interval, configuration-match."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-pum-drd15 domain: space-systems16 subdomain: ecss17 tags: [ecss, e-st-10-system-scope, product-user-manual, annex-p-drd, operating-procedures, hazard-warnings, maintenance-interval]18 version: 0.1.019 author: Aero Agent Skills20---2122# ECSS System Engineering — Product User Manual DRD (space-systems/ecss/e10-pum-drd)2324Use when the task is to produce or check the Product User Manual of25ECSS-E-ST-10C Annex P -- the document delivered with a product so that26someone who did not build it can operate, maintain and handle it safely.2728## Domain quick reference2930- A manual is written against one configuration of one product and must31 say which. A manual whose declared configuration differs from what was32 delivered is not a documentation defect to be corrected in review --33 it describes a different article, and the operator following it is34 working from the wrong book.35- A declared-but-absent configuration and a mismatched one are separate36 findings, because they are fixed differently: one is filled in, the37 other means the wrong manual shipped.38- The required sections are fixed. An empty section and an absent one39 are the same defect -- there is nothing to read either way -- so the40 check looks at content, not at headings.41- Operators follow procedures by step number. A duplicate number or a42 gap in the sequence is an execution hazard, not a typographic one:43 under load, the reader jumps to a number that is ambiguous or absent.44- A hazard warning must precede the step it protects. A warning placed45 after has already failed, because the operator reads it having46 already acted. Position is the substance of the check, not presence.47- Hazard classes are a closed set. An unrecognized class cannot be48 matched to a warning convention, so it stops the review.49- A maintenance task needs both an interval and its required resources.50 Without an interval it is never scheduled; without stated tooling or51 consumables it cannot be prepared for, and both turn planned52 maintenance into unplanned downtime.5354## Workflow55561. Confirm the manual declares a product configuration and that it57 matches the delivered article.582. Check every required section for real content, reporting empty59 sections alongside absent ones.603. For each procedure, check step numbering for duplicates and for a61 sequence that does not run contiguously from one.624. For each hazardous step, confirm its warning is placed before the63 step; reject an unrecognized hazard class outright.645. For each maintenance task, confirm both the interval and the65 required resources are stated.666. The manual may ship only when the finding list is empty.6768## Pitfalls6970- Checking that section headings exist rather than that they contain71 anything. A manual of empty headings passes a structural check and72 helps nobody.73- Accepting a hazard warning anywhere in the procedure. Placed after74 the step, it documents the accident rather than preventing it.75- Treating step numbering as formatting. It is the operator's index76 into the procedure, and a repeat or a gap is read under time pressure.77- Shipping a manual whose configuration was never updated after a78 design change. It looks complete, and every limit in it may belong to79 a different build.80- Recording a maintenance task with a resource list but no interval, so81 it is well specified and never scheduled.82- Silently accepting a hazard class the warning convention does not83 cover, which lets an unanalyzed hazard through with no warning rule84 applied to it.8586## Behavior contract (gate 3)8788The section-completeness, configuration-match, step-numbering,89hazard-warning-placement and maintenance-task logic is exercised by the90gate 3 contract test: scripts/test_e10_pum_drd.py against91scripts/e10_pum_drd_logic.py (stdlib unittest, offline). Run:92python3 scripts/test_e10_pum_drd.py9394## Compliance9596- ECSS standards are freely downloadable (ESA); cite the source and97 paraphrase per standards-map.yaml.98- compliance: STANDARDS-REF, gated: false.