Document 116

SEBoK *Engineered Resilience and Adaptability*, Distilled

framework

SEBoK Engineered Resilience and Adaptability, Distilled

Third-batch SEBoK distillation, batch 5 doc 5. System Resilience (Part 6 cluster on quality attributes) defines resilience as "the ability to provide required capability when facing adversity" (Brtis, McEvilley 2016). The three-layer framework (3 Fundamental Objectives / 17 Means Objectives / 40+ Techniques) is universal-sibling lattice (Cluster A) at three nested rungs simultaneously. The three Fundamental Objectives (Avoid / Withstand / Recover) are Cluster A at the response-stage rung and admit a partial-order reading on the temporal-precedence axis (universal-sibling-with-ordinal-axis sub-form, paralleling SE-071 SoS four-type taxonomy). Loss-Driven Systems Engineering (LDSE) is the institutional ground that composes resilience with reliability, safety, security, availability, maintainability — six siblings sharing common adversities, requirements, technical approaches: Cluster A at the loss-discipline rung. Resilience is the canonical Cluster G (SIPE) worked example: capability-under-adversity emerges at and above a coherence-density threshold of avoid + withstand + recover techniques; below threshold the system is brittle, above threshold resilience is the system property. This is Cluster G's first SIPE-as-emergent-system-property instance (prior instances were institutional/maturity); resilience supplies the canonical engineered-system-scale SIPE worked example. Six clusters compose; Cluster G stress-test passes — resilience is structurally an emergent-only system property.

I. Source

II. Source Read

The INCOSE Resilient Systems Working Group defines resilience as "the ability to provide required capability when facing adversity" (Brtis, McEvilley 2016), extending the materials-science "rebounding" definition to engineered systems and encompassing both proactive (before adversity) and reactive (after adversity) perspectives. Three Fundamental Objectives: avoid adversity (eliminate or reduce exposure), withstand adversity (resist capability degradation under stress), recover from adversity (restore lost capability after degradation). Three-layer framework: Layer 1 (3 Fundamental Objectives), Layer 2 (17 Means Objectives — adapt, anticipate, constrain, continue, degrade gracefully, disaggregate, evolve, fortify, monitor, prevent, repair, replace, tolerate, understand, etc.), Layer 3 (40+ Techniques — redundancy, modularity, fault tolerance, diversification, etc.). Loss-Driven Systems Engineering (LDSE) positions resilience alongside reliability, safety, security, availability, maintainability — these disciplines share common adversities, requirements, technical approaches. Resilience requirements pattern: operational concept, capability metrics, target values, adversity sources/types, stresses, timeframes, resilience metrics, constraints, often varying temporally across scenarios. Position: Part 6 Related Disciplines, Quality Attributes; companion glossary terms include absorption, flexibility, tolerance, capacity, recovery, defense in depth, drift correction, complexity avoidance, etc.

III. Structural Read

Cluster A (universal-sibling lattice, Doc 572 Appendix D), three nested rungs. First rung: 3 Fundamental Objectives (Avoid / Withstand / Recover) bind every resilience engagement universally; the discriminator is response-stage. Second rung: 17 Means Objectives bind every resilience engagement aspect-wise. Third rung: 40+ Techniques are the implementation lattice. Three nested Cluster A lattices in one article is structurally noteworthy and exceeds the two-co-located pattern observed in Docs 678/680. The three-layer framework is the cleanest SEBoK case of nested universal-sibling lattices.

Cluster A sub-form: universal-sibling-with-ordinal-axis (SE-039 §VII.5 candidate from SE-071). The three Fundamental Objectives carry a temporal-precedence ordinal: Avoid precedes Withstand precedes Recover in the unfolding of an adversity event. Universal-sibling on aspect (each binds every resilience engagement) plus ordinal on the temporal axis. This is the second canonical instance of the sub-form after SoS four-type central-authority partial order; the sub-form is now confirmed at two SEBoK pages and is load-bearing for Cluster A synthesis.

Cluster G (SIPE, Doc 541), canonical engineered-system-scale worked example. Resilience is the cleanest SEBoK case of a property that emerges at and above a coherence-density threshold in a system whose components and interactions have crossed it. Below threshold (insufficient avoid + withstand + recover techniques composed coherently) the system is brittle; above threshold the system has resilience as a system property. The threshold is a structural-emergence threshold in Doc 541's sense. Prior Cluster G instances (SE-027 ESE, SE-033 capability, SE-034 CMMI maturity) operate at the institutional or maturity rungs; resilience operates at the engineered-system rung. Cluster G gains its first engineered-system-scale instance and the sub-population becomes diverse enough for synthesis.

Cluster A (fourth instance in this article), at the loss-discipline rung. LDSE composes resilience with reliability, safety, security, availability, maintainability — six siblings sharing "common adversities, requirements, and technical approaches." The six disciplines are universal-sibling at the loss-engineering-aspect rung; the discriminator is what kind of loss the discipline is engineering against. Cluster A density now tops twenty.

