ECSS Verification — Control and Close-out (space-systems/ecss/e1002-control-closeout)
Use when the task is to control verification through the verification
control document and finally close it out under ECSS-E-ST-10-02 clause
5.4.1 -- including the delivery of the verification database in
electronic form.
Domain quick reference
- Close-out is conjunctive. Every requirement closed, every
nonconformance dispositioned, every invoked waiver approved, and the
database delivered. A delivered database does not offset an open
nonconformance, and a clean nonconformance log does not offset a
partial delivery.
- Closing against a waiver is a real closure, but only when the waiver
reference names something the granting authority actually approved.
An unapproved waiver closes nothing -- it records that somebody
wanted to.
- A missing waiver reference and an unapproved one are different
findings: one is unrecorded, the other was recorded and refused.
- Every closed row cites evidence, including rows closed with a waiver.
The waiver explains why the requirement was not met; it does not
excuse the absence of a record of what was actually found.
- An open row needs no evidence yet. Applying the evidence check to
unfinished work generates findings against rows that are simply not
done.
- A nonconformance with no recorded state is open. The default runs
toward stopping, because an unanswered question must not close a
programme.
- The database is checked for completeness against the control
document's own rows. Delivered-but-partial is the characteristic
failure of this clause: the programme ends, and the evidence trail
has holes nobody will ever go back and fill.
- Machine-readability is part of delivery, not a nicety. A scanned
matrix satisfies "delivered" and defeats every later query the
database exists to answer.
Workflow
- Walk the control document rows and list every one not at a closed
status.
- For each row closed with a waiver, confirm the reference is present
and names an approved waiver.
- Confirm every closed row cites evidence.
- Confirm no nonconformance remains open, treating an absent state as
open.
- Check the database delivery: delivered at all, in the agreed format,
machine-readable, and carrying every row the control document holds.
- Declare close-out only when nothing is open and no finding stands.
Pitfalls
- Closing a programme on a waiver that was raised but never approved,
which converts an unmet requirement into a closed one by paperwork.
- Accepting a waiver closure with no evidence of what was actually
found, leaving no record of the departure the waiver permitted.
- Treating an unstated nonconformance state as dispositioned, so an
unanswered finding disappears at exactly the moment it matters most.
- Checking the database is delivered without checking it is complete.
Partial delivery passes every presence check and is the failure this
clause exists to prevent.
- Delivering a non-machine-readable export, which satisfies the word
"delivered" and defeats the purpose.
- Trading one close-out condition against another -- a strong evidence
set does not compensate for an undelivered database.
Behavior contract (gate 3)
The row-status, waiver-approval, closure-evidence, nonconformance and
database-delivery-completeness logic is exercised by the gate 3 contract
test: scripts/test_e1002_control_closeout.py against
scripts/e1002_control_closeout_logic.py (stdlib unittest, offline). Run:
python3 scripts/test_e1002_control_closeout.py
Compliance
- ECSS standards are freely downloadable (ESA); cite the source and
paraphrase per standards-map.yaml.
- compliance: STANDARDS-REF, gated: false.
1---2name: e1002-control-closeout3description: "Use when control and close out product verification under ECSS-E-ST-10-02 clause 5.4.1: confirm every verification control document row reached a closed status with evidence cited, confirm each closure taken against a waiver names a waiver the authority actually approved, confirm no nonconformance is still open, and confirm the verification database was delivered machine-readable in the agreed format covering every row the control document holds. Trigger: ecss, e-st-10-02c, verification-closeout, verification-control-document, waiver-approval, nonconformance, verification-database, electronic-delivery."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/e1002-control-closeout15 domain: space-systems16 subdomain: ecss17 tags: [ecss, e-st-10-02c, verification-closeout, verification-control-document, waiver-approval, verification-database]18 version: 0.1.019 author: Aero Agent Skills20---2122# ECSS Verification — Control and Close-out (space-systems/ecss/e1002-control-closeout)2324Use when the task is to control verification through the verification25control document and finally close it out under ECSS-E-ST-10-02 clause265.4.1 -- including the delivery of the verification database in27electronic form.2829## Domain quick reference3031- Close-out is conjunctive. Every requirement closed, every32 nonconformance dispositioned, every invoked waiver approved, and the33 database delivered. A delivered database does not offset an open34 nonconformance, and a clean nonconformance log does not offset a35 partial delivery.36- Closing against a waiver is a real closure, but only when the waiver37 reference names something the granting authority actually approved.38 An unapproved waiver closes nothing -- it records that somebody39 wanted to.40- A missing waiver reference and an unapproved one are different41 findings: one is unrecorded, the other was recorded and refused.42- Every closed row cites evidence, including rows closed with a waiver.43 The waiver explains why the requirement was not met; it does not44 excuse the absence of a record of what was actually found.45- An open row needs no evidence yet. Applying the evidence check to46 unfinished work generates findings against rows that are simply not47 done.48- A nonconformance with no recorded state is open. The default runs49 toward stopping, because an unanswered question must not close a50 programme.51- The database is checked for completeness against the control52 document's own rows. Delivered-but-partial is the characteristic53 failure of this clause: the programme ends, and the evidence trail54 has holes nobody will ever go back and fill.55- Machine-readability is part of delivery, not a nicety. A scanned56 matrix satisfies "delivered" and defeats every later query the57 database exists to answer.5859## Workflow60611. Walk the control document rows and list every one not at a closed62 status.632. For each row closed with a waiver, confirm the reference is present64 and names an approved waiver.653. Confirm every closed row cites evidence.664. Confirm no nonconformance remains open, treating an absent state as67 open.685. Check the database delivery: delivered at all, in the agreed format,69 machine-readable, and carrying every row the control document holds.706. Declare close-out only when nothing is open and no finding stands.7172## Pitfalls7374- Closing a programme on a waiver that was raised but never approved,75 which converts an unmet requirement into a closed one by paperwork.76- Accepting a waiver closure with no evidence of what was actually77 found, leaving no record of the departure the waiver permitted.78- Treating an unstated nonconformance state as dispositioned, so an79 unanswered finding disappears at exactly the moment it matters most.80- Checking the database is delivered without checking it is complete.81 Partial delivery passes every presence check and is the failure this82 clause exists to prevent.83- Delivering a non-machine-readable export, which satisfies the word84 "delivered" and defeats the purpose.85- Trading one close-out condition against another -- a strong evidence86 set does not compensate for an undelivered database.8788## Behavior contract (gate 3)8990The row-status, waiver-approval, closure-evidence, nonconformance and91database-delivery-completeness logic is exercised by the gate 3 contract92test: scripts/test_e1002_control_closeout.py against93scripts/e1002_control_closeout_logic.py (stdlib unittest, offline). Run:94python3 scripts/test_e1002_control_closeout.py9596## Compliance9798- ECSS standards are freely downloadable (ESA); cite the source and99 paraphrase per standards-map.yaml.100- compliance: STANDARDS-REF, gated: false.