c-ECO INSTITUTESYSTEMIC INTELLIGENCE LIBRARY · DSSS

c-ECO SYSTEM / DOMAIN LIBRARY

DSSS · Domain knowledge

Defense & Strategic Security Systems

Risks · Response · Governance · Calibration
Scenarios · Recovery · Sources

c-ECO Institute crest

A domain library connecting systemic risks, monitoring, governance and recovery. Explore nine parts and 35 sections with mechanisms, observations, evidence matrices and documented cases.

English research and learning edition · Scientific references, domain cases and reproducible exercises. Methodological notes →

READING AND EVIDENCE

How to use this library

The library combines domain research, a c-ECO analytical teaching structure and original exercises. References identify mechanisms, methods and documented cases; inclusion does not validate a complete TFP application.

N1 · Analytical and simulated material
The risk–TFP associations, candidate observations, scenario designs and exercise parameters organize inquiry. They are not measured local results, approved operational thresholds or estimates of event frequency. The case must define its function, observations and criteria.
N2 · Reproducible laboratory
Section 20 specifies a synthetic model, assumptions, dependence and random seed. Its Q output is a pedagogical index, separate from SPS. Numerical summaries describe only that declared experiment.
N3 · Sources and scope
Research papers, official documents and case records have distinct roles. This is a curated teaching library, not an exhaustive systematic review. Dynamic sources require a cited version or extraction date; applicability of a legal or technical instrument depends on the actual jurisdiction and activity.
N4 · Governance and learning
The library establishes no statutory power, quorum, emergency command, provider certification, partnership or institutional endorsement. A learning case may be real or simulated. Completion, optional credentialing, permission to submit and licensing remain distinct. Projects and data contributions to the SIL require an associated fellow and applicable review.

PART I

Domain intelligence profile

SECTION 01

Domain overview and system boundary

Strategic resilience should be framed around civilian functions whose loss would seriously constrain public wellbeing or recovery. Define minimum service, the population depending on it and the relevant time horizon. An asset is important because of what it enables, not simply because it is large or expensive. The case boundary should include essential supporting services and legitimate public responsibilities. This framing allows comparison of preparedness choices without disclosing sensitive live-system details or drifting into operational security tactics. [D10] Choose one essential function and explain the consequences of its interruption for different population groups.

This library addresses the civilian, public-interest governance of strategic dependencies and essential-service resilience. It examines continuity of water, energy, health, communications, logistics and legitimate public decision-making under severe disruption. The relevant unit is a function and its dependent population, not a list of protected assets. Analysis remains at the level of resilience, preparedness, lawful coordination and recovery; it does not provide weapons, targeting, offensive operations or tactical instructions. [D01] [D21]

Strategic importance arises when a function has few practical substitutes, supports many other services or is needed before recovery can begin. A disruption may be natural, accidental, technological or deliberate; the protection of civilians and continuity of essential services remain the common analytical concern. Hazard likelihood, service consequence and recoverability should be distinguished. An improbable disturbance can justify attention when its consequences are severe and its recovery constraints are difficult to reverse. [D04] [D07]

The educational case should define a public-service objective, affected groups, plausible initiating disturbances, lawful responsibilities and a bounded information policy. Public learning should focus on aggregate service consequences and governance choices. Sensitive details about live systems require appropriate custodianship and are unnecessary for demonstrating the central methods. Comparative case evidence supports analysis of common-cause exposure, dependencies, warning interpretation and recovery sequencing without implying that different crises have identical causes. [D03] [D12]

A domain label is not yet a case boundary. Separate the condition of a resource or asset from the function delivered to users. A nominally available installation may fail to deliver usable service, and a system-wide average can conceal localized loss. Preserve the original physical or institutional unit alongside any normalized representation. The boundary should make it possible to ask what enters, what changes, what leaves and who experiences the consequences.

Case-analysis method
Case fieldRecord
FunctionDescribe the outcome delivered, affected users and the minimum useful unit of service.
BoundaryRecord spatial, technical, organizational and temporal boundaries, including excluded processes.
Reference conditionState what counts as functional performance and which evidence defines that condition.
Exposure and distributionIdentify which groups, assets and ecological functions can be affected differently.
DependenciesIdentify prerequisites, substitutes and common points of failure.
ObservationConnect each important claim to a source, method, scale and update interval.

Section readings [D10]

SECTION 02

Historical development and changing conditions

The resilience literature distinguishes reliability under expected conditions from the ability to maintain, adapt and recover function under disruption. These concepts developed partly because severe events exposed the limits of isolated asset protection. More redundancy does not always mean more independence, and faster recovery does not establish that the recovered state is safe or equitable. Historical analysis should identify the functional objective, conditions exceeded and adaptations observed. This creates a disciplined basis for comparing cases rather than treating resilience as an all-purpose favorable label. [D05] Compare robustness and recovery in one service and explain why each needs different evidence.

A historical baseline must be examined for changes in exposure, technology, operating practice and observation. Compare episodes using their mechanisms and evidence, rather than treating all events with a similar label as exchangeable observations. A reconstruction should show what was known at each time; later explanations should not be presented as information available to the original decision maker. Recovery and long-term change may require a separate timeline from the initiating incident.

Historical comparison: documented records for further study
Case and periodMechanism to examineComparison questionSource
North American blackout, 2003Loss of situational awareness and power-system failures contributed to cascading disruptionCompare system-wide consequences with isolated component reliability[D18]
Hurricane Katrina, 2005Severe hazard exposure interacted with capability and coordination gapsTest shared response assumptions across jurisdictions[D16]
Fukushima Daiichi accident, 2011Compound external hazards challenged assumptions and essential supporting functionsAssess common-cause exposure and recovery constraints without equating different technologies[D17]
WannaCry and the NHS, 2017Digital disruption affected access to civilian healthcare servicesEvaluate essential service continuity and implementation of known preparedness measures[D19]

Section readings [D05]

SECTION 03

Actors, institutions and decision responsibilities

The institutional map should distinguish operators, regulators, public authorities, service users and independent technical reviewers. Their responsibilities may overlap, but their powers and evidentiary duties differ. Coordination requires specific interfaces for warning, shared assessment, resource requests and restoration verification. No analytical framework substitutes for lawful authorization. Record who can make a decision, who can implement it and who can challenge or review it. Include affected communities because continuity priorities can distribute disruption and recovery very unevenly. [D06] Identify one decision requiring several organizations and show where final lawful responsibility lies.

Map actors by the function they perform and the responsibility they actually hold in the case. The same organization may observe a condition, supply a service and participate in a decision; those roles should remain distinguishable. Examine information access, resources, expertise, affected users and accountability together. A list of institution names is not an operating governance arrangement. Record the evidence for each responsibility and the process for resolving a disagreement or correcting a record.

Case-analysis method
FunctionActors to identifyReviewable output
ObserveOperators, observation networks, laboratories and affected usersTimestamped records and methods.
InterpretAnalysts and relevant subject specialistsMechanism hypotheses, alternatives and uncertainty.
ReviewQualified reviewers with declared interestsDocumented assessment and unresolved disagreements.
Decide and executeThe actor with the applicable mandateReasons, authorized action and verifiable completion.
CommunicateResponsible institutions and accessible public channelsMessage, receipt, corrections and feedback.
UpdateData custodians and the review functionVersion, new evidence and conditions for revision.

Section readings [D06; C07]

PART II

Systemic risk intelligence

SECTION 04

Primary systemic risks

Primary risks threaten the ability to maintain an essential civilian function. A single-source input, unusable backup or absent specialist can become consequential when ordinary alternatives fail. Assess each mechanism against minimum service and the time available for correction. The inventory should distinguish initiating disturbances from weaknesses in preparedness and recovery. Describing every threat as catastrophic obscures prioritization; identify the pathway, exposed population and practical margin. A risk becomes actionable when evidence can inform a defined responsibility or intervention. [D01] Distinguish a severe hazard from the dependency that converts it into prolonged service loss.

The inventory is a structured set of research hypotheses. It separates a threatening condition from the mechanism of loss and from its consequences. The proposed TFP association indicates which question to investigate; it is not evidence that a particular indicator predicts the event. Risk importance depends on the defined function, exposure, duration and usable alternatives. Do not infer frequency, severity or priority from the position of a row in the table.

Thirty domain-specific risk hypotheses
#Risk or threatening conditionMechanism to examineProposed TFP inquiry
1Common-cause service lossOne disturbance affects nominally redundant capabilitiesP: simultaneous margin loss
2Single-source dependencyNo practical alternative supplies an essential inputLr: substitution constraint
3Geographic concentrationCritical capacity shares exposure in one regionP; σ: correlated consequence
4Supply-chain opacityHidden upstream suppliers concentrate riskσ: unrecognized dependency
5Surge mismatchDemand rises while usable capacity fallsΔV: shrinking service margin
6Staff unavailabilityEssential skills are absent during disruptionLr: recovery bottleneck
7Communication fragmentationAgencies cannot form a shared service pictureΔV: coordination delay
8Information integrity lossDecisions rely on incorrect or stale operational evidenceσ: decision error
9Warning non-acknowledgementCredible alerts fail to reach authorized actionΔV: lost lead time
10Power continuity failureSupporting electricity cannot sustain minimum functionsP; Lr: enabling-service loss
11Fuel logistics interruptionTransport and backup supply become unavailableLr: constrained continuity
12Water continuity failureSafe water and sanitation loss undermines response capacityP: civilian consequence
13Healthcare overloadService demand exceeds available staffed capacityP; ΔV: escalating harm
14Digital continuity failureShared platforms interrupt several essential servicesP; Lr: common dependency
15Records integrity failureAuthoritative service and identity records cannot be trustedσ; Lr: restoration barrier
16Procurement inflexibilityReplacement capability cannot be obtained lawfully in timeLr: deployment delay
17Interoperability failureSupport resources cannot work with receiving systemsLr: unusable assistance
18Maintenance debtLatent degradation reduces performance under stressΔV: declining readiness
19Unsafe restartService resumes before integrity and dependencies are verifiedP: renewed disruption
20Recovery resource competitionParallel sectors claim the same scarce personnel or suppliesLr: sequencing conflict
21Public guidance inconsistencyConflicting messages reduce feasible protective actionσ; ΔV: confusion
22Access inequalityContinuity measures protect some groups while excluding othersP: distributional failure
23Rights erosionEmergency measures exceed lawful necessity or reviewP: irreversible civic harm
24Privacy exposureCrisis data sharing reveals protected personal informationP: disclosure harm
25Misinformation amplificationUnverified claims distort essential-service decisionsΔV: correction burden
26Exercise unrealityPlans assume resources unavailable in the modeled crisisσ: false readiness
27Unclosed preparedness findingsKnown weaknesses remain unresolved between eventsLr: recurring exposure
28Climate nonstationarityHistorical operating assumptions fail under changing extremesσ; ΔV: outdated margins
29Mutual-aid correlationAssisting regions experience the same disruptionLr: unavailable support
30Knowledge lossCritical procedures depend on undocumented expertiseLr: delayed reconstruction