Cluster F (pulverization, Doc 445). The resilience requirements pattern (operational concept, capability metrics, target values, adversity sources/types, stresses, timeframes, resilience metrics, constraints) is a forward-pulverization template at the requirements rung — every requirement names an anticipated adversity to be pulverized against. Cluster F gains an instance.

Cluster H (hypostatic boundary, Doc 372). "Capability under adversity" is functional throughout; resilience does not become a metaphysical property of the system, only an operational characteristic. Doc 372 binds; the corpus accepts the framing.

Cluster I (pin-art / temporal-concurrency, Doc 572 Appendix C). "Resilience metrics often varying temporally across scenarios" is canonical pin-art: resilience is pinned across operational time scales. Cluster I gains an adversity-temporal instance.

IV. Tier-Tags

  • Resilience definition (Brtis, McEvilley 2016 / INCOSE RSWG) — π / α as cited.
  • Three Fundamental Objectives — π / α as cited; μ / β under Doc 572 Appendix D with ordinal-axis sub-form.
  • 17 Means Objectives — π / α as cited; μ / β under Doc 572 Appendix D at the means-aspect rung.
  • 40+ Techniques — π / α as cited; μ / β as third nested lattice.
  • LDSE six-discipline composition — π / α as cited; μ / β under Doc 572 Appendix D at the loss-discipline rung.
  • "Capability under adversity emerges from coherent composition" reading — μ / β under Doc 541 SIPE engineered-system-scale.
  • Resilience requirements pattern — π / α as cited; μ / β under Doc 445 forward-pulverization.

V. Residuals

Cluster G engineered-system-scale gap closed. Prior Cluster G instances were institutional/maturity-scale (school maturity, capability, CMMI). System Resilience supplies the canonical engineered-system-scale SIPE instance. Cluster G is no longer "no movement" (SE-039 §VII.5 status); resilience is the worked example that opens the cluster's engineered-system-scale population.

Adaptability folded into resilience. SEBoK's separate System Adaptability glossary entry composes with resilience's "adapt" Means Objective. Adaptability is not a separate discipline at the cluster level; it is a Layer-2 means-objective component of resilience. The keeper's prompt title "Engineered Resilience and Adaptability" is correct as a thematic pairing — the formalization is unified inside System Resilience.

VI. Provisional Refinements

Cluster G synthesis ripe. With resilience supplying the engineered-system-scale instance, Cluster G now spans institutional (ESE), practitioner (capability), maturity (CMMI), and engineered-system (resilience) scales. A Cluster G synthesis successor (analogous to Doc 604's Cluster B synthesis) is now structurally warranted; resilience supplies the canonical engineered-system-scale anchor article.

Universal-sibling-with-ordinal-axis sub-form confirmed. Two independent SEBoK instances (SoS four-type central-authority partial order, resilience three Fundamental Objectives temporal-precedence). The Cluster A synthesis (SE-039 §VII.5 candidate Universal-Sibling Lattice Composition) should formalize the sub-form with these two as canonical worked examples.

Three-nested-lattice as Cluster A density signal. Resilience exhibits three nested Cluster A lattices (Fundamental / Means / Techniques) plus a fourth at the LDSE rung. This is the densest Cluster A density per page observed. The Cluster A synthesis should treat nested-lattice depth as an indicator of cluster-density at the article level.

VII. Cross-Links

Form documents. Doc 572 Appendix D (universal-sibling, three nested + ordinal-axis sub-form confirmed), Doc 541 (SIPE, engineered-system-scale anchor), Doc 445 (pulverization, requirements pattern), Doc 372 (hypostatic boundary), Doc 572 Appendix C (temporal concurrency).

Part-level reformulation. SE-009 (Part 6 Related Disciplines).

Related distillations. SE-071 (SoS, ordinal-axis sub-form precedent). SE-027 (ESE, Cluster G institutional). SE-033 (capability, Cluster G practitioner). SE-034 (CMMI, Cluster G maturity). SE-112 (System Security, LDSE composition partner).

Adjacent SEBoK concepts (per source). System Adaptability, System Reliability, Availability, and Maintainability, System Safety, System Security, Resilience Engineering: Concepts and Precepts.

Methodology refinement candidates. Cluster G synthesis with resilience as engineered-system-scale anchor. Universal-sibling-with-ordinal-axis sub-form formalization in Cluster A synthesis.

Appendix: Originating Prompt

"Apply refinements; report back for next 40" / "Continue"

(SE-116 is one of the third-batch SEBoK distillations. Batch 5/5. Source is System Resilience. Stress-test of Cluster G passes: resilience is the canonical engineered-system-scale SIPE worked example and closes the engineered-system-scale gap in the cluster.)

Referenced Documents

More in framework