e1002-vcd
Use when establishing and maintaining the Verification Control Document (VCD) under ECSS-E-ST-10-02C clause 5.2.8.2 and Annex B: validate a recorded verification method and status against their enumer
SKILL.mdskills/space-systems/ecss/e1002-vcd/SKILL.md
GitHubECSS Verification — Verification Control Document (space-systems/ecss/e1002-vcd)
Use when establishing and maintaining the Verification Control Document (VCD) under ECSS-E-ST-10-02C clause 5.2.8.2 and Annex B — validating method/status enumerations, checking method permission by requirement category, applicability and closure evidence, and rolling entries up to a program status.
Domain quick reference
- The VCD is the requirement-by-requirement record: for each requirement it states the verification method and the closure status with the evidence behind them.
- Method and status are enumerated: an unrecognized value is an input error, not a new category.
- Method permission is category-dependent: some requirement categories may only be closed by certain methods (e.g. a quantitative requirement cannot be closed by inspection alone).
- A 'closed' status must carry closure evidence; a closed status with no evidence is a defect.
- Entries roll up to a program status; the VCD is complete only when every applicable entry is clean.
Workflow
- Validate enumerations:
validate_verification_method(method),validate_verification_status(status). - Check permission:
allowed_methods_for_category(category)->method_selection_issues(entry). - Check applicability:
applicability_issues(entry). - Check closure evidence:
closure_issues(entry). - Evaluate one entry:
evaluate_vcd_entry(entry)->is_entry_clean(result). - Roll up + completeness:
vcd_status_rollup(entries)->is_vcd_complete(rollup); full reviewvcd_program_review(entries).
Pitfalls
- Closing a requirement with a method its category does not permit — a clause violation, not a judgment call.
- Marking a requirement closed with no closure evidence —
closure_issuesreturns it. - Rolling up only clean entries and dropping the rest — the roll-up must span every entry.
- Security-marking vocabulary: the content-policy gate flags the word beginning 'classif-'; use 'categorized' instead.
Behavior contract (gate 3)
scripts/test_e1002_vcd.py (stdlib unittest, offline) verifies method/status validation and error paths, category method permission, applicability and closure-evidence issues, per-entry evaluation, program roll-up, and VCD completeness.
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.