ECSS Nonconformance Control — Close-Out and Retained Records (space-systems/ecss/q1009-closeout)
Use when the task is the close-out step of ECSS-Q-ST-10-09C clause
5.4.2 — deciding whether a nonconformance report has actually met the
criteria that let it be closed, and what has to be retained once it is.
Domain quick reference
- Closure is a verification, not a filing step. Four things are shown
against criteria fixed in advance: the granted disposition was
carried out and checked, the agreed actions were completed and shown
effective, the records the report rests on exist, and the people
entitled to close it have signed.
- Carried out and checked are two criteria, not one. An item that was
reworked but never re-inspected against the grant has an unverified
disposition, and closing on it puts an unproven repair into the
as-built record.
- Conditions attached to the disposition close before the report does.
A conditional grant whose analysis or inspection is still outstanding
is an open item wearing a closed label.
- The record set depends on the route. Every closure holds the report
itself, the disposition record and the verification evidence; a route
that left a departure in the hardware additionally holds the approved
concession and the as-built configuration update; a report that
agreed actions holds their closure evidence.
- Signature authority follows severity. Product assurance and
engineering sign every closure; a major nonconformance also needs the
customer, because the customer granted the disposition in the first
place.
- A closed report is a retained report. The set stays available for the
period the programme declares, and the closure date fixes when that
period ends — the next question about that hardware usually arrives
years after the board has moved on.
Workflow
- Take the identifier, the granted disposition and the severity, and
reject a case that cannot name them rather than closing on a
partially described report.
- Check the disposition twice: that it was carried out, and that what
was carried out was verified against what was granted.
- Count the conditions still attached to the grant; any open condition
holds the closure regardless of how complete the rest looks.
- Check the agreed actions are verified effective, and check the
opposite direction too — a closure claiming verified actions on a
report that agreed none is describing something that did not happen.
- Derive the record set the route owes, compare it with what is held,
and name what is absent rather than reporting a count.
- Check the closure signatures against the roles the severity
requires, naming the missing ones.
- Compute the retention end date from the closure date and the
declared retention period, and report any shortfall against the
programme requirement.
- Close only with every criterion met; otherwise report the unmet
criteria together, so one board sitting can clear them all.
Pitfalls
- Closing on the disposition alone. The disposition is one of four
criteria; a report closed with its actions still running leaves the
cause in place and the record says the case was handled.
- Treating a signature as agreement that the criteria were met rather
than a check that they were. The verification comes first; the
signature records that it happened.
- Filing a departure closure without the as-built configuration update.
The hardware now differs from the drawing, and the only place that
difference was ever going to be recorded is the configuration record.
- Counting a retention period from the date of the nonconformance
rather than from closure. The period covers the closed record, and
starting it early can retire the file while the hardware is still
flying.
- Closing a major nonconformance on internal signatures because the
customer is slow to respond. The customer granted the disposition;
closing without them removes the only party who can confirm the grant
was honoured.
- Clearing an open condition by noting it in the closure text. A
condition closes with the evidence it named, not with a sentence in
the report that closes over it.
Behavior contract (gate 3)
The disposition verification, condition and action checks, record-set
derivation, signature roles, retention arithmetic and the closure
verdict are exercised by the gate 3 contract test:
scripts/test_q1009_closeout.py against scripts/q1009_closeout_logic.py
(stdlib unittest, offline). Run: python3 scripts/test_q1009_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: q1009-closeout3description: "Verify that a nonconformance has met its close-out criteria under ECSS-Q-ST-10-09C clause 5.4.2 before the report is closed. Use when an NCR is proposed for closure, when the retained record set has to be checked against the route that was taken, or when closure signatures and retention are in question: confirm the granted disposition was carried out and checked, hold closure while a condition or an agreed action is unfinished, name the records a departure route additionally owes, and compute how long the closed report has to stay available. Trigger: ecss, q-st-10-09c, ncr-closure-criteria, disposition-verification, capa-completion-check, closure-signature-roles, retained-record-set, ncr-retention-period."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/q1009-closeout15 domain: space-systems16 subdomain: ecss17 tags: [ecss, q-st-10-09c-nonconformance-scope, q1009-closeout, ncr-closure-criteria, disposition-verification, capa-completion-check, closure-signature-roles, retained-record-set, ncr-retention-period]18 version: 0.1.019 author: Aero Agent Skills20---2122# ECSS Nonconformance Control — Close-Out and Retained Records (space-systems/ecss/q1009-closeout)2324Use when the task is the close-out step of ECSS-Q-ST-10-09C clause255.4.2 — deciding whether a nonconformance report has actually met the26criteria that let it be closed, and what has to be retained once it is.2728## Domain quick reference2930- Closure is a verification, not a filing step. Four things are shown31 against criteria fixed in advance: the granted disposition was32 carried out and checked, the agreed actions were completed and shown33 effective, the records the report rests on exist, and the people34 entitled to close it have signed.35- Carried out and checked are two criteria, not one. An item that was36 reworked but never re-inspected against the grant has an unverified37 disposition, and closing on it puts an unproven repair into the38 as-built record.39- Conditions attached to the disposition close before the report does.40 A conditional grant whose analysis or inspection is still outstanding41 is an open item wearing a closed label.42- The record set depends on the route. Every closure holds the report43 itself, the disposition record and the verification evidence; a route44 that left a departure in the hardware additionally holds the approved45 concession and the as-built configuration update; a report that46 agreed actions holds their closure evidence.47- Signature authority follows severity. Product assurance and48 engineering sign every closure; a major nonconformance also needs the49 customer, because the customer granted the disposition in the first50 place.51- A closed report is a retained report. The set stays available for the52 period the programme declares, and the closure date fixes when that53 period ends — the next question about that hardware usually arrives54 years after the board has moved on.5556## Workflow57581. Take the identifier, the granted disposition and the severity, and59 reject a case that cannot name them rather than closing on a60 partially described report.612. Check the disposition twice: that it was carried out, and that what62 was carried out was verified against what was granted.633. Count the conditions still attached to the grant; any open condition64 holds the closure regardless of how complete the rest looks.654. Check the agreed actions are verified effective, and check the66 opposite direction too — a closure claiming verified actions on a67 report that agreed none is describing something that did not happen.685. Derive the record set the route owes, compare it with what is held,69 and name what is absent rather than reporting a count.706. Check the closure signatures against the roles the severity71 requires, naming the missing ones.727. Compute the retention end date from the closure date and the73 declared retention period, and report any shortfall against the74 programme requirement.758. Close only with every criterion met; otherwise report the unmet76 criteria together, so one board sitting can clear them all.7778## Pitfalls7980- Closing on the disposition alone. The disposition is one of four81 criteria; a report closed with its actions still running leaves the82 cause in place and the record says the case was handled.83- Treating a signature as agreement that the criteria were met rather84 than a check that they were. The verification comes first; the85 signature records that it happened.86- Filing a departure closure without the as-built configuration update.87 The hardware now differs from the drawing, and the only place that88 difference was ever going to be recorded is the configuration record.89- Counting a retention period from the date of the nonconformance90 rather than from closure. The period covers the closed record, and91 starting it early can retire the file while the hardware is still92 flying.93- Closing a major nonconformance on internal signatures because the94 customer is slow to respond. The customer granted the disposition;95 closing without them removes the only party who can confirm the grant96 was honoured.97- Clearing an open condition by noting it in the closure text. A98 condition closes with the evidence it named, not with a sentence in99 the report that closes over it.100101## Behavior contract (gate 3)102103The disposition verification, condition and action checks, record-set104derivation, signature roles, retention arithmetic and the closure105verdict are exercised by the gate 3 contract test:106scripts/test_q1009_closeout.py against scripts/q1009_closeout_logic.py107(stdlib unittest, offline). Run: python3 scripts/test_q1009_closeout.py108109## Compliance110111- ECSS standards are freely downloadable (ESA); cite the source and112 paraphrase per standards-map.yaml.113- compliance: STANDARDS-REF, gated: false.