Section readings [D01]

SECTION 05

Amplification mechanisms and secondary risks

Amplifiers increase the consequence or duration of an initiating disturbance. Shared geography can affect both primary and backup capacity; fatigue can reduce the workforce needed for recovery; inconsistent guidance can increase avoidable demand. These interactions are conditional and should be supported by a plausible sequence. Avoid assuming that the simultaneous failure of two services proves a causal dependency between them. Common exposure and direct propagation require different remedies and different evidence. [D03] Trace one amplification loop and identify a feasible civilian measure that interrupts it without shifting harm elsewhere.

An amplifier changes the consequences of an initiating condition without necessarily causing the initiating event. Useful counterfactuals hold the threat constant and vary concentration, maintenance, access, information or response capacity. Document the mechanism and the observation that would distinguish it from an alternative explanation. Several amplifiers may share the same upstream cause; counting each one as independent evidence exaggerates confidence.

Amplification mechanisms
AmplifierPropagation mechanismEvidence or TFP inquiry
Regional hazard correlationSeveral services and support providers fail togetherTest alternatives outside the shared exposure
Shared digital platformsA common service dependency defeats organizational separationMap common providers and recovery interfaces
Staff fatigueSustained disruption reduces remaining capacityUse realistic staffing and rest constraints
Demand feedbackService loss creates additional emergency demandTrack service and demand together
Unclear authorityCoordination delays while responsibility is disputedPredefine lawful interfaces and escalation
Unequal accessThe same outage creates different consequences across groupsMeasure distribution and accessible alternatives
Opaque supply tiersApparent supplier diversity hides common sourcesAssess traceable upstream concentration
Premature recovery declarationsPartial functionality is reported as complete restorationVerify minimum service and integrity independently

Section readings [D03]

SECTION 06

Emerging risks and research horizons

Emerging strategic dependencies often result from beneficial transitions. Electrification, cloud services and automated situational awareness can improve ordinary performance while concentrating dependence on shared systems. Evaluate changes in usable alternatives, common-cause exposure and oversight rather than treating novelty as inherently dangerous. Update the dependency inventory when a service changes its operating model. A new capability should be assessed against the public function it supports and the evidence needed to verify continuity under stress. [D13] Identify an efficiency improvement that also changes the system's failure and recovery relationships.

A research horizon is tied to the time needed to investigate, prepare or change a system. It is not a date at which an emerging threat is predicted to occur. Record the reason for concern, the strength of evidence, the exposed function and the observation that would change the priority. Distinguish a newly observed mechanism from a known mechanism whose exposure, scale or institutional context is changing.

Emerging research agenda
Research topicMechanism or knowledge gapObservation or horizon question
Climate-compound disruptionMultiple environmental stresses overlap with service dependenciesCompare joint exposure and recovery constraints
Cloud concentrationMany public functions inherit a common digital dependencyAssess service continuity and accessible alternatives
AI-mediated situational awarenessAutomated interpretation can amplify unsupported conclusionsPreserve source evidence and accountable review
Electrification couplingMore services depend on the same electricity systemReassess minimum-service dependencies
Cross-border supply restrictionsStrategic inputs face changing lawful access conditionsEvaluate substitutability and civilian consequences
Information-environment disruptionSynthetic content can confuse public-service guidanceUse authenticated accessible communication and timely correction

Section readings [D13]

SECTION 07

Cascades and cross-domain dependencies

Cascade analysis follows a disruption through directional functional links. Electricity loss may interrupt communications, which can delay coordination and extend other service outages. The pathway needs timing, an enabling mechanism and evidence that the dependent function lacks a suitable alternative. Abstract network models can reveal possible systemic behavior but do not supply empirical probabilities for a particular city or service network. Preserve the difference between a conceptual cascade and a verified historical sequence. [D02] Construct a short service-loss pathway and identify the observation needed to verify each link.

Interdependence transmits service loss through physical supply, information exchange, shared geography or decision rules. These pathways require different evidence. A common storm can affect several facilities simultaneously without a causal link between them, while loss of electricity can directly disable another service. Keep those mechanisms distinct. [D01]

Criticality depends on function, time and affected population. The same asset can be substitutable during ordinary demand and indispensable during an emergency. Assess minimum service, available alternatives and the period over which substitution remains feasible. Asset counts alone do not establish strategic importance. [D10]

Common-cause disturbances can defeat nominal redundancy. Two suppliers may share a region, transport route, technology platform or parent company. Evaluate independence at the level of plausible failure mechanisms rather than assuming that different names or facilities provide separate protection. [D02]

For each directed dependency, specify the function supplied, the destination, the propagation time and the substitute. Shared-cause failure, interacting threats and cascading propagation are different structures. A directed arrow becomes an explanatory claim only when the timing and mechanism are supported. Test apparent redundancy by removing the common access route, platform, energy supply or specialist on which both alternatives depend.

Directed dependency hypotheses
DependencyMechanism and directionVerification or TFP inquiry
EnergyElectricity and fuel enable most continuity resourcesVerify actual minimum-load support and replenishment
Water and sanitationSafe water sustains healthcare, shelter and ordinary lifeProtect both quality and distribution access
HealthMedical capacity supports affected populations and essential workersMap staffed capacity and continuity needs
Food systemsDistribution depends on energy, transport and usable payment channelsAssess minimum supply and access
LogisticsTransport enables staff, supplies and recovery workIdentify scenario-appropriate alternative routes at aggregate level
Digital systemsCommunication and records support coordinationTest independent continuity and trustworthy restoration
GovernanceLawful authority and accountability shape emergency decisionsPreserve review, proportionality and clear roles
Scientific observationReliable evidence informs warnings and recovery verificationMaintain independent checks and uncertainty records
IndustrySpecialist components and maintenance support restorationAssess replacement lead times and compatibility
Urban systemsPopulation density and built environments shape consequenceMeasure vulnerable groups and accessible services

Section readings [D02; C01; C02]

PART III

Systemic response intelligence

SECTION 08

Readiness and response protocols

Continuity protocols should define the minimum civilian function, evidence thresholds, responsible roles and review conditions. A prewritten plan is not demonstrated capability until its assumptions have been tested. Include degraded operation, accessible public communication and conditions for pausing an unsafe restart. Protocols should remain usable when ordinary staffing or communication is impaired. Public-facing material can explain these principles and aggregate outcomes without exposing sensitive configurations or details of live-system vulnerabilities. [D07] Test whether the protocol can still deliver its minimum function when one assumed supporting resource is absent.

Preparedness connects a signal to a responsible actor, an available measure and a condition of completion. This learning architecture does not grant emergency command or operational authority to the c-ECO Institute or a course participant. A useful protocol distinguishes checking the signal, protecting exposed functions and verifying recovery. A paper plan contributes to usable capacity only when its relevant assumptions have been tested.

Case-analysis method
StageAction to prepareEvidence
PrepareDefine critical functions, contacts, alternatives and observation coverage.A tested readiness record.
VerifyCheck the signal, the instrument and plausible alternative explanations.A traceable observation and uncertainty statement.
ProtectSelect and implement measures within the responsible actor’s authority.Coverage of priority functions and evidence of execution.
RecoverVerify usable performance before treating the function as restored.Recorded return criteria, monitoring and decision owner.

Section readings [D07]

SECTION 09

Scientific review and decision records

Escalation should occur when consequences or recovery needs exceed the authority or capability available at the current level. Specify the information transferred, the lawful receiving role and the continuing responsibilities of the originating operator. Technical review should challenge assumptions and verify restoration claims without silently acquiring operational command. Record material disagreements and interim safeguards. The process must be proportionate to the public consequences and preserve civilian rights, especially when emergency measures restrict ordinary access or movement. [D21] Identify the evidence that justifies escalation and the condition under which responsibility returns to ordinary arrangements.

A review record separates observation, inference and decision. Record the data version, methods, alternative explanations, relevant expertise, conflicts of interest and unresolved disagreement. Review should be matched to the question and its consequences. Scientific analysis can inform a competent actor without replacing that actor’s mandate. No membership size, quorum or institutional power is established by this teaching library.

Case-analysis method
Review itemQuestion and record
QuestionWhat specific claim is being evaluated?
EvidenceWhich observations, sources and transformations support it?
AlternativesWhat other process could explain the same observation?
IndependenceWhich interests or shared data origins affect review?
DecisionWho can act, on what basis and with which constraints?
RevisionWhat new observation or failure of an assumption reopens the analysis?

Section readings [D21; C05; C07]

SECTION 10

Communication and observation continuity

Communication supports protective action only when people can receive, understand and use the guidance. Shared operational information and public messages have different purposes and access requirements. Keep time, geographic scope, uncertainty and required action clear. Contradictory versions should be corrected visibly. Include channels that remain accessible during digital or electricity disruption, and test their reach with affected communities. Message volume is a poor proxy for effective communication when people lack feasible means to comply. [D06] Evaluate a continuity message from the perspective of someone without reliable internet access or private transport.

