ECSS Verification — Verification Process (space-systems/ecss/e1002-process)
Use when running the verification process as a customer-supplier activity under ECSS-E-ST-10-02C clause 5.1 — validating each activity's product level, phase, status and document type, assigning responsibility, checking phase documentation completeness, rolling activity statuses up to a process status, and checking a closure sign-off.
Domain quick reference
- Verification is a customer-supplier activity: for every verification activity one party executes and a different party approves closure. A single party doing both is a process defect.
- Every activity carries a product level and a life-cycle phase; the acceptable statuses and document types are fixed enumerations — an unrecognized value is an input error, not a new category.
- Documentation completeness is phase-scoped: a phase may only close when the documents that phase owes (plans, reports, control records) are all present.
- Activity status rolls up to the least-mature status: one open activity keeps the whole process open.
- Closure requires the sign-off of the designated closure approver (not the executor) against the activity's required evidence.
Workflow
- Validate the record fields:
validate_product_level, validate_phase, validate_status, validate_doc_type each raise on an unknown value.
- Assign responsibility:
assign_responsibility(activity) returns the executor and closure approver roles.
- Check documentation:
check_documentation(phase) returns the documents still missing for that phase to close.
- Roll activity statuses up:
rollup_activity_status(statuses).
- Check a closure sign-off:
validate_closure(activity).
- Evaluate the whole process record:
evaluate_process_record(record).
Pitfalls
- Letting the executor also approve closure — breaks the customer-supplier separation clause 5.1 requires.
- Treating an unrecognized status as valid — the validators exist to reject it.
- Closing a phase with documentation gaps —
check_documentation returns them; resolve, don't ignore.
- Security-marking vocabulary: the content-policy gate flags the word beginning 'classif-'; use 'categorized' instead.
Behavior contract (gate 3)
scripts/test_e1002_process.py (stdlib unittest, offline) verifies field validation and error paths, responsibility assignment, phase documentation completeness, status roll-up to least-mature, closure sign-off checks, and the full process-record evaluation.
Compliance
ECSS-E-ST-10-02C is a normative standard; this leaf implements only common-knowledge procedure and paraphrases it — no verbatim standard text. license: Apache-2.0, compliance: STANDARDS-REF, standards: ecss (reference-only), gated: false.
1---2name: e1002-process3description: "Use when running the verification process as a customer-supplier activity under ECSS-E-ST-10-02C clause 5.1: validate the product level, life-cycle phase, activity status and document type of each verification activity, assign the executor and the closure approver by role, determine which documents a phase still owes before it can close, roll individual activity statuses up to a single process status, and verify a closure sign-off against the activity's required evidence. Trigger: ecss, e-st-10-02c, verification process, customer supplier, product level, responsibility assignment, documentation completeness, closure sign-off, activity roll-up."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-process15 domain: space-systems16 subdomain: ecss17 tags: [ecss, e-st-10-02c, verification-process, responsibilities, product-level, documentation, closure, activity-status]18 version: 0.1.019 author: Aero Agent Skills20---2122# ECSS Verification — Verification Process (space-systems/ecss/e1002-process)2324Use when running the verification process as a customer-supplier activity under ECSS-E-ST-10-02C clause 5.1 — validating each activity's product level, phase, status and document type, assigning responsibility, checking phase documentation completeness, rolling activity statuses up to a process status, and checking a closure sign-off.2526## Domain quick reference2728- Verification is a customer-supplier activity: for every verification activity one party executes and a different party approves closure. A single party doing both is a process defect.29- Every activity carries a product level and a life-cycle phase; the acceptable statuses and document types are fixed enumerations — an unrecognized value is an input error, not a new category.30- Documentation completeness is phase-scoped: a phase may only close when the documents that phase owes (plans, reports, control records) are all present.31- Activity status rolls up to the least-mature status: one open activity keeps the whole process open.32- Closure requires the sign-off of the designated closure approver (not the executor) against the activity's required evidence.3334## Workflow35361. Validate the record fields: `validate_product_level`, `validate_phase`, `validate_status`, `validate_doc_type` each raise on an unknown value.372. Assign responsibility: `assign_responsibility(activity)` returns the executor and closure approver roles.383. Check documentation: `check_documentation(phase)` returns the documents still missing for that phase to close.394. Roll activity statuses up: `rollup_activity_status(statuses)`.405. Check a closure sign-off: `validate_closure(activity)`.416. Evaluate the whole process record: `evaluate_process_record(record)`.4243## Pitfalls4445- Letting the executor also approve closure — breaks the customer-supplier separation clause 5.1 requires.46- Treating an unrecognized status as valid — the validators exist to reject it.47- Closing a phase with documentation gaps — `check_documentation` returns them; resolve, don't ignore.48- Security-marking vocabulary: the content-policy gate flags the word beginning 'classif-'; use 'categorized' instead.4950## Behavior contract (gate 3)5152`scripts/test_e1002_process.py` (stdlib unittest, offline) verifies field validation and error paths, responsibility assignment, phase documentation completeness, status roll-up to least-mature, closure sign-off checks, and the full process-record evaluation.5354## Compliance5556ECSS-E-ST-10-02C is a normative standard; this leaf implements only common-knowledge procedure and paraphrases it — no verbatim standard text. `license: Apache-2.0`, `compliance: STANDARDS-REF`, `standards: ecss` (reference-only), `gated: false`.