ECSS Data Package Cover Page (space-systems/ecss/q20-eidp-example-cover)
Use when the task is the Annex F worked data package cover of
ECSS-Q-ST-20C taken as the standard header format: a package is being
issued, reissued or received, and the question is whether its front sheet
identifies the package, agrees with the index and carries three real
signatures.
Domain quick reference
- The example's value is the field order and the number pattern, not the
wording. Project, contract, item, part and serial number, package
number, issue, issue date, document count, index reference and the
customer acceptance block -- always those, always in that order.
- The package number is derived, not chosen. Built from the contract
number and the serial number it is unique by construction, so a cover
whose number does not rebuild from its own fields is either a copy of
another package's cover or a package pointing at the wrong item.
- The approval block is three signatures because it is three people. One
name in two roles makes the check self-made, which is the one defect
that leaves the block looking complete.
- The signatures have an order and a ceiling. Prepared, then checked, then
approved -- and none of them after the cover's own issue date, because a
signature dated later was added to a sheet already sent out. Same-day
signatures are ordinary and are accepted.
- The document count is reconcilable. It is not a description of the
package, it is a claim about the index behind the cover, and the index
is what settles it. A line listed twice inflates the count while the
package is short.
- The customer acceptance block is the only optional field. It is blank on
every package at issue and filled on receipt, so grading it as mandatory
rejects every cover the moment it is raised.
Workflow
- Refuse a header carrying a field the cover has no place for, so a local
variant is caught rather than silently dropped.
- Normalise each field by kind: identifiers trimmed and lowered, issue
and document count positive integers, the issue date an ISO day.
- Refuse a blank mandatory field, leaving the customer acceptance block
free to be empty.
- Rebuild the package number from the contract and serial number and
compare it with the one printed.
- Validate the approval block by role, refusing an unknown role, then
raise an unsigned role, a repeated name, a signature out of order and a
signature later than the cover issue date.
- Reconcile the declared document count with the index, raising a
repeated index line separately from the count itself.
- Render the header with labels aligned to one column and return the
verdict.
Pitfalls
- Typing the package number instead of deriving it. A hand-typed number
survives every check on the page and points at the wrong item.
- Counting signatures rather than signatories. Three filled rows with two
names is an unchecked package.
- Reading the signature dates only against each other. A correctly ordered
set can still sit after the issue date, which means the sheet went out
unsigned.
- Treating the customer acceptance block as mandatory. It is filled by the
receiving organisation, not the issuer.
- Trusting the document count. It is a claim about the index, and a
duplicated index line is the usual reason the two disagree.
Behavior contract (gate 3)
The header field order, the unknown-field refusal, the mandatory-field and
integer validation, the package number derivation and comparison, the
approval block role validation with the duplicate-name, signing-order and
issue-date rules, and the document count to index reconciliation are
exercised by the gate 3 contract test:
scripts/test_q20_eidp_example_cover.py against
scripts/q20_eidp_example_cover_logic.py (stdlib unittest, offline). Run:
python3 scripts/test_q20_eidp_example_cover.py
Compliance
- ECSS standards are freely downloadable (ESA); cite the source and
paraphrase per standards-map.yaml.
- compliance: STANDARDS-REF, gated: false.
1---2name: q20-eidp-example-cover3description: "Prepare and assess the end item data package cover page of ECSS-Q-ST-20C Annex F, used as the house header format for the Annex B package: hold the field order the worked example fixes, refuse a blank mandatory field or a non-positive issue and document count, rebuild the package number from the contract and serial number, check the three-signature approval block for one person holding two roles or signatures taken out of order or after the cover issue, and reconcile the declared document count with the index. Use when a package cover is raised, reissued or checked on receipt. Trigger: ecss, q-st-20c-annex-f, eidp-cover-page, eidp-header-format, eidp-number-pattern, eidp-approval-block, eidp-document-count."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/q20-eidp-example-cover15 domain: space-systems16 subdomain: ecss17 tags: [ecss, q-st-20c-quality-assurance-scope, q20-eidp-example-cover, eidp-cover-page-header, eidp-cover-field-order, eidp-number-format, eidp-cover-approval-block-chain, eidp-cover-document-count-check]18 version: 0.1.019 author: Aero Agent Skills20---2122# ECSS Data Package Cover Page (space-systems/ecss/q20-eidp-example-cover)2324Use when the task is the Annex F worked data package cover of25ECSS-Q-ST-20C taken as the standard header format: a package is being26issued, reissued or received, and the question is whether its front sheet27identifies the package, agrees with the index and carries three real28signatures.2930## Domain quick reference3132- The example's value is the field order and the number pattern, not the33 wording. Project, contract, item, part and serial number, package34 number, issue, issue date, document count, index reference and the35 customer acceptance block -- always those, always in that order.36- The package number is derived, not chosen. Built from the contract37 number and the serial number it is unique by construction, so a cover38 whose number does not rebuild from its own fields is either a copy of39 another package's cover or a package pointing at the wrong item.40- The approval block is three signatures because it is three people. One41 name in two roles makes the check self-made, which is the one defect42 that leaves the block looking complete.43- The signatures have an order and a ceiling. Prepared, then checked, then44 approved -- and none of them after the cover's own issue date, because a45 signature dated later was added to a sheet already sent out. Same-day46 signatures are ordinary and are accepted.47- The document count is reconcilable. It is not a description of the48 package, it is a claim about the index behind the cover, and the index49 is what settles it. A line listed twice inflates the count while the50 package is short.51- The customer acceptance block is the only optional field. It is blank on52 every package at issue and filled on receipt, so grading it as mandatory53 rejects every cover the moment it is raised.5455## Workflow56571. Refuse a header carrying a field the cover has no place for, so a local58 variant is caught rather than silently dropped.592. Normalise each field by kind: identifiers trimmed and lowered, issue60 and document count positive integers, the issue date an ISO day.613. Refuse a blank mandatory field, leaving the customer acceptance block62 free to be empty.634. Rebuild the package number from the contract and serial number and64 compare it with the one printed.655. Validate the approval block by role, refusing an unknown role, then66 raise an unsigned role, a repeated name, a signature out of order and a67 signature later than the cover issue date.686. Reconcile the declared document count with the index, raising a69 repeated index line separately from the count itself.707. Render the header with labels aligned to one column and return the71 verdict.7273## Pitfalls7475- Typing the package number instead of deriving it. A hand-typed number76 survives every check on the page and points at the wrong item.77- Counting signatures rather than signatories. Three filled rows with two78 names is an unchecked package.79- Reading the signature dates only against each other. A correctly ordered80 set can still sit after the issue date, which means the sheet went out81 unsigned.82- Treating the customer acceptance block as mandatory. It is filled by the83 receiving organisation, not the issuer.84- Trusting the document count. It is a claim about the index, and a85 duplicated index line is the usual reason the two disagree.8687## Behavior contract (gate 3)8889The header field order, the unknown-field refusal, the mandatory-field and90integer validation, the package number derivation and comparison, the91approval block role validation with the duplicate-name, signing-order and92issue-date rules, and the document count to index reconciliation are93exercised by the gate 3 contract test:94scripts/test_q20_eidp_example_cover.py against95scripts/q20_eidp_example_cover_logic.py (stdlib unittest, offline). Run:96python3 scripts/test_q20_eidp_example_cover.py9798## Compliance99100- ECSS standards are freely downloadable (ESA); cite the source and101 paraphrase per standards-map.yaml.102- compliance: STANDARDS-REF, gated: false.