ECSS System Engineering — Requirements Baseline Management (space-systems/ecss/e10-req-baseline)
Use when the task is to establish and control the requirements
baseline of a configuration item (CI) under ECSS-E-ST-10C clause
5.2.3.9 -- checking a CI's requirement set for baseline readiness at
an agreed project milestone, freezing it into a baseline record, and
tracking every later change to a baselined requirement through an
authorized change request.
Domain quick reference
- A CI's requirement set is baselined at an agreed project milestone
(e.g. SRR, PDR, CDR, QR), not on an arbitrary date -- the milestone
is the trigger that closes the requirement definition activity for
that phase and opens the change-control activity.
- A requirement is baseline-ready only when it is approved (not
draft, in review, or withdrawn), carries requirement text, and
carries a verification method; a requirement missing any one of
these is a distinct, independently reported gap, because fixing one
gap does not imply the others are fixed too.
- Two requirements sharing the same identifier within one CI's set is
a baseline-blocking defect in its own right -- it breaks
traceability between the requirement and its verification evidence
even if both copies are individually approved.
- Once a baseline is established, the requirement set behind it is
frozen: an addition, a modification, or a deletion against a
baselined requirement is only authorized when it carries an approved
change request. A baseline that has not yet been established has no
change-control obligation -- there is nothing frozen to protect yet.
Workflow
- Assemble the CI's full requirement set for the target milestone.
Reject an unrecognized requirement status or milestone name before
the review proceeds -- an unrecognized value is a data problem to
fix, not a baseline gap to report.
- For each requirement, check approval status, requirement text, and
verification method independently, and report every gap found (not
just the first). Separately scan the set for duplicate requirement
identifiers.
- A CI with zero requirements at the milestone is itself a finding --
an empty set is not vacuously ready.
- Establish the baseline only when the full review comes back with no
violations; an ineligible attempt is rejected, not recorded with a
caveat, so an incomplete baseline can never be mistaken for a
complete one.
- After establishment, route every proposed change (add, modify,
delete) against a baselined requirement through the change-control
check: a change without an approved change request is flagged, and
the baseline itself must be in "established" status before any
change control can be applied against it.
- Aggregate the change-control findings for the baseline; the
baseline is not change-controlled until that list is empty.
Pitfalls
- Baselining a requirement set that has an unset verification method
because the requirement text itself looks complete -- text and
verification method are separate readiness gates and both must be
satisfied.
- Treating a duplicate requirement identifier as harmless when both
copies happen to be approved -- the duplicate breaks the one-to-one
link to verification evidence regardless of each copy's status.
- Recording an ineligible baseline attempt "with exceptions noted"
instead of rejecting it -- clause 5.2.3.9 baseline control depends on
the baseline record meaning the set was actually ready, not that it
was reviewed and waved through anyway.
- Applying change control to a baseline that was never established --
there is no frozen reference to change against, so the check must
reject the attempt rather than silently approve or silently flag
every change.
Behavior contract (gate 3)
The requirement-readiness, duplicate-identifier, milestone-baseline,
and change-control logic is exercised by the gate 3 contract test:
scripts/test_e10_req_baseline.py against
scripts/e10_req_baseline_logic.py (stdlib unittest, offline). Run:
python3 scripts/test_e10_req_baseline.py
Compliance
- ECSS standards are freely downloadable (ESA); cite the source and
paraphrase per standards-map.yaml.
- compliance: STANDARDS-REF, gated: false.
1---2name: e10-req-baseline3description: "Use when establishing or controlling the requirements baseline for a configuration item (CI) under ECSS-E-ST-10C clause 5.2.3.9: classify each requirement's approval status ahead of an agreed baseline milestone, verify it carries requirement text and a verification method, identify duplicate requirement identifiers within the set, define the baseline record once every requirement in the set is ready, and validate every subsequent addition, modification, or deletion of a baselined requirement against an approved change request. Trigger: ecss, e-st-10c, requirements baseline, baseline management, configuration item, milestone review, change control, requirement verification."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/e10-req-baseline15 domain: space-systems16 subdomain: ecss17 tags: [ecss, e-st-10c, requirements-baseline, baseline-management, configuration-item, change-control]18 version: 0.1.019 author: Aero Agent Skills20---2122# ECSS System Engineering — Requirements Baseline Management (space-systems/ecss/e10-req-baseline)2324Use when the task is to establish and control the requirements25baseline of a configuration item (CI) under ECSS-E-ST-10C clause265.2.3.9 -- checking a CI's requirement set for baseline readiness at27an agreed project milestone, freezing it into a baseline record, and28tracking every later change to a baselined requirement through an29authorized change request.3031## Domain quick reference3233- A CI's requirement set is baselined at an agreed project milestone34 (e.g. SRR, PDR, CDR, QR), not on an arbitrary date -- the milestone35 is the trigger that closes the requirement definition activity for36 that phase and opens the change-control activity.37- A requirement is baseline-ready only when it is approved (not38 draft, in review, or withdrawn), carries requirement text, and39 carries a verification method; a requirement missing any one of40 these is a distinct, independently reported gap, because fixing one41 gap does not imply the others are fixed too.42- Two requirements sharing the same identifier within one CI's set is43 a baseline-blocking defect in its own right -- it breaks44 traceability between the requirement and its verification evidence45 even if both copies are individually approved.46- Once a baseline is established, the requirement set behind it is47 frozen: an addition, a modification, or a deletion against a48 baselined requirement is only authorized when it carries an approved49 change request. A baseline that has not yet been established has no50 change-control obligation -- there is nothing frozen to protect yet.5152## Workflow53541. Assemble the CI's full requirement set for the target milestone.55 Reject an unrecognized requirement status or milestone name before56 the review proceeds -- an unrecognized value is a data problem to57 fix, not a baseline gap to report.582. For each requirement, check approval status, requirement text, and59 verification method independently, and report every gap found (not60 just the first). Separately scan the set for duplicate requirement61 identifiers.623. A CI with zero requirements at the milestone is itself a finding --63 an empty set is not vacuously ready.644. Establish the baseline only when the full review comes back with no65 violations; an ineligible attempt is rejected, not recorded with a66 caveat, so an incomplete baseline can never be mistaken for a67 complete one.685. After establishment, route every proposed change (add, modify,69 delete) against a baselined requirement through the change-control70 check: a change without an approved change request is flagged, and71 the baseline itself must be in "established" status before any72 change control can be applied against it.736. Aggregate the change-control findings for the baseline; the74 baseline is not change-controlled until that list is empty.7576## Pitfalls7778- Baselining a requirement set that has an unset verification method79 because the requirement text itself looks complete -- text and80 verification method are separate readiness gates and both must be81 satisfied.82- Treating a duplicate requirement identifier as harmless when both83 copies happen to be approved -- the duplicate breaks the one-to-one84 link to verification evidence regardless of each copy's status.85- Recording an ineligible baseline attempt "with exceptions noted"86 instead of rejecting it -- clause 5.2.3.9 baseline control depends on87 the baseline record meaning the set was actually ready, not that it88 was reviewed and waved through anyway.89- Applying change control to a baseline that was never established --90 there is no frozen reference to change against, so the check must91 reject the attempt rather than silently approve or silently flag92 every change.9394## Behavior contract (gate 3)9596The requirement-readiness, duplicate-identifier, milestone-baseline,97and change-control logic is exercised by the gate 3 contract test:98scripts/test_e10_req_baseline.py against99scripts/e10_req_baseline_logic.py (stdlib unittest, offline). Run:100python3 scripts/test_e10_req_baseline.py101102## Compliance103104- ECSS standards are freely downloadable (ESA); cite the source and105 paraphrase per standards-map.yaml.106- compliance: STANDARDS-REF, gated: false.