ECSS Structures — Safe-Life Item Compliance (space-systems/ecss/safe-life-compliance)
Use when the task is verifying safe-life fracture-control compliance under
ECSS-E-ST-32C clause 6.3.2 -- categorizing structural items as safe-life or
fail-safe, checking that crack-growth life and residual strength evidence meet
the required margins, and confirming documented analysis or test support exists
for every safe-life item.
Domain quick reference
- Clause 6.3.2 recognizes two fracture-control approaches for structural items:
safe-life (no in-service inspection path; the item must demonstrate by
analysis or test that an assumed initial crack cannot grow to a critical size
within the full service life, with a scatter factor applied) and fail-safe
(redundant load paths or periodic inspectability; a different compliance route
applies). Every structural item must be categorized into exactly one approach
before its compliance evidence is assessed.
- Crack-growth life is the computed or tested number of load cycles (or
service hours) from the assumed initial flaw size to the critical crack size.
For a safe-life item to be compliant, this life must be at least equal to the
design life multiplied by the scatter factor required by the standard (a factor
of four on life is the typical ECSS default; project-specific values override
it). A shortfall -- crack-growth life below the required multiple -- is a
direct compliance failure regardless of whether residual strength passes.
- Residual strength is the load-carrying capacity of the structure at the
end-of-life crack size; it must be shown to meet or exceed the design limit
load. A residual-strength margin of zero (i.e., residual strength exactly
equals limit load) is the minimum acceptable threshold; any ratio below one
is a failure. This check is independent of the crack-growth life check: both
must pass.
- Evidence for a safe-life item must be either a documented crack-growth
analysis (fracture-mechanics computation with material crack-growth data and
load spectrum) or a crack-growth test, or both. An item with no recorded
evidence type cannot be evaluated and must be flagged before the compliance
assessment proceeds.
Workflow
- Inventory every structural item subject to the fracture-control programme
and categorize each one as safe-life or fail-safe. Reject any item whose
category is not one of those two before it enters the compliance check.
- For each safe-life item, confirm that at least one evidence type -- analysis
or test -- is on record. Flag items with no evidence and stop their
assessment; do not carry forward items with unknown evidence status.
- Retrieve the crack-growth life (cycles or hours) and the design life for
each evidenced safe-life item. Multiply the design life by the applicable
scatter factor (default four; use the project-specified value if one is set).
Compare: if crack-growth life is below the required multiple, record a FAIL
with the numerical shortfall.
- Retrieve the residual strength (force or stress, consistent units with limit
load) and the limit load for each safe-life item. Compute the ratio. If the
ratio is below one, record a FAIL with the deficit.
- For each safe-life item, both the crack-growth life check and the residual-
strength check must show PASS for the item to be compliant. A MISSING_DATA
outcome on either check is treated as non-compliant until the data is
supplied.
- Aggregate findings across all items. Report the count of compliant and
non-compliant items, list the item IDs with failures, and confirm whether
the full set is compliant. Fail-safe items pass at the categorization step
(their detailed fracture-control evidence follows a separate path not covered
by this leaf).
Pitfalls
- Applying the source crack-growth rate directly as a life figure without
multiplying by the scatter factor -- the clause requires the demonstrated life
to cover the design life times the scatter factor; omitting the factor gives
a non-conservative result and an incorrect PASS.
- Treating a MISSING_DATA outcome as a pass -- if the crack-growth life or
residual strength is not on record, the item has not been shown to be
compliant; absence of data is a finding, not a clean slate.
- Mixing units between residual strength and limit load (e.g. one in kN, the
other in kN·m) -- the ratio is only valid when both quantities are expressed
in the same unit; a unit mismatch gives a meaningless margin number.
- Concluding that a pass on residual strength implies a pass on crack-growth
life, or vice versa -- the two checks are independent; an item can have
adequate residual strength at end-of-life crack size while still failing
the crack-growth life check if that crack size is reached too quickly.
- Skipping the evidence check and proceeding directly to the numerical checks
-- if the evidence type is unknown or absent, the numerical values may come
from an unverified source; the evidence check gates the numerical checks.
Behavior contract (gate 3)
The item-categorization, crack-growth-life, residual-strength, evidence, and
aggregate-compliance logic is exercised by the gate 3 contract test:
scripts/test_safe_life_compliance.py against
scripts/safe_life_compliance_logic.py (stdlib unittest, offline). Run:
python3 scripts/test_safe_life_compliance.py
Compliance
- ECSS standards are freely downloadable (ESA); cite the source and paraphrase
per standards-map.yaml.
- compliance: STANDARDS-REF, gated: false.
1---2name: safe-life-compliance3description: "Use when verify safe-life fracture-control compliance for structural items per ECSS-E-ST-32C clause 6.3.2: categorize each structural item as safe-life or fail-safe, gather crack-growth analysis and test evidence for every safe-life item, confirm that crack-growth life meets or exceeds the design life multiplied by the applicable scatter factor, check that residual strength at end-of-life crack size meets the limit-load requirement, and flag items with missing analysis, test documentation, or margin shortfall. Trigger: ecss, e-st-32-structures-scope, safe-life, crack-growth, residual-strength, fracture-control, structural-margin, fatigue-crack."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/safe-life-compliance15 domain: space-systems16 subdomain: ecss17 tags: [ecss, e-st-32-structures-scope, safe-life, crack-growth, residual-strength, fracture-control, structural-margin, fatigue-crack]18 version: 0.1.019 author: Aero Agent Skills20---2122# ECSS Structures — Safe-Life Item Compliance (space-systems/ecss/safe-life-compliance)2324Use when the task is verifying safe-life fracture-control compliance under25ECSS-E-ST-32C clause 6.3.2 -- categorizing structural items as safe-life or26fail-safe, checking that crack-growth life and residual strength evidence meet27the required margins, and confirming documented analysis or test support exists28for every safe-life item.2930## Domain quick reference3132- Clause 6.3.2 recognizes two fracture-control approaches for structural items:33 **safe-life** (no in-service inspection path; the item must demonstrate by34 analysis or test that an assumed initial crack cannot grow to a critical size35 within the full service life, with a scatter factor applied) and **fail-safe**36 (redundant load paths or periodic inspectability; a different compliance route37 applies). Every structural item must be categorized into exactly one approach38 before its compliance evidence is assessed.39- **Crack-growth life** is the computed or tested number of load cycles (or40 service hours) from the assumed initial flaw size to the critical crack size.41 For a safe-life item to be compliant, this life must be at least equal to the42 design life multiplied by the scatter factor required by the standard (a factor43 of four on life is the typical ECSS default; project-specific values override44 it). A shortfall -- crack-growth life below the required multiple -- is a45 direct compliance failure regardless of whether residual strength passes.46- **Residual strength** is the load-carrying capacity of the structure at the47 end-of-life crack size; it must be shown to meet or exceed the design limit48 load. A residual-strength margin of zero (i.e., residual strength exactly49 equals limit load) is the minimum acceptable threshold; any ratio below one50 is a failure. This check is independent of the crack-growth life check: both51 must pass.52- **Evidence** for a safe-life item must be either a documented crack-growth53 analysis (fracture-mechanics computation with material crack-growth data and54 load spectrum) or a crack-growth test, or both. An item with no recorded55 evidence type cannot be evaluated and must be flagged before the compliance56 assessment proceeds.5758## Workflow59601. Inventory every structural item subject to the fracture-control programme61 and categorize each one as safe-life or fail-safe. Reject any item whose62 category is not one of those two before it enters the compliance check.632. For each safe-life item, confirm that at least one evidence type -- analysis64 or test -- is on record. Flag items with no evidence and stop their65 assessment; do not carry forward items with unknown evidence status.663. Retrieve the crack-growth life (cycles or hours) and the design life for67 each evidenced safe-life item. Multiply the design life by the applicable68 scatter factor (default four; use the project-specified value if one is set).69 Compare: if crack-growth life is below the required multiple, record a FAIL70 with the numerical shortfall.714. Retrieve the residual strength (force or stress, consistent units with limit72 load) and the limit load for each safe-life item. Compute the ratio. If the73 ratio is below one, record a FAIL with the deficit.745. For each safe-life item, both the crack-growth life check and the residual-75 strength check must show PASS for the item to be compliant. A MISSING_DATA76 outcome on either check is treated as non-compliant until the data is77 supplied.786. Aggregate findings across all items. Report the count of compliant and79 non-compliant items, list the item IDs with failures, and confirm whether80 the full set is compliant. Fail-safe items pass at the categorization step81 (their detailed fracture-control evidence follows a separate path not covered82 by this leaf).8384## Pitfalls8586- Applying the source crack-growth rate directly as a life figure without87 multiplying by the scatter factor -- the clause requires the demonstrated life88 to cover the design life times the scatter factor; omitting the factor gives89 a non-conservative result and an incorrect PASS.90- Treating a MISSING_DATA outcome as a pass -- if the crack-growth life or91 residual strength is not on record, the item has not been shown to be92 compliant; absence of data is a finding, not a clean slate.93- Mixing units between residual strength and limit load (e.g. one in kN, the94 other in kN·m) -- the ratio is only valid when both quantities are expressed95 in the same unit; a unit mismatch gives a meaningless margin number.96- Concluding that a pass on residual strength implies a pass on crack-growth97 life, or vice versa -- the two checks are independent; an item can have98 adequate residual strength at end-of-life crack size while still failing99 the crack-growth life check if that crack size is reached too quickly.100- Skipping the evidence check and proceeding directly to the numerical checks101 -- if the evidence type is unknown or absent, the numerical values may come102 from an unverified source; the evidence check gates the numerical checks.103104## Behavior contract (gate 3)105106The item-categorization, crack-growth-life, residual-strength, evidence, and107aggregate-compliance logic is exercised by the gate 3 contract test:108scripts/test_safe_life_compliance.py against109scripts/safe_life_compliance_logic.py (stdlib unittest, offline). Run:110python3 scripts/test_safe_life_compliance.py111112## Compliance113114- ECSS standards are freely downloadable (ESA); cite the source and paraphrase115 per standards-map.yaml.116- compliance: STANDARDS-REF, gated: false.