ECSS SE Document Delivery Per Review (space-systems/ecss/e10-delivery-per-review)
Use when the task is planning or checking the systems-engineering (SE)
document delivery schedule for a space project under ECSS-E-ST-10C
Annex A (informative): which SE documents must be delivered or
re-baselined at which review milestone, and whether an actual review's
deliveries satisfy that schedule.
Domain quick reference
- ECSS-E-ST-10C Annex A is an informative table mapping SE documents
(e.g. mission description, SEP, specification tree, technical
specifications, interface control documents, verification/technical
budget reports) to the review milestones at which each is due,
either as a first delivery or a re-baseline/update.
- The review milestones follow the sibling systems-engineering leaf's
phase-gate sequence: MDR, PRR, SRR, PDR, CDR, QR, AR, FRR, CRR, ER.
- Being informative, Annex A is guidance for tailoring a project's own
document delivery schedule, not a fixed mandatory checklist -- a
project's schedule is the authoritative record this leaf checks
against, not the Annex A table itself.
- A document can be due at more than one review (first issue at one
gate, re-baseline at later gates); the schedule is a document x
review applicability matrix, not a one-to-one mapping.
Workflow
- Build the project's delivery schedule: for each SE document, record
the set of review milestones at which it must be delivered or
re-baselined (tailored from Annex A, agreed with the customer).
- Before a given review, list the documents the schedule requires for
that review.
- Compare against the documents actually delivered for that review:
- missing deliveries: scheduled for the review but not delivered.
- unplanned deliveries: delivered for the review but not scheduled
(flag for review -- may be a legitimate addition or a schedule
gap).
- A review's delivery is complete only when there are no missing
deliveries (unplanned deliveries do not block completeness but
must be reconciled into the schedule).
- Roll up across the full review sequence: report which reviews are
complete and which still have missing deliveries, to see delivery
readiness across the whole program.
Pitfalls
- Treating Annex A's informative table as a mandatory universal
checklist instead of tailoring it into the project's own schedule.
- Missing that a document is due again as a re-baseline at a later
review, not just once at its first-issue review.
- Blocking a review on an unplanned (extra) delivery instead of only
on missing scheduled deliveries.
- Confusing this leaf's document-delivery check with the sibling
systems-engineering leaf's review-gate/phase-exit readiness, which
checks that reviews themselves are completed, not that documents
were delivered on schedule.
Behavior contract (gate 3)
The delivery-schedule and review-readiness logic is exercised by the
gate 3 contract test: scripts/test_e10_delivery_per_review.py against
scripts/e10_delivery_per_review_logic.py (stdlib unittest, offline).
Run:
python3 scripts/test_e10_delivery_per_review.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-delivery-per-review3description: "Use when planning or checking which systems-engineering documents a space project must deliver or re-baseline at each review milestone per ECSS-E-ST-10C Annex A (informative): build the document-by-review delivery schedule, verify a given review's deliveries against it (missing and unplanned deliveries), and roll up readiness across the whole review sequence. Trigger: delivery schedule, document delivery per review, Annex A, review deliverables, MDR PRR SRR PDR CDR QR AR FRR CRR ER documents, ECSS-E-ST-10C Annex A."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-delivery-per-review15 domain: space-systems16 subdomain: ecss17 tags: [ecss, e-st-10c, annex-a, delivery-schedule, review, document-management]18 version: 0.1.019 author: Aero Agent Skills20---2122# ECSS SE Document Delivery Per Review (space-systems/ecss/e10-delivery-per-review)2324Use when the task is planning or checking the systems-engineering (SE)25document delivery schedule for a space project under ECSS-E-ST-10C26Annex A (informative): which SE documents must be delivered or27re-baselined at which review milestone, and whether an actual review's28deliveries satisfy that schedule.2930## Domain quick reference3132- ECSS-E-ST-10C Annex A is an informative table mapping SE documents33 (e.g. mission description, SEP, specification tree, technical34 specifications, interface control documents, verification/technical35 budget reports) to the review milestones at which each is due,36 either as a first delivery or a re-baseline/update.37- The review milestones follow the sibling systems-engineering leaf's38 phase-gate sequence: MDR, PRR, SRR, PDR, CDR, QR, AR, FRR, CRR, ER.39- Being informative, Annex A is guidance for tailoring a project's own40 document delivery schedule, not a fixed mandatory checklist -- a41 project's schedule is the authoritative record this leaf checks42 against, not the Annex A table itself.43- A document can be due at more than one review (first issue at one44 gate, re-baseline at later gates); the schedule is a document x45 review applicability matrix, not a one-to-one mapping.4647## Workflow48491. Build the project's delivery schedule: for each SE document, record50 the set of review milestones at which it must be delivered or51 re-baselined (tailored from Annex A, agreed with the customer).522. Before a given review, list the documents the schedule requires for53 that review.543. Compare against the documents actually delivered for that review:55 - missing deliveries: scheduled for the review but not delivered.56 - unplanned deliveries: delivered for the review but not scheduled57 (flag for review -- may be a legitimate addition or a schedule58 gap).594. A review's delivery is complete only when there are no missing60 deliveries (unplanned deliveries do not block completeness but61 must be reconciled into the schedule).625. Roll up across the full review sequence: report which reviews are63 complete and which still have missing deliveries, to see delivery64 readiness across the whole program.6566## Pitfalls6768- Treating Annex A's informative table as a mandatory universal69 checklist instead of tailoring it into the project's own schedule.70- Missing that a document is due again as a re-baseline at a later71 review, not just once at its first-issue review.72- Blocking a review on an unplanned (extra) delivery instead of only73 on missing scheduled deliveries.74- Confusing this leaf's document-delivery check with the sibling75 systems-engineering leaf's review-gate/phase-exit readiness, which76 checks that reviews themselves are completed, not that documents77 were delivered on schedule.7879## Behavior contract (gate 3)8081The delivery-schedule and review-readiness logic is exercised by the82gate 3 contract test: scripts/test_e10_delivery_per_review.py against83scripts/e10_delivery_per_review_logic.py (stdlib unittest, offline).84Run:85python3 scripts/test_e10_delivery_per_review.py8687## Compliance8889- ECSS standards are freely downloadable (ESA); cite the source and90 paraphrase per standards-map.yaml.91- compliance: STANDARDS-REF, gated: false.