ECSS Verification — Execution Control (space-systems/ecss/e1002-execution)
Use when the task is to run verification activities under ECSS-E-ST-10-02
clause 5.3.1 -- against the verification plan and control document, with
nonconformances and deviations controlled while the activity is live
rather than reconciled afterwards.
Domain quick reference
- Readiness is conjunctive, not a score. Approved procedure, available
facility, confirmed article configuration, qualified personnel: all
four hold or the activity does not start. Three out of four is not
seventy-five percent ready, it is not ready.
- A nonconformance raised during execution suspends the activity until
it is dispositioned. Suspension is a state the record implies, not a
decision someone remembers to make.
- A nonconformance with no recorded disposition is open. The default
runs toward stopping, because the alternative silently treats an
unanswered question as answered.
- A departure from the approved procedure needs approval before
execution continues. Approving it afterwards is the defect, not the
departure itself: the evidence was produced outside the procedure and
nobody agreed in advance that it would still be valid.
- The as-run record is reconciled against the as-planned steps in both
directions -- a planned step not run, and a step run that was never
planned. A deviation covering the step explains either one; an
unexplained difference in either direction invalidates the evidence.
- An activity with planned steps and no as-run record at all is a single
finding, not one per step. Nothing was recorded, and enumerating the
plan back at the reader adds nothing.
- The state is derived from the record, never read from a status field,
so a stale field cannot make a suspended activity look complete.
Suspension dominates: an open nonconformance outranks unmet readiness.
Workflow
- Check all four readiness conditions; record each unmet one.
- List nonconformances raised against the activity with no
disposition; each one suspends it.
- For each procedure deviation, confirm approval preceded execution.
- Reconcile as-run against as-planned in both directions, treating a
step covered by a deviation as explained.
- Derive the activity state: suspended if anything is open, planned if
readiness is unmet, ready if nothing has run, complete only when the
as-run reconciles.
- The activity's evidence enters the verification control document
only when it completed with no findings.
Pitfalls
- Starting on "substantially ready". The unmet condition is usually the
one that invalidates the run -- an article in the wrong configuration
produces perfectly good data about the wrong hardware.
- Treating a nonconformance with a blank disposition as resolved. The
blank is the signal that nobody has decided yet.
- Accepting a deviation approved after the run as equivalent to one
approved before. The approval is a prediction that the evidence will
still be valid; made afterwards it is only a description.
- Reconciling as-run against as-planned in one direction. Extra steps
nobody planned are as much a departure as planned steps skipped.
- Reading the activity's state from a stored status field, which lets a
suspended activity report complete because nobody updated it.
- Emitting one finding per planned step when no as-run record exists at
all, burying the single real problem in noise.
Behavior contract (gate 3)
The readiness, open-nonconformance, deviation-approval, as-run
reconciliation and derived-state logic is exercised by the gate 3
contract test: scripts/test_e1002_execution.py against
scripts/e1002_execution_logic.py (stdlib unittest, offline). Run:
python3 scripts/test_e1002_execution.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-execution3description: "Use when execute verification activities against the verification plan and control document under ECSS-E-ST-10-02 clause 5.3.1: confirm every readiness condition holds before an activity starts, suspend it while any nonconformance raised against it stays open, confirm each departure from the approved procedure was authorized before execution rather than after, reconcile the as-run steps against the as-planned steps, and derive the activity's true state from its own record. Trigger: ecss, e-st-10-02c, verification-execution, readiness-review, nonconformance, deviation-approval, as-run-record, activity-state."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-execution15 domain: space-systems16 subdomain: ecss17 tags: [ecss, e-st-10-02c, verification-execution, nonconformance, deviation-approval, as-run-record]18 version: 0.1.019 author: Aero Agent Skills20---2122# ECSS Verification — Execution Control (space-systems/ecss/e1002-execution)2324Use when the task is to run verification activities under ECSS-E-ST-10-0225clause 5.3.1 -- against the verification plan and control document, with26nonconformances and deviations controlled while the activity is live27rather than reconciled afterwards.2829## Domain quick reference3031- Readiness is conjunctive, not a score. Approved procedure, available32 facility, confirmed article configuration, qualified personnel: all33 four hold or the activity does not start. Three out of four is not34 seventy-five percent ready, it is not ready.35- A nonconformance raised during execution suspends the activity until36 it is dispositioned. Suspension is a state the record implies, not a37 decision someone remembers to make.38- A nonconformance with no recorded disposition is open. The default39 runs toward stopping, because the alternative silently treats an40 unanswered question as answered.41- A departure from the approved procedure needs approval *before*42 execution continues. Approving it afterwards is the defect, not the43 departure itself: the evidence was produced outside the procedure and44 nobody agreed in advance that it would still be valid.45- The as-run record is reconciled against the as-planned steps in both46 directions -- a planned step not run, and a step run that was never47 planned. A deviation covering the step explains either one; an48 unexplained difference in either direction invalidates the evidence.49- An activity with planned steps and no as-run record at all is a single50 finding, not one per step. Nothing was recorded, and enumerating the51 plan back at the reader adds nothing.52- The state is derived from the record, never read from a status field,53 so a stale field cannot make a suspended activity look complete.54 Suspension dominates: an open nonconformance outranks unmet readiness.5556## Workflow57581. Check all four readiness conditions; record each unmet one.592. List nonconformances raised against the activity with no60 disposition; each one suspends it.613. For each procedure deviation, confirm approval preceded execution.624. Reconcile as-run against as-planned in both directions, treating a63 step covered by a deviation as explained.645. Derive the activity state: suspended if anything is open, planned if65 readiness is unmet, ready if nothing has run, complete only when the66 as-run reconciles.676. The activity's evidence enters the verification control document68 only when it completed with no findings.6970## Pitfalls7172- Starting on "substantially ready". The unmet condition is usually the73 one that invalidates the run -- an article in the wrong configuration74 produces perfectly good data about the wrong hardware.75- Treating a nonconformance with a blank disposition as resolved. The76 blank is the signal that nobody has decided yet.77- Accepting a deviation approved after the run as equivalent to one78 approved before. The approval is a prediction that the evidence will79 still be valid; made afterwards it is only a description.80- Reconciling as-run against as-planned in one direction. Extra steps81 nobody planned are as much a departure as planned steps skipped.82- Reading the activity's state from a stored status field, which lets a83 suspended activity report complete because nobody updated it.84- Emitting one finding per planned step when no as-run record exists at85 all, burying the single real problem in noise.8687## Behavior contract (gate 3)8889The readiness, open-nonconformance, deviation-approval, as-run90reconciliation and derived-state logic is exercised by the gate 391contract test: scripts/test_e1002_execution.py against92scripts/e1002_execution_logic.py (stdlib unittest, offline). Run:93python3 scripts/test_e1002_execution.py9495## Compliance9697- ECSS standards are freely downloadable (ESA); cite the source and98 paraphrase per standards-map.yaml.99- compliance: STANDARDS-REF, gated: false.