Continuity of observation should be tested alongside continuity of the function itself. Losing data may increase uncertainty before the physical process visibly changes. Redundancy must be demonstrated against common causes, including power, location, communications, credentials and specialist availability. During disconnected operation, preserve the last reliable observation, record the uncertainty that follows and reconcile timestamps and authorship when information paths return.

Case-analysis method
Continuity capabilityTest
Observation pathTest sensor availability, power, timing and independent confirmation.
Alternative communicationTest actual reach, autonomy and the ability to contact responsible people.
Degraded operationSpecify what can remain usable safely under loss of information or connectivity.
Offline recordKeep controlled copies of essential maps, contacts, definitions and procedures.
Accessible messagesCheck language, disability access, delivery and routes for correction.
ReconciliationPreserve timestamps and authorship when disconnected records are merged.

Section readings [D06; C01]

PART IV

Governance and legal architecture

SECTION 11

International instruments and technical references

International frameworks can guide civilian preparedness and cooperation without granting powers to an educational project. The Sendai Framework emphasizes understanding risk, strengthening governance, investing in resilience and improving preparedness and recovery. Its use should be linked to the case's actual institutional arrangements and applicable law. Cross-border essential-service dependencies require attention to information sharing, mutual assistance and public consequences. Distinguish binding commitments from policy guidance and voluntary technical practice before deriving operational implications. [D21] Map one relevant international instrument to a concrete civilian responsibility while preserving its legal status.

Classify each instrument before using it. A scholarly article supports an inference, a technical guide describes a method, a standard has a defined scope, and a legal instrument may create obligations only where applicable. The case record should identify the specific provision or method, its version and the activity to which it relates. A source’s institutional reputation cannot by itself establish applicability or demonstrate compliance.

Technical and institutional documents: identify their actual function
ReferenceDocumentUse and scope
[D13]Cybersecurity Supply Chain Risk Management Practices for Systems and OrganizationsGovernance of supplier and technology dependencies; current updated edition.
[D14]The NIST Cybersecurity Framework (CSF) 2.0Govern, identify, protect, detect, respond and recover as organizational outcomes.
[D15]The February 2021 Cold Weather Outages in Texas and the South Central United StatesGas-electric dependency and common-cause cold-weather exposure.
[D16]Catastrophic Disasters: Enhanced Leadership, Capabilities, and Accountability Controls Will Improve the Effectiveness of the Nation's Preparedness, Response, and Recovery SystemKatrina lessons on coordination, capability and accountability.
[D17]The Fukushima Daiichi AccidentCompound external hazards, organizational assumptions and recovery challenges.
[D18]Final Report on the August 14, 2003 Blackout in the United States and Canada: Causes and RecommendationsSituational awareness and cascading power-system disruption.
[D19]Investigation: WannaCry cyber attack and the NHSDigital disruption and continuity of civilian healthcare.

Section readings [D21]

SECTION 12

Jurisdiction-specific responsibilities and requirements

Domestic arrangements define responsibilities for essential services, emergency coordination, public information and protection of rights. These vary by jurisdiction and sector. An asset operator's duty, a regulator's oversight role and an emergency authority's powers should not be conflated. The case should identify current authoritative sources and seek qualified interpretation where necessary. Scientific analysis can compare consequence and recovery options, but the selected action must remain within lawful responsibility and review procedures. [D16] Compare who owns the infrastructure, who operates the service and who can authorize an extraordinary measure.

The register should cover the actual activity and location, including interfaces between organizations and jurisdictions. Separate responsibility for observing, supervising, deciding and executing. Retain the official source, version consulted and evidence needed to assess a condition. Conflicting definitions and overlapping mandates are analytical findings to investigate. A general library cannot create a universal legal threshold for all settings.

Case-analysis method
Register fieldInformation to preserve
Instrument and versionOfficial title, scope, jurisdiction and date consulted.
Actor and functionThe competent authority, operator, owner or custodian for the relevant activity.
ConditionThe requirement, decision trigger or performance obligation actually applicable.
EvidenceThe observation or document needed to evaluate that condition.
InterfaceOverlaps, conflicts, shared duties and coordination procedures.
ReviewHow changes in the instrument, activity or evidence affect applicability.

Section readings [D16]

SECTION 13

Causation, accountability and cascading consequences

Accountability continues during severe disruption. Urgency may justify defined temporary arrangements, but their purpose, legal basis, duration and review should remain clear. Distinguish the immediate restoration decision from later investigation, remedy and institutional learning. Records should support reconstruction without exposing unnecessary sensitive information. A successful continuity claim requires evidence of service delivery and residual limitations, not only a declaration by the responsible institution. Affected people need accessible routes to report unmet needs and challenge errors. [D19] Identify one emergency decision whose consequences should be independently reviewed after minimum service is restored.

A technical chain of consequences is not automatically a legal allocation of liability. Separate evidence of causation from the duties, control and decisions relevant to each actor. A case may contain direct damage, dependent service interruption and persistent environmental or social consequences on different timescales. The analysis should show which links are documented and which need further investigation, without presuming an institutional restoration fund, mandatory levy or insurance mechanism.

Case-analysis method
LayerAnalytical question
Technical sequenceSeparate the initiating condition, failure mechanism, propagation and consequence.
Duty and controlIdentify the applicable responsibility and the actor able to influence the relevant process.
ExposureTrace the connection between a change of state and an affected function or population.
Alternative explanationsIdentify concurrent conditions and missing evidence relevant to attribution.
Recovery resourcesIdentify documented resources and their access conditions, without assuming an institutional fund or levy.

Section readings [D19]

SECTION 14

Cross-boundary coordination

Transboundary dependencies can connect service users to suppliers and infrastructure outside their government's direct control. Cooperation may require agreed information, compatible assistance procedures and lawful arrangements for resource transfer. Geographic distance alone does not establish independence when suppliers share technology or upstream production. Evaluate how restrictions, transport interruptions or regional hazards could affect civilian service continuity. Public analysis should describe the dependency at the functional and aggregate level necessary for governance decisions, avoiding sensitive operational detail. [D13] Compare an apparent alternative supplier with the original and determine whether both share a critical upstream source.

Processes and dependencies often cross administrative, organizational or national boundaries. Coordination requires compatible definitions, useful timing, authorized exchange and an identifiable decision interface. Sharing data does not by itself resolve disagreements over objectives, risk allocation or resources. An exercise should expose which decision can be coordinated under existing arrangements and which would require an additional agreement or competent determination.

Coordination across functional boundaries
Boundary / dependencyMechanism to coordinateCase record
EnergyElectricity and fuel enable most continuity resourcesIdentify the actors, notification time, information definition and decision interface for this boundary.
Water and sanitationSafe water sustains healthcare, shelter and ordinary lifeIdentify the actors, notification time, information definition and decision interface for this boundary.
HealthMedical capacity supports affected populations and essential workersIdentify the actors, notification time, information definition and decision interface for this boundary.
Food systemsDistribution depends on energy, transport and usable payment channelsIdentify the actors, notification time, information definition and decision interface for this boundary.
LogisticsTransport enables staff, supplies and recovery workIdentify the actors, notification time, information definition and decision interface for this boundary.
Digital systemsCommunication and records support coordinationIdentify the actors, notification time, information definition and decision interface for this boundary.

Section readings [D13; C07]

PART V

TFP calibration intelligence

SECTION 15

Position (P): candidate observations

P should represent a defined margin to an unacceptable essential-service condition. Examples include usable water supply relative to minimum demand or staffed healthcare capacity relative to urgent need. Retain the units, affected population and service-quality requirement. Nominal capacity can overstate the margin when supporting electricity, personnel or access is absent. The chosen threshold should be identified as a service obligation, technical criterion or explicit scenario assumption. It is not established by the framework's terminology alone. [D10] Compare installed capacity with usable capacity under the stated disturbance and explain the practical difference.

P represents position relative to a specified loss of function. The raw observation, reference condition, direction of deterioration and boundary of failure must remain explicit. A candidate monotone transformation can help compare states within a defined case, but it does not establish the threshold or validate an aggregate index. Capacity, delivered performance and exposure may require different indicators even when they concern the same installation.

Thirty candidate observations for P and related case questions
#Candidate observationUnit or definitionInterpretation and data requirement
1Minimum essential-service coverage% defined population servedSpecify function, population and service-quality requirement
2Usable capacity marginservice-specific units or %Count capabilities available under the scenario
3Alternative supply coverage% minimum requirementVerify independence and switching feasibility
4Supplier concentration% essential inputs by sourceInclude shared upstream dependencies
5Dependency documentation coverage% critical interfaces mappedRequire mechanism, owner and last review
6Common-cause exposure% capacity sharing defined exposureUse scenario-specific geography and technology
7Staffed surge capacityservice-specific unitsDistinguish physical space from trained available staff
8Critical-role substitute coverage% roles with verified substituteExercise handover and availability
9Warning acknowledgement timeminutes or hoursRecord issue, receipt and authorized acknowledgement
10Shared situation-report latencyminutes or hoursMeasure age of relevant observations
11Data integrity check coverage% critical recordsState check type and residual limitations
12Backup continuity durationhours at specified loadUse tested demand and replenishment assumptions
13Fuel replenishment lead timehours or daysAssess access and supplier availability under disruption
14Water continuity durationhours at minimum safe demandMaintain quality as well as volume requirements
15Healthcare service interruptionhours by service typeIdentify essential procedures and affected groups
16Digital service recovery timehoursVerify end-to-end service and record integrity
17Authoritative record recovery pointtime since last recoverable valid stateDistinguish restored files from reliable records
18Alternative-channel accessibility% affected population able to useAssess disability, language and digital exclusion
19Mutual-assistance activation timehoursMeasure request through useful deployment
20Restoration resource availability% scenario requirementAvoid double counting shared teams and equipment
21Interoperability exercise success% defined tasks completedTest realistic receiving conditions
22Overdue maintenancecount and age by critical functionLink to failure mechanisms and condition evidence
23Corrective actions verified closed% actions dueRequire evidence beyond administrative closure
24Exercises covering compound disruptioncount and scopeDocument simultaneous constraints and learning
25Service restoration inequalityhours by population groupProtect privacy and explain grouping
26Public guidance consistency% sampled messages alignedCheck substance, date and accessible version
27Emergency-measure review timelinessdaysApply the relevant lawful review and expiry rules
28Sensitive-data minimization coverage% relevant exchanges assessedIdentify purpose, access and retention
29Observed restoration performanceservice level over timeRetain partial and repeated loss of service
30Recovery assumption review agemonthsRefresh after material changes or failed exercises

A didactic monotone transformation for an indicator that worsens as it rises is p = clip[(x − x_ref)/(x_failure − x_ref), 0, 1]. Reverse the direction for a reserve that deteriorates as it falls. The expression makes the reference points visible; it does not choose those points, prove comparability or establish an operational aggregate. Retain x in its original unit and justify the function separately for each case.

Section readings [D10]

SECTION 16

Velocity (ΔV): rates and trajectory

ΔV concerns how quickly the service margin is changing. Supply can decline while emergency demand accelerates, creating deterioration faster than either trend suggests alone. Estimate change over a window suited to the process and preserve noise and uncertainty. A restoration curve can include setbacks and unequal progress across groups, so a single average recovery rate may mislead. Connect velocity to a realistic action and mobilization time rather than treating a steep trend as self-explanatory evidence of imminent collapse. [D11] Compare the estimated time to minimum-service loss with the earliest feasible protective response.

ΔV describes direction and rate of change over a declared interval. Two systems at the same apparent position may have different reaction times because their trajectories differ. Compare rates using consistent units, observation windows and reference systems. Check seasonality, missing periods, reporting changes and process acceleration before extrapolating. A time-to-boundary calculation is conditional on its trajectory assumption; it is not a general forecast.

Ten families of rate-of-change observations
ProcessRate / unitInterpretation
Essential-service margin depletionservice units/hourTrack demand and usable capacity jointly
Supplier concentration changepercentage points/yearInspect common upstream ownership and logistics
Maintenance backlog growthtasks/monthStratify by functional consequence
Staff availability declinequalified staff/dayInclude fatigue, exposure and replacement constraints
Warning lead-time contractionhours/hourCompare disturbance development and action latency
Shared information stalenessminutes/hourSeparate acquisition and interagency delivery
Demand surge accelerationrequests/hour squaredUse stable service definitions and plausible noise treatment
Recovery progresspercentage points of service/dayRetain setbacks and unequal recovery
Corrective-action delay growthdays/quarterFollow comparable cohorts and verified closure
Alternative capability readiness changepercentage points/monthUse demonstrated tests rather than planned purchases

Section readings [D11]

SECTION 17

Uncertainty (σ): evidence and model limits

Uncertainty in strategic resilience includes incomplete dependency maps, limited disturbance data and uncertain human adaptation. These cannot all be represented by independent component-failure probabilities. Shared exposure and policy responses can dominate outcomes. Use scenario alternatives and sensitivity analysis to identify assumptions that change the decision. Acknowledge where empirical evidence is insufficient for a numerical likelihood. Decision quality depends on a transparent account of consequence, capability and uncertainty, not simply on the precision of a modeled risk score. [D09] Identify the uncertain assumption that most changes the priority among two continuity investments.

Uncertainty should be recorded by object and source. Measurement uncertainty, sampling limitations, parameter uncertainty, model structure, future scenarios and institutional ambiguity cannot be replaced by one unsupported percentage. More simulation samples can reduce numerical sampling error without resolving a missing mechanism. Identify which uncertainty changes the decision and which further observation, comparison or test could reduce it.

Case-analysis method
Source of uncertaintyObject affectedTreatment
MeasurementInstrument error, drift, reference system and quality controls.Calibration, cross-check and traceable metadata.
SamplingSpatial, temporal or population coverage.A design matched to the decision and exposed groups.
ParametersValues weakly identified by available observations.Estimation, sensitivity and alternatives.
Model structureProcesses excluded or represented inadequately.Competing models and tests outside the fitting conditions.
ScenarioUncertain future demand, environment or operating practice.A declared set of plausible trajectories.
DependenceCorrelated conditions or failures treated as independent.Joint analysis and explicit common-cause hypotheses.
InstitutionsUnverified duties, access or resource availability.Documentary checks and mobilization tests.
Unknown mechanismsA plausible process with insufficient evidence.A research question and decisions robust to the unresolved gap.

Section readings [D09; C06]

SECTION 18

Reversibility liquidity (Lr): usable recovery resources

Lr describes the constraints on recovering a minimum function after disruption. Specialist staff, compatible components, safe access, lawful authority and trustworthy records may all be necessary. Recovery is limited by the slowest required dependency, and several sectors may compete for the same resource. Different population groups can face different restoration times even when an aggregate service indicator improves. Report the sequence, usable alternatives and residual exclusions. Reopening an asset does not by itself demonstrate restoration of the civilian function. [D04] Identify one recovery resource whose absence would delay every other planned restoration activity.

Lr examines resources that can preserve, contain or recover the defined function within the relevant time. A resource listed in an inventory is different from a resource that is accessible, compatible, staffed and mobilizable. Record capacity, useful arrival time, duration, dependencies and evidence of testing. Avoid averaging away an essential bottleneck. Recovery of a service does not necessarily restore ecological condition, accumulated losses or public trust.

Recovery resources to verify in the case
Recovery resourceAvailability or mobilization questionVerification or dependency
Trained continuity personnelDemonstrated competence and realistic availabilityExercise the minimum-service function
Independent communication optionsAccessible alternatives with different failure modesTest message receipt and comprehension
Verified backupsRecoverable records and operational configurationsValidate integrity and end-to-end restoration
Alternative suppliersQualified substitutes with feasible lead timesCheck common upstream dependencies
Mutual-assistance agreementsDefined request, responsibility and handback arrangementsTest deployment during correlated regional stress
Essential-service inventoriesScenario-relevant supplies with lawful custodianshipVerify condition and replenishment
Specialist maintenance supportCompetence, access and compatible componentsTest realistic mobilization time
Accessible community channelsTrusted routes for needs reporting and guidanceVerify reach among underserved groups
Independent recovery verificationEvidence of safe minimum service and residual limitationsRecheck after restart and subsequent stress
Corrective-action capabilityOwners, deadlines and evidence of durable changeDemonstrate the original failure mechanism has been addressed

Section readings [D04]

PART VI

Scenario and simulation intelligence

SECTION 19

Stress scenarios and comparative strategies

Scenarios should compare meaningful combinations of disturbance and capability. Begin with a bounded service objective, then vary common-cause exposure, demand surge and the availability of alternatives. Include a scenario in which mutual assistance is constrained because neighboring regions are also affected. The purpose is to test decisions across plausible conditions, not to predict every possible crisis. A useful comparison reveals which assumptions drive performance and which measures preserve minimum function despite uncertainty. [D07] Identify a preparedness choice that remains beneficial across the scenarios and one that depends on favorable assumptions.

A stress scenario states the initiating condition, prior state, time sequence, exposed function, shared dependencies and feasible responses. Its purpose is to reveal when a strategy loses usefulness and why. Compare alternatives across several conditions, including absent substitutes and simultaneous demand. Scenarios should lead to observations, tests and resource questions; assigning a precise event probability requires a separate justified model and evidence.

Five domain-anchored stress-test designs · N1
ScenarioInitiating mechanismObservation designStrategy comparison
A · Common-cause service lossOne disturbance affects nominally redundant capabilitiesCheck which observation distinguishes onset, propagation and loss of the defined function.Compare current practice, improved readiness and a structural alternative; remove one shared prerequisite.
B · Supply-chain opacityHidden upstream suppliers concentrate riskCheck which observation distinguishes onset, propagation and loss of the defined function.Compare current practice, improved readiness and a structural alternative; remove one shared prerequisite.
C · Power continuity failureSupporting electricity cannot sustain minimum functionsCheck which observation distinguishes onset, propagation and loss of the defined function.Compare current practice, improved readiness and a structural alternative; remove one shared prerequisite.
D · Maintenance debtLatent degradation reduces performance under stressCheck which observation distinguishes onset, propagation and loss of the defined function.Compare current practice, improved readiness and a structural alternative; remove one shared prerequisite.
E · Misinformation amplificationUnverified claims distort essential-service decisionsCheck which observation distinguishes onset, propagation and loss of the defined function.Compare current practice, improved readiness and a structural alternative; remove one shared prerequisite.

Section readings [D07]

SECTION 20

Reproducible simulation and sensitivity analysis

Simulation should represent the service process needed for the question. A network model may show dependency structure, while a flow or queue model may better capture capacity and demand. State boundaries, time steps, resource constraints and correlations. Compare outputs against observed behavior or independent technical expectations where possible. Synthetic parameters remain exercise assumptions even when the computational result is reproducible. Numerical complexity should not conceal a missing physical or institutional mechanism essential to the civilian consequence. [D09] Explain why the selected model can answer the stated question and identify one question it cannot answer.

Simulation is an explicit transformation of assumptions. Input distributions, dependencies, parameter estimation, output definition and testing must be documented. Numerical convergence does not establish model validity. Examine sensitivity to the function used, the weights selected, dependence assumptions and conditions outside the fitting data. The reproducible laboratory below is a synthetic exercise, separated from SPS and from any claim about real-event frequency.

Reproducible synthetic laboratory · N2
ElementSpecification
Samples and seed10,000 samples; Python Random; seed 1631332263.
Reference centersP = 0.72; ΔV = 0.62; σ = 0.40; Lr = 0.38.
Latent dispersion0.40, 0.45, 0.30, 0.40, respectively.
Common-factor loading0.65, 0.55, 0.35, −0.45, respectively.
Dependence constructionz_j = a_j g + √(1 − a_j²) ε_j; g and ε_j are independent standard normal draws.
Bounded transformationx_j = logistic[logit(m_j) + s_j z_j].
Learning outputQ = 0.35P + 0.25ΔV + 0.15σ + 0.25(1 − Lr).
Comparison conditionQ ≥ 0.70, selected only for this synthetic laboratory.
Calculated outputs under the declared assumptions
StatisticValue
Mean0.618
5th percentile0.516
Median0.620
95th percentile0.711
Fraction with Q ≥ 0.707.58%

The factor loadings define association on the latent scale. Correlations after the nonlinear transform should be estimated from the simulated samples. Q is a teaching index and is not SPS. Its exceedance fraction concerns the generated sample under these assumptions; it is not the probability of a real event or a forecast over a stated number of years. A temporal forecast would require a separately specified process and observation model.

Reproduce the calculation in Python
from random import Random
from math import log, exp, sqrt
from statistics import mean
rng = Random(1631332263)
m = [.72, .62, .40, .38]
s = [.40, .45, .30, .40]
a = [.65, .55, .35, -.45]
q = []
for _ in range(10000):
    g = rng.gauss(0, 1)
    x = []
    for mj, sj, aj in zip(m, s, a):
        z = aj*g + sqrt(1-aj*aj)*rng.gauss(0, 1)
        x.append(1/(1+exp(-(log(mj/(1-mj))+sj*z))))
    p, v, u, lr = x
    q.append(.35*p+.25*v+.15*u+.25*(1-lr))
q.sort()
print(mean(q), q[499], (q[4999]+q[5000])/2, q[9499])
print(sum(x >= .70 for x in q)/len(q))

Sensitivity exercise: remove the common factor, vary one dispersion, change the weight of recovery resources, and compare the ranking of the selected strategies. Then state which domain observations would be needed to replace each illustrative assumption. Use a suitable estimator when inputs are dependent; the common-factor experiment is a dependence check, not a claim that a particular Sobol estimator applies unchanged.

Section readings [D09; C03; C06]

SECTION 21

Restoration and performance verification

Recovery simulation should retain resource competition, prerequisites and service distribution. Restoring the largest asset first may not restore the most urgent civilian function. Compare strategies against the same minimum-service objective and realistic capability constraints. Track partial service, repeated interruption and the time until affected groups can actually use the service. Independent verification should test safety and integrity before declaring success. The modeled sequence informs review; lawful operators and authorities remain responsible for actual restoration decisions. [D10] Compare two restoration sequences and explain the tradeoff between aggregate speed and access for vulnerable groups.

Restoration follows prerequisites and verification conditions rather than a universal fixed clock. Tasks may proceed in parallel only where they do not compete for the same people, access, equipment or information. Protect essential functions while the critical path is addressed. Define what is measured before returning service, who can make that determination and which effects require continued observation after a technical restart.

Case-analysis method
StageAction and prerequisiteEvidence of usable progress
Protect essential usersProvide a feasible interim function while restoration proceeds.Coverage and actual receipt.
Restore prerequisitesRecover access, inputs, energy, information and competent personnel.Verified availability for the next task.
Restore the processRepair and operate the affected function within its relevant constraints.Technical tests matched to the failure mechanism.
Verify performanceMeasure the delivered outcome and remaining exposure.A predeclared verification record.
Authorize and communicateRecord who can declare the relevant return condition.Clear status, limitations and notification.
Follow upMonitor persistent effects and resolve causal and monitoring gaps.A review record and tracked corrective actions.

Section readings [D10]

PART VII

Restoration and recovery architecture

SECTION 22

Recovery provider capability

Qualification should follow the civilian task and its consequence. Infrastructure expertise, continuity planning, community access and public-law interpretation require complementary knowledge. Ask contributors to demonstrate relevant methods, explain limits and disclose material interests. An organization that supplies a recovery resource may provide useful evidence without being an independent evaluator of its own performance. Preserve a separate route for challenge and verification. Public educational casework should use appropriate aggregate or historical information rather than depend on access to sensitive live configurations. [D12] Identify the expertise needed to verify minimum service and the expertise needed to assess unequal consequences.

Capability assessment must be specific to the task, place and stress conditions. A training certificate cannot demonstrate that a team can mobilize and deliver the required function. Inspect competence, safety, compatibility, relevant experience and actual availability. Define the verification method and limits of recognition. This teaching library does not establish a c-ECO provider certification scheme or substitute for professional or regulatory requirements.

Case-analysis method
CapabilityVerification
Technical capabilityEvidence relevant to the specific task, process and failure mechanism.
MobilizationA demonstrated route, team, equipment and useful arrival time.
CompatibilityProof that resources can work with the installation, data and local constraints.
Safety and responsibilitiesRelevant professional duties, safe work and accountable supervision.
VerificationPerformance tests, records and independent review proportionate to the task.
ContinuitySubstitutes and supplies under simultaneous demand or extended interruption.

Section readings [D12]

SECTION 23

Recovery sequencing and time constraints

Recovery sequencing starts with safe conditions and trustworthy information about the disruption. Stabilize enabling functions, establish accessible minimum services, verify integrity and then expand toward ordinary performance. Some tasks can proceed in parallel, but their shared resource constraints should be explicit. A temporary workaround may create later correction or maintenance needs; include those in the assessment. Durable recovery addresses the assumptions that failed, rather than returning without change to the same exposure and dependency structure. [D05] Distinguish what is necessary for safe restart from what is necessary for long-term restoration and improvement.

A recovery time objective is a decision criterion to test against real capacity. Distinguish mobilization, work, verification and decision time, and identify dependencies between tasks. Shared resources can prevent apparently parallel activities from proceeding together. Repeating the sequence with unavailable access, a specialist or a verification service reveals where a target relies on an untested assumption.

Case-analysis method
Sequencing itemCase requirement
Task and functionDefine the outcome, prerequisites and critical users.
Time componentsSeparate mobilization, execution, verification and decision time.
Shared resourcesIdentify people, equipment, access and systems needed by more than one task.
Parallel workDemonstrate that tasks can proceed together without competing for the same bottleneck.
Completion conditionSpecify the observation that permits the next task or return of the function.
SensitivityRepeat with unavailable resources or longer lead times to expose the critical path.

Section readings [D05]

SECTION 24

Equipment, inputs and replenishment

A continuity inventory should record function, usability, custodian, maintenance condition and deployment time. Counts alone can exaggerate readiness when resources share fuel, staff or access routes. Verify whether assistance is available under the same regional disturbance, and check compatibility before relying on replacement equipment or services. The inventory should be reviewed after exercises and material system changes. Public reporting can summarize readiness and limitations without disclosing sensitive quantities or configurations that are unnecessary for accountability. [D13] Identify two inventory entries that compete for the same underlying resource and correct the apparent capacity.

Inventory analysis connects each item to a protected function. Use condition, compatibility, accessibility and consumption under stress rather than a nominal stock count alone. Replenishment time must include procurement, transport, installation and verification where relevant. A substitute that depends on the same supplier or platform may disappear in the same event. Keep the last inspection date and the evidence supporting usable availability.

Case-analysis method
Inventory fieldVerification
SpecificationIdentity, quantity, condition, compatibility and installation requirements.
AvailabilityLocation, access rights, expiry where relevant and verification date.
Stress consumptionUseful stock under the conditions studied, including losses and surge demand.
ReplenishmentSupplier, lead time, transport constraints and alternatives.
Common dependenceOther stocks or substitutes that share a supplier, access route, platform or energy source.
TestEvidence from inspection, deployment or a representative mobilization exercise.

Section readings [D13]

SECTION 25

Mutual aid and cooperation arrangements

Mutual assistance works through clear requests, compatible capabilities and agreed responsibility. The receiving institution must be able to integrate support while protecting data and preserving lawful authority. Test not only deployment but also handback, record correction and the assisting organization's continuing obligations to its own population. Regional hazards can reduce availability simultaneously across partners. A robust case includes an alternative when expected assistance cannot arrive, with an honest account of the resulting minimum service and remaining needs. [D16] Test a support arrangement under a scenario in which the nearest assisting jurisdiction is affected by the same event.

Cooperation contributes to recovery when its scope, activation, resources and practical availability are demonstrated. Record who requests support, who authorizes it, the useful arrival time, responsibility for the work and conditions of return. Consider simultaneous demand across participants. A reference to an organization or network in the literature does not imply that c-ECO or a case partner has joined it or secured a deployment commitment.

Case-analysis method
Agreement elementQuestion
ActivationWho can request and authorize support, and on what documented basis?
ResourceWhat can actually be supplied, at what capacity and for how long?
DeliveryWhich access, transport, compatibility, information and safety conditions apply?
SimultaneityWhat happens when several participants need the resource at the same time?
ResponsibilityWhich actor controls the task and its records, verification and constraints?
ReviewHow are performance, remaining gaps and revised arrangements recorded?

Section readings [D16]

PART VIII

Research and source library

SECTION 26

Source classification and evidence quality

Classify sources by the evidentiary role they serve. A technical standard defines recommended practice, an operational record documents performance and an investigation reconstructs a particular disruption. A threat statement does not establish the probability of failure, and a successful exercise does not prove all-hazard readiness. Assess timeliness, independence, methods and relevance to the service objective. Preserve the distinction between observed case evidence and the analytical assumptions used to transfer its lessons to another setting. [D03] For one continuity claim, identify the source that supplies observation and the source that supports interpretation.

Source classes organize origin and function; they do not form an automatic hierarchy of evidential strength. An official statistic, an operational record and a causal study answer different questions. Classify the product, not only the organization. Detect shared data origins so that a dashboard, article and secondary report based on one observation are not counted as three independent confirmations.

Case-analysis method
Source classContributionQuality criterion
A · Institutional / officialOfficial statistics, instruments, technical guidance and investigation records.Mandate, method, version, scope and actual applicability.
B · Operational / technicalMeasurements, process records, assets, inventories and delivered performance.Traceability, coverage, quality controls and usable access.
C · Academic / independentResearch designs, mechanism studies, models and independent observations.Methods, inference, reproducibility and fit to the question.

Section readings [D03; C04; C05]

SECTION 27

Institutional, regulatory and technical sources

Government and intergovernmental sources provide public responsibilities, official investigations and technical guidance. Their scope and status differ. NIST guidance addresses organizational outcomes and practices; an incident investigation assesses particular events; Sendai supplies a policy framework. None should be cited as if it validates a case-specific numerical forecast. Record edition, jurisdiction and the relevant finding. Where guidance has been updated, use the appropriate version while preserving the historical version when analyzing an earlier decision. [D14] Check whether the source defines a recommended process, reports a verified outcome or establishes a binding duty.

Institutional sources should be selected by product, method and scale. Record whether the source defines a requirement, observes a condition, reports an investigation or synthesizes a literature. A current portal may contain several editions and methods; cite the actual version used. Public access does not establish accuracy for a different question, and a restricted source can still be used only under its authorized conditions.

Institutional and technical source register
IDProduct / documentWhy it matters
[D13]Cybersecurity Supply Chain Risk Management Practices for Systems and OrganizationsGovernance of supplier and technology dependencies; current updated edition.
[D14]The NIST Cybersecurity Framework (CSF) 2.0Govern, identify, protect, detect, respond and recover as organizational outcomes.
[D15]The February 2021 Cold Weather Outages in Texas and the South Central United StatesGas-electric dependency and common-cause cold-weather exposure.
[D16]Catastrophic Disasters: Enhanced Leadership, Capabilities, and Accountability Controls Will Improve the Effectiveness of the Nation's Preparedness, Response, and Recovery SystemKatrina lessons on coordination, capability and accountability.
[D17]The Fukushima Daiichi AccidentCompound external hazards, organizational assumptions and recovery challenges.
[D18]Final Report on the August 14, 2003 Blackout in the United States and Canada: Causes and RecommendationsSituational awareness and cascading power-system disruption.
[D19]Investigation: WannaCry cyber attack and the NHSDigital disruption and continuity of civilian healthcare.
[D20]Colonial Pipeline Cyber IncidentPublic record of pipeline shutdown and interagency response.
[D21]Sendai Framework for Disaster Risk Reduction 2015–2030Civilian risk governance, preparedness and recovery.

Section readings [D14]

SECTION 28

Operational observations and monitoring products

Operator and industry records can reveal service timing, constraints and recovery performance. They may also omit unsuccessful access attempts or frame restoration around assets rather than users. Compare operational evidence with independent investigation and community experience. Sensitive details require lawful custodianship, but aggregate accountability remains possible through defined service metrics and verified summaries. Preserve source limitations and avoid presenting a supplier's readiness declaration as an independent assessment. A transparent evidence interface can support scrutiny without publishing live-system vulnerabilities. [D13] Compare an asset-restoration timestamp with the time affected people regained usable service.

Operational observations should show what the system delivered, not merely that an asset was declared available. Inspect the acquisition process, sensor or reporting changes, gaps, coverage and quality controls. Compare records with independent observations where feasible. Aggregated performance, a status dashboard and user experience can diverge because they concern different units, locations, periods or definitions of availability.

Observation products to obtain for the case
ObservationUnitInterpretationProvenance record
Minimum essential-service coverage% defined population servedSpecify function, population and service-quality requirementRecord acquisition, coverage, timestamp, reference, quality controls and the responsible custodian.
Usable capacity marginservice-specific units or %Count capabilities available under the scenarioRecord acquisition, coverage, timestamp, reference, quality controls and the responsible custodian.
Alternative supply coverage% minimum requirementVerify independence and switching feasibilityRecord acquisition, coverage, timestamp, reference, quality controls and the responsible custodian.
Supplier concentration% essential inputs by sourceInclude shared upstream dependenciesRecord acquisition, coverage, timestamp, reference, quality controls and the responsible custodian.
Dependency documentation coverage% critical interfaces mappedRequire mechanism, owner and last reviewRecord acquisition, coverage, timestamp, reference, quality controls and the responsible custodian.
Common-cause exposure% capacity sharing defined exposureUse scenario-specific geography and technologyRecord acquisition, coverage, timestamp, reference, quality controls and the responsible custodian.
Staffed surge capacityservice-specific unitsDistinguish physical space from trained available staffRecord acquisition, coverage, timestamp, reference, quality controls and the responsible custodian.
Critical-role substitute coverage% roles with verified substituteExercise handover and availabilityRecord acquisition, coverage, timestamp, reference, quality controls and the responsible custodian.
Warning acknowledgement timeminutes or hoursRecord issue, receipt and authorized acknowledgementRecord acquisition, coverage, timestamp, reference, quality controls and the responsible custodian.
Shared situation-report latencyminutes or hoursMeasure age of relevant observationsRecord acquisition, coverage, timestamp, reference, quality controls and the responsible custodian.
Data integrity check coverage% critical recordsState check type and residual limitationsRecord acquisition, coverage, timestamp, reference, quality controls and the responsible custodian.
Backup continuity durationhours at specified loadUse tested demand and replenishment assumptionsRecord acquisition, coverage, timestamp, reference, quality controls and the responsible custodian.

Section readings [D13]

SECTION 29

Academic research and independent evidence

Academic and community evidence offer complementary perspectives on resilience. Research can test models and compare mechanisms; local observations reveal accessibility, trust and unmet needs. Evaluate methods and context rather than treating either source category as automatically superior. A theory developed for a power network may not transfer directly to healthcare demand or public administration. Community participation should allow people to challenge assumptions about acceptable degraded service. Scientific interpretation and distributive judgment should remain visible as distinct contributions. [D12] Compare a model-defined successful recovery with a community-defined account of continuing service barriers.

Read the research design before transferring a conclusion. Identify the question, unit of analysis, method, comparison, result, limitations and conditions that matter for the case. Foundational concepts, empirical studies, critical replications and technical syntheses serve different functions. A literature-supported mechanism may justify a hypothesis without validating a local threshold, forecasting performance or a complete TFP application.

Academic reading map: mechanisms and methods
IDResearch workContribution and limit
[D01]Identifying, understanding, and analyzing critical infrastructure interdependenciesPhysical, cyber, geographic and logical dependencies among essential systems.
[D02]Catastrophic cascade of failures in interdependent networksAn abstract network mechanism; empirical use requires system-specific validation.
[D03]Understanding Compound, Interconnected, Interacting, and Cascading Risks: A Holistic FrameworkDistinguishes forms of multi-system interaction and cascading risk.
[D04]Changing the resilience paradigmConnects risk assessment with maintaining and recovering essential function.
[D05]Four concepts for resilience and the implications for the future of resilience engineeringDistinguishes rebound, robustness, graceful extensibility and sustained adaptability.
[D06]Crisis Management in Hindsight: Cognition, Communication, Coordination, and ControlCoordination and shared understanding in crisis management.
[D07]Preparing for Critical Infrastructure Breakdowns: The Limits of Crisis Management and the Need for ResilienceLimits of conventional crisis planning under interconnected disruption.
[D08]Globally networked risks and how to respondSystemic interdependence and the limits of isolated risk analysis.
[D09]Review on modeling and simulation of interdependent critical infrastructure systemsComparison of modeling approaches and their assumptions.
[D10]Operational Models of Infrastructure ResilienceFunction-based analysis of infrastructure performance under disruption.
[D11]A Framework to Quantitatively Assess and Enhance the Seismic Resilience of CommunitiesRobustness, resourcefulness, redundancy and recovery in a community context.
[D12]A place-based model for understanding community resilience to natural disastersLocal context and uneven community capacity in resilience assessment.
[C03]Variance based sensitivity analysis of model output. Design and estimator for the total sensitivity indexMethodological reference for sensitivity analysis; assumptions about independence and the model structure must accompany the chosen estimator.
[C04]The FAIR Guiding Principles for scientific data management and stewardshipGuides metadata and reuse. Accessible data may still have legitimate authorization and protection requirements.
[C07]A general framework for analyzing sustainability of social-ecological systemsSupports a structured inquiry into actors, resources, institutions and interactions; institutional interpretation must be adapted to the system studied.

Section readings [D12]

PART IX

Evidence matrices and historical intelligence

SECTION 30

Source–variable correspondence

The source-to-variable map should show how each continuity metric is obtained. Usable capacity requires evidence of staff, supporting supplies and operating conditions; installed capacity alone is insufficient. A recovery time needs a clear start, end condition and affected function. Derived indices require explicit weighting and should retain the underlying observations. Record aggregation choices so that improved overall service cannot hide a prolonged outage affecting a smaller group. Reproducibility starts with consistent definitions before it reaches computation. [D11] Reconstruct one service indicator from records and explain how changing the recovery definition alters its value.

The source–variable matrix exposes the path from an observation to an analytical representation. Preserve the raw unit, time, location, method, transformation and uncertainty. Multiple derived variables may share one observation and therefore share its limitations. Record the code or reproducible procedure, authorized access and version. A score should remain inspectable through its originating evidence rather than replacing that evidence.

Source–variable design matrix
ObservationUnitSource requirementCandidate analytical questionTransformation and limit
Minimum essential-service coverage% defined population servedSpecify function, population and service-quality requirementP / stateVerify whether the observation supports this analytical use; preserve the raw record and transformation.
Usable capacity marginservice-specific units or %Count capabilities available under the scenarioP and ΔV / trajectoryVerify whether the observation supports this analytical use; preserve the raw record and transformation.
Alternative supply coverage% minimum requirementVerify independence and switching feasibilityσ / evidence qualityVerify whether the observation supports this analytical use; preserve the raw record and transformation.
Supplier concentration% essential inputs by sourceInclude shared upstream dependenciesLr / usable resourcesVerify whether the observation supports this analytical use; preserve the raw record and transformation.
Dependency documentation coverage% critical interfaces mappedRequire mechanism, owner and last reviewP / stateVerify whether the observation supports this analytical use; preserve the raw record and transformation.
Common-cause exposure% capacity sharing defined exposureUse scenario-specific geography and technologyP and ΔV / trajectoryVerify whether the observation supports this analytical use; preserve the raw record and transformation.
Staffed surge capacityservice-specific unitsDistinguish physical space from trained available staffσ / evidence qualityVerify whether the observation supports this analytical use; preserve the raw record and transformation.
Critical-role substitute coverage% roles with verified substituteExercise handover and availabilityLr / usable resourcesVerify whether the observation supports this analytical use; preserve the raw record and transformation.
Warning acknowledgement timeminutes or hoursRecord issue, receipt and authorized acknowledgementP / stateVerify whether the observation supports this analytical use; preserve the raw record and transformation.
Shared situation-report latencyminutes or hoursMeasure age of relevant observationsP and ΔV / trajectoryVerify whether the observation supports this analytical use; preserve the raw record and transformation.
Data integrity check coverage% critical recordsState check type and residual limitationsσ / evidence qualityVerify whether the observation supports this analytical use; preserve the raw record and transformation.
Backup continuity durationhours at specified loadUse tested demand and replenishment assumptionsLr / usable resourcesVerify whether the observation supports this analytical use; preserve the raw record and transformation.

Section readings [D11; C04; C05]

SECTION 31

Source–risk correspondence

Evidence-to-risk mapping requires a causal pathway. An outage report can document service loss without establishing which preparedness measure would have prevented it. Compare timing, enabling conditions and plausible alternatives. Shared-source evidence should not be counted as independent confirmation. Use the case investigations to distinguish findings, recommendations and later analytical interpretation. A strong risk map identifies what would falsify the proposed mechanism and where current evidence supports only a scenario rather than a verified relationship. [D18] Write one competing explanation for a service interruption and identify the evidence needed to distinguish it.

A source–risk matrix should cover the threat, the observed state, the mechanism and the consequences separately. Evidence that an event occurred does not alone show why a function failed or who was affected. Use a chronology and alternative explanations to test the chain. A citation becomes useful when the specific part of the claim it supports and its limits are visible.

Source–risk evidence matrix
RiskProposed mechanismEvidence chainInvestigation requirement
Common-cause service lossOne disturbance affects nominally redundant capabilitiesThreat / state → mechanism → consequence.Specify the dated observation for each link and at least one alternative explanation.
Single-source dependencyNo practical alternative supplies an essential inputThreat / state → mechanism → consequence.Specify the dated observation for each link and at least one alternative explanation.
Geographic concentrationCritical capacity shares exposure in one regionThreat / state → mechanism → consequence.Specify the dated observation for each link and at least one alternative explanation.
Supply-chain opacityHidden upstream suppliers concentrate riskThreat / state → mechanism → consequence.Specify the dated observation for each link and at least one alternative explanation.
Surge mismatchDemand rises while usable capacity fallsThreat / state → mechanism → consequence.Specify the dated observation for each link and at least one alternative explanation.
Staff unavailabilityEssential skills are absent during disruptionThreat / state → mechanism → consequence.Specify the dated observation for each link and at least one alternative explanation.
Communication fragmentationAgencies cannot form a shared service pictureThreat / state → mechanism → consequence.Specify the dated observation for each link and at least one alternative explanation.
Information integrity lossDecisions rely on incorrect or stale operational evidenceThreat / state → mechanism → consequence.Specify the dated observation for each link and at least one alternative explanation.
Warning non-acknowledgementCredible alerts fail to reach authorized actionThreat / state → mechanism → consequence.Specify the dated observation for each link and at least one alternative explanation.
Power continuity failureSupporting electricity cannot sustain minimum functionsThreat / state → mechanism → consequence.Specify the dated observation for each link and at least one alternative explanation.

Section readings [D18]

SECTION 32

Monitoring gaps and research priorities

Monitoring gaps often concern relationships rather than components. An operator may know its own inventory while lacking information about shared upstream suppliers or the accessibility of alternative services. Prioritize gaps by consequence for the civilian decision. Additional measurements of a well-observed asset may add less value than a basic account of an undocumented dependency. State where inference relies on assumed availability and what can be done while the gap persists. Observation limits should remain visible in readiness claims. [D01] Identify the unobserved dependency most likely to change the recommended continuity priority.

Prioritize a gap by its consequence for the decision. The next observation may be a targeted measurement, an independent comparison, a capability test or a correction of incompatible definitions. More data of the same kind may not resolve structural uncertainty. Specify the question, required observation, responsible custodian, time of collection and condition under which the gap is considered sufficiently addressed.

Case-analysis method
Monitoring gapDecision consequenceInvestigation
Spatial coverageExposed locations, groups or assets are not represented.Targeted observations matched to exposure.
Temporal resolutionA change occurs faster than the collection interval.A sampling interval fitted to the process and useful decision time.
Missing periodA critical part of the trajectory is absent.Independent backup and transparent missing-data handling.
Changing methodA sensor, reference or reporting practice changes.Overlap, comparison and version metadata.
Unmeasured mechanismImportant inputs or consequences are not observed.A mechanism-specific investigation and appropriate measurement.
Unverified resourcesA listed capacity has not been mobilized.Inspection and a representative deployment test.
Incompatible definitionsDatasets describe different populations, units or conditions.A documented harmonization and retained original values.
Access restrictionEvidence cannot be inspected or reused under current conditions.An authorized access and review arrangement.
Unequal representationSome users or effects disappear in aggregates.Disaggregated observation and a suitable participatory protocol.
Post-event follow-upReturn of service masks persistent effects.A monitoring period appropriate to the mechanism and affected function.

Section readings [D01; C03]

SECTION 33

Dependency matrix and propagation tests

The dependency matrix should describe direction, mechanism, delay and substitution at a suitable public level. Energy supports communications, while communications support coordination of energy recovery; these reciprocal links need not have equal strength or timing. Shared geography should be recorded separately from direct service dependence. A matrix becomes analytically useful when a scenario tests how losing one function affects minimum service elsewhere. Avoid turning qualitative links into numerical weights without explaining their evidence and intended interpretation. [D08] Compare a direct physical dependency with a coordination dependency and identify the different recovery actions each requires.

Capacity margins can vanish through simultaneous demand growth and supply loss. Surge demand for emergency communications, fuel or healthcare may occur exactly when staffing and infrastructure are impaired. Track both sides of the balance and distinguish ordinary reserves from capabilities usable under the scenario. [D11]

Situational awareness depends on timely observations, shared definitions and acknowledgement by authorized actors. A technically available signal can be operationally ineffective if it is inaccessible, distrusted or inconsistent with another agency’s information. Exercises should test interpretation and coordination as well as message transmission. [D06]

Continuity arrangements can preserve a minimum function while degrading convenience, capacity or equity. Such degradation should be explicit and time-bounded, with monitoring of affected groups. Returning to nominal operation without addressing unsafe assumptions can restore the conditions that produced the original disruption. [D05]

A dependency matrix should be directional and time-specific. Record the supplying function, receiving function, mechanism, useful delay, substitute and evidence. Test the destination when the origin becomes unavailable for different periods. Then remove a common prerequisite of the substitute. The resulting structure describes the case; it does not establish all connections in a global architecture or validate an edge weight.

Dependency matrix for case testing
DependencyMechanism and directionVerification or TFP inquiry
EnergyElectricity and fuel enable most continuity resourcesVerify actual minimum-load support and replenishment
Water and sanitationSafe water sustains healthcare, shelter and ordinary lifeProtect both quality and distribution access
HealthMedical capacity supports affected populations and essential workersMap staffed capacity and continuity needs
Food systemsDistribution depends on energy, transport and usable payment channelsAssess minimum supply and access
LogisticsTransport enables staff, supplies and recovery workIdentify scenario-appropriate alternative routes at aggregate level
Digital systemsCommunication and records support coordinationTest independent continuity and trustworthy restoration
GovernanceLawful authority and accountability shape emergency decisionsPreserve review, proportionality and clear roles
Scientific observationReliable evidence informs warnings and recovery verificationMaintain independent checks and uncertainty records
IndustrySpecialist components and maintenance support restorationAssess replacement lead times and compatibility
Urban systemsPopulation density and built environments shape consequenceMeasure vulnerable groups and accessible services

For each relationship, add the measured delay, duration of tolerable interruption, substitute and observation supporting the directed edge. Repeat the test for short, intermediate and extended unavailability. A generic list of linked sectors is not an estimated network, and no edge weight is validated by inclusion in this table.

Section readings [D08; C01; C02]

SECTION 34

Documented cases, near misses and recovery

Historical cases illustrate different combinations of exposure, dependency and institutional response. The 2003 blackout highlights system awareness and cascading interruption; Texas in 2021 highlights correlated weather exposure and gas-electric relationships; WannaCry shows digital disruption reaching civilian healthcare. These investigations do not establish a universal probability of strategic failure. Reconstruct the sequence from primary sources and preserve what was reasonably knowable before the outcome. Comparative learning is strongest when a recurring mechanism is identified alongside the conditions limiting transfer. [D15] [D19] Compare two cases using one dependency mechanism while keeping their technologies and civilian consequences distinct.

Historical analysis distinguishes observed loss, protective response, near miss and recovery. Several records can concern one event without becoming independent events. Preserve what the source actually investigated and avoid adding unsupported casualty, cost or restoration-time estimates. Compare cases by mechanism and evidence quality; the fact that one response was associated with an outcome does not alone establish a general causal effect.

Documented cases and comparative learning
Case / periodDocumented mechanism or study objectLearning and transfer questionSource
North American blackout, 2003Loss of situational awareness and power-system failures contributed to cascading disruptionCompare system-wide consequences with isolated component reliability[D18]
Hurricane Katrina, 2005Severe hazard exposure interacted with capability and coordination gapsTest shared response assumptions across jurisdictions[D16]
Fukushima Daiichi accident, 2011Compound external hazards challenged assumptions and essential supporting functionsAssess common-cause exposure and recovery constraints without equating different technologies[D17]
WannaCry and the NHS, 2017Digital disruption affected access to civilian healthcare servicesEvaluate essential service continuity and implementation of known preparedness measures[D19]
Colonial Pipeline incident, 2021A cyber incident prompted operational shutdown and interagency responseSeparate digital compromise, precautionary decisions and downstream service consequences[D20]
Texas and South Central U.S. cold-weather outages, 2021Cold exposure and gas-electric dependencies contributed to widespread service lossEvaluate usable preparedness and correlated dependencies rather than nominal reserves alone[D15]

Section readings [D15; D19]

SECTION 35

Integrated review, transfer and learning portfolio

Cross-domain synthesis should end with a defensible civilian preparedness decision. Identify the minimum function, affected groups, dependency most constraining continuity, evidence supporting the interpretation and the next lawful action. Explain alternatives and the conditions that would change the recommendation. Strategic resilience is strengthened when public accountability, independent evidence and practical recovery capability remain connected. An attractive network map or a completed checklist is useful only insofar as it helps preserve or restore the service people actually need. [D21] Prepare a decision memo that states both the expected continuity benefit and the unresolved distributional or evidentiary limitation.

The integrated portfolio should allow a reviewer to move from the question to observations, transformations, mechanism tests, scenarios and proposed monitoring. Make the strongest competing explanation and the most consequential unresolved gap visible. Transfer requires checking mechanisms, exposure and recovery resources in the new setting. Formation, optional credentialing, submission permission and licensing remain distinct processes; no case or data contribution enters the SIL without an associated fellow and applicable review.

Case-analysis method
Review stepEvidence requirement
SpecifyState the function, claim, exposed group, location and period.
TraceIdentify original observations, shared origins and transformations.
HarmonizeCompare units, reference systems, sampling and versions.
ChallengeTest alternative explanations and seek counter-evidence.
Evaluate uncertaintyIdentify which assumptions change the conclusion or recommended action.
Test transferCheck equivalence of mechanisms, exposure and recovery resources in another setting.
Record and updatePreserve reasons, limits, responsibility and the next review condition.

Section readings [D21; C04; C05]

RESEARCH AND READING PATHS

Annotated scientific and technical bibliography

The section citations connect domain mechanisms, methods and cases to the underlying sources. Read each reference for its question, design, findings and limits. Technical guides, case investigations and scholarly articles do not provide interchangeable forms of evidence.

  1. D01 · Scholarly article

    Rinaldi, S. M.; Peerenboom, J. P.; Kelly, T. K. (2001). Identifying, understanding, and analyzing critical infrastructure interdependencies. IEEE Control Systems Magazine 21(6), 11–25.

    Original publication / source ↗

    Physical, cyber, geographic and logical dependencies among essential systems.

  2. D02 · Scholarly research article

    Buldyrev, S. V. et al. (2010). Catastrophic cascade of failures in interdependent networks. Nature 464, 1025–1028.

    Original publication / source ↗

    An abstract network mechanism; empirical use requires system-specific validation.

  3. D03 · Scholarly article

    Pescaroli, G.; Alexander, D. (2018). Understanding Compound, Interconnected, Interacting, and Cascading Risks: A Holistic Framework. Risk Analysis 38, 2245–2257.

    Original publication / source ↗

    Distinguishes forms of multi-system interaction and cascading risk.

  4. D04 · Scholarly perspective

    Linkov, I. et al. (2014). Changing the resilience paradigm. Nature Climate Change 4, 407–409.

    Original publication / source ↗

    Connects risk assessment with maintaining and recovering essential function.

  5. D05 · Scholarly article

    Woods, D. D. (2015). Four concepts for resilience and the implications for the future of resilience engineering. Reliability Engineering & System Safety 141, 5–9.

    Original publication / source ↗

    Distinguishes rebound, robustness, graceful extensibility and sustained adaptability.

  6. D06 · Scholarly article

    Comfort, L. K. (2007). Crisis Management in Hindsight: Cognition, Communication, Coordination, and Control. Public Administration Review 67, 189–197.

    Original publication / source ↗

    Coordination and shared understanding in crisis management.

  7. D07 · Scholarly article

    Boin, A.; McConnell, A. (2007). Preparing for Critical Infrastructure Breakdowns: The Limits of Crisis Management and the Need for Resilience. Journal of Contingencies and Crisis Management 15, 50–59.

    Original publication / source ↗

    Limits of conventional crisis planning under interconnected disruption.

  8. D08 · Scholarly review

    Helbing, D. (2013). Globally networked risks and how to respond. Nature 497, 51–59.

    Original publication / source ↗

    Systemic interdependence and the limits of isolated risk analysis.

  9. D09 · Scholarly review

    Ouyang, M. (2014). Review on modeling and simulation of interdependent critical infrastructure systems. Reliability Engineering & System Safety 121, 43–60.

    Original publication / source ↗

    Comparison of modeling approaches and their assumptions.

  10. D10 · Scholarly research article

    Alderson, D. L.; Brown, G. G.; Carlyle, W. M. (2015). Operational Models of Infrastructure Resilience. Risk Analysis 35, 562–586.

    Original publication / source ↗

    Function-based analysis of infrastructure performance under disruption.

  11. D11 · Scholarly article

    Bruneau, M. et al. (2003). A Framework to Quantitatively Assess and Enhance the Seismic Resilience of Communities. Earthquake Spectra 19, 733–752.

    Original publication / source ↗

    Robustness, resourcefulness, redundancy and recovery in a community context.

  12. D12 · Scholarly article

    Cutter, S. L. et al. (2008). A place-based model for understanding community resilience to natural disasters. Global Environmental Change 18, 598–606.

    Original publication / source ↗

    Local context and uneven community capacity in resilience assessment.

  13. D13 · Official technical guidance

    NIST (2024). Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations. SP 800-161 Rev. 1, Update 1.

    Original publication / source ↗

    Governance of supplier and technology dependencies; current updated edition.

  14. D14 · Official framework

    NIST (2024). The NIST Cybersecurity Framework (CSF) 2.0. NIST CSWP 29.

    Original publication / source ↗

    Govern, identify, protect, detect, respond and recover as organizational outcomes.

  15. D15 · Official investigation

    FERC; NERC; Regional Entity Staff (2021). The February 2021 Cold Weather Outages in Texas and the South Central United States. Joint staff report.

    Original publication / source ↗

    Gas-electric dependency and common-cause cold-weather exposure.

  16. D16 · Official investigation

    U.S. GAO (2006). Catastrophic Disasters: Enhanced Leadership, Capabilities, and Accountability Controls Will Improve the Effectiveness of the Nation's Preparedness, Response, and Recovery System. GAO-06-618.

    Original publication / source ↗

    Katrina lessons on coordination, capability and accountability.

  17. D17 · Official technical investigation

    IAEA (2015). The Fukushima Daiichi Accident. Director General's report and technical volumes.

    Original publication / source ↗

    Compound external hazards, organizational assumptions and recovery challenges.

  18. D18 · Official investigation

    U.S.–Canada Power System Outage Task Force (2004). Final Report on the August 14, 2003 Blackout in the United States and Canada: Causes and Recommendations. Joint task-force report.

    Original publication / source ↗

    Situational awareness and cascading power-system disruption.

  19. D19 · Official investigation

    UK National Audit Office (2017). Investigation: WannaCry cyber attack and the NHS. Report HC 414.

    Original publication / source ↗

    Digital disruption and continuity of civilian healthcare.

  20. D20 · Official incident record

    U.S. Department of Energy (2021). Colonial Pipeline Cyber Incident. Office of Cybersecurity, Energy Security, and Emergency Response.

    Original publication / source ↗

    Public record of pipeline shutdown and interagency response.

  21. D21 · Official framework

    UNDRR (2015). Sendai Framework for Disaster Risk Reduction 2015–2030. United Nations framework.

    Original publication / source ↗

    Civilian risk governance, preparedness and recovery.

  22. C03 · peer-reviewed

    Saltelli, A. et al. (2010). Variance based sensitivity analysis of model output. Design and estimator for the total sensitivity index. Computer Physics Communications, 181, 259–270.

    Original publication / source ↗

    Methodological reference for sensitivity analysis; assumptions about independence and the model structure must accompany the chosen estimator.

  23. C04 · peer-reviewed

    Wilkinson, M. D. et al. (2016). The FAIR Guiding Principles for scientific data management and stewardship. Scientific Data, 3, 160018.

    Original publication / source ↗

    Guides metadata and reuse. Accessible data may still have legitimate authorization and protection requirements.

  24. C05 · standard

    W3C (2013). PROV-DM: The PROV Data Model. W3C Recommendation, 30 April 2013.

    Original publication / source ↗

    Represents provenance through entities, activities and agents; useful for connecting a result to its transformations and responsible contributors.

  25. C06 · technical guide

    JCGM (2008). Evaluation of measurement data — Supplement 1 to the GUM — Propagation of distributions using a Monte Carlo method. JCGM 101:2008.

    Original publication / source ↗

    A methodological basis for propagating input distributions through a specified model, rather than treating simulated frequency as an observed event probability.

  26. C07 · peer-reviewed

    Ostrom, E. (2009). A general framework for analyzing sustainability of social-ecological systems. Science, 325, 419–422.

    Original publication / source ↗

    Supports a structured inquiry into actors, resources, institutions and interactions; institutional interpretation must be adapted to the system studied.

External sources are cited for research and learning. Their inclusion implies no partnership, certification or institutional endorsement.