Black Swan Preparedness¶
Prepare for consequential surprise by protecting survival floors, reducing concentrated exposure, preserving slack and options, limiting cascades, enabling bounded improvisation, and rebuilding adaptively without pretending to predict the unknown event.
Essence¶
Black-Swan Preparedness builds survival and adaptation capacity for high-impact events that lie outside the trusted forecast set. It does not claim to predict unknown unknowns. It asks which functions and rights must survive model failure, which architectural features turn surprise into catastrophe, and which reserves, boundaries, options, authorities, local capabilities, and recovery paths remain valuable across many shocks.
The archetype shifts attention from event enumeration to consequence architecture. Concentration, common-mode dependence, zero slack, irreversible commitment, tight coupling, centralized bottlenecks, and fragile recovery magnify almost any surprise. Modularity, genuine diversity, protected reserves, optionality, sentinel networks, bounded improvisation, mutual aid, and adaptive rebuild reduce that amplification.
Compression statement¶
Black-Swan Preparedness designs for failure of the forecast set. It defines critical functions and survival floors; records model limits and unknown dependencies; maps exposure, irreversibility, tail dependence, and cascades; protects reserves; adds modularity, firebreaks, genuine diversity, options, sentinels, bounded emergency authority, local agency, continuity and mutual aid; governs recovery and adaptive rebuild; learns without hindsight overfit; and protects legitimacy, equity, rights, and emergency-power expiry. It substitutes general survival and adaptation capacity for false precision about event probability.
Canonical formula: surprise_resilience = survival_floor + slack + modularity + diversity + optionality + local_agency + mutual_aid + adaptive_recovery + legitimacy - concentration - tight_coupling - irreversible_exposure - common_mode_failure - permanent_emergency_power
When to Use This Archetype¶
Use it when critical or irreversible outcomes depend on models that may omit event classes, when tail dependence can defeat diversification, when cascades cross boundaries, or when ordinary scripts and central coordination may fail. It is appropriate in infrastructure, finance, health, supply networks, digital systems, governance, ecology, and community resilience.
Do not use black-swan language to excuse foreseeable negligence. Frequent, well-understood failures still need ordinary prevention and response. Nor should preparedness become a promise of prediction, a permanent emergency regime, or a dramatic scenario exercise without tested capacity.
Structural Problem¶
Systems optimized for ordinary variance often remove the very capacities that make surprise survivable. Reserves look idle, diversity looks expensive, modularity looks redundant, and local discretion looks inconsistent. Forecast confidence then encourages concentration and irreversible commitments. When the model fails, defenses fail together and response authority arrives late.
The central tension is efficient specialization versus general survival. Preparedness has visible carrying costs before an event and uncertain attribution afterward. Yet catastrophic exposure is often created precisely by treating unused capacity and alternative paths as waste.
A mature intervention makes survival floors, model limits, cascade paths, reserve rights, emergency authority, equity, and recovery choices inspectable before the shock.
Intervention Logic¶
- Critical Function and Survival Floor. Defines the people, functions, rights, assets, and minimum service states that must survive even when the initiating event was not predicted. Preparedness cannot protect everything equally. A survival floor makes consequence, equity, and restoration order explicit before crisis bargaining begins.
- Epistemic Humility and Surprise Boundary. States what models omit, where probabilities are unreliable, which dependencies remain unknown, and which claims must not be treated as complete. Black-swan preparedness is not a promise to enumerate unknown unknowns. It designs for model failure and surprise without pretending surprise has been predicted.
- Exposure, Concentration, and Irreversibility Map. Locates concentrated value, single points of loss, irreversible commitments, fragile dependencies, and conditions under which ordinary recovery becomes impossible. Large impact often comes from exposure architecture rather than event frequency. Reducing concentration and irreversible coupling can matter more than refining probability.
- Tail Dependence and Common-Mode Review. Tests whether nominally diverse assets, regions, suppliers, models, or defenses fail together under stress. Ordinary correlation can understate crisis dependence. Shared infrastructure, incentives, climate, finance, software, or governance can collapse diversification when it is most needed.
- Impact Cascade and Second-Order Consequence Map. Traces direct shock, propagation, feedback, substitution, behavioral response, legitimacy effects, and delayed consequences across system boundaries. The initiating event may be unknowable while cascade pathways remain designable. Mapping consequence structure avoids scenario-specific tunnel vision.
- Slack, Reserve, and Capacity Floor. Maintains protected financial, material, staffing, attention, time, and infrastructure capacity for shocks outside the forecast set. Reserve must be real, accessible, and protected from routine consumption. Idle-looking capacity is an option against model error.
- Modularity, Firebreak, and Blast-Radius Control. Partitions systems so failure, compromise, shortage, or misinformation cannot propagate without limit. Boundaries should allow isolation and graceful degradation while preserving essential exchange and avoiding abandonment of vulnerable parts.
- Redundancy, Diversity, and Independence Design. Creates genuinely different ways to perform critical functions, with explicit dependency and correlated-failure checks. Copies are not resilient when they share the same platform, geography, model, supplier, authority, or failure assumption.
- Optionality, Reversibility, and Exit Portfolio. Preserves multiple viable courses of action, delayed commitment, rollback, substitution, and escape routes before uncertainty resolves. Options have carrying cost, but they prevent one forecast from locking the whole system into an unrecoverable path.
- Weak-Signal, Anomaly, and Sentinel Network. Monitors distributed anomalies, boundary violations, near misses, local knowledge, and emerging conditions without requiring a known event template. Signals are used to shorten surprise and response delay, not to claim reliable prediction of the event class.
- Trigger, Escalation, and Emergency Authority. Defines who may declare exceptional conditions, release reserves, isolate components, suspend rules, and coordinate response, with evidence and limits. Ambiguous authority wastes the brief period when containment and survival actions remain possible; unbounded authority turns preparedness into abuse.
- Decentralized Improvisation and Local Agency. Equips local actors with objectives, boundaries, resources, communication, and permission to adapt when central plans are obsolete or unreachable. Surprise invalidates detailed scripts. Local agency must be competent and bounded, not abandoned without support or accountability.
- Continuity, Mutual Aid, and Substitution Network. Prearranges alternate suppliers, reciprocal support, manual modes, cross-training, temporary facilities, and interoperable handoffs. Mutual aid works only if capacity, priority, activation, reimbursement, and dependency assumptions are tested before simultaneous demand.
- Recovery, Reconstitution, and Adaptive Rebuild. Restores critical function in stages, preserves evidence, prevents repeated exposure, and decides what should be rebuilt, redesigned, or retired. Recovery is not automatic return to the fragile baseline. The shock can reveal new constraints and opportunities for safer structure.
- Learning Without Story Overfit. Extracts structural lessons while resisting hindsight certainty, single-cause stories, false universality, and preparation for only the last event. Black-swan narratives can make the improbable look obvious after the fact. Learning should improve general capacities and boundaries rather than rehearse one screenplay.
- Legitimacy, Equity, and Safeguard Governance. Protects rights, priority fairness, transparency, appeal, vulnerable groups, emergency-power expiry, and accountable burden allocation before, during, and after surprise. Preparedness that saves aggregate capacity by abandoning low-power groups or normalizing permanent emergency authority is not mature resilience.
The lifecycle is deliberately event-agnostic but not consequence-agnostic. New evidence can change exposure maps, reserve levels, authority, and recovery design, but it cannot erase the survival floor or safeguards without explicit review.
Key Components¶
| Component | Description |
|---|---|
| Critical Function and Survival Floor ↗ | Defines the people, functions, rights, assets, and minimum service states that must survive even when the initiating event was not predicted. Semantic canonical mapping retained the complete legacy component record: {"slug":"critical_function_and_survival_floor","name":"Critical Function and Survival Floor","role":"Defines the people, functions, rights, assets, and minimum service states that must survive even when the initiating event was not predicted.","notes":"Preparedness cannot protect everything equally. A survival floor makes consequence, equity, and restoration order explicit before crisis bargaining begins.","component_type":"required_structural_component","reuse_scope":"cross_domain","maturity":"provisional","host_archetypes":["black_swan_preparedness"],"not_a_mechanism_because":"This is a persistent preparedness responsibility, not a particular reserve, drill, contract, dashboard, or emergency tool."} |
| Epistemic Humility and Surprise Boundary ↗ | States what models omit, where probabilities are unreliable, which dependencies remain unknown, and which claims must not be treated as complete. Semantic canonical mapping retained the complete legacy component record: {"slug":"epistemic_humility_and_surprise_boundary","name":"Epistemic Humility and Surprise Boundary","role":"States what models omit, where probabilities are unreliable, which dependencies remain unknown, and which claims must not be treated as complete.","notes":"Black-swan preparedness is not a promise to enumerate unknown unknowns. It designs for model failure and surprise without pretending surprise has been predicted.","component_type":"required_structural_component","reuse_scope":"cross_domain","maturity":"provisional","host_archetypes":["black_swan_preparedness"],"not_a_mechanism_because":"This is a persistent preparedness responsibility, not a particular reserve, drill, contract, dashboard, or emergency tool."} |
| Exposure, Concentration, and Irreversibility Map ↗ | Locates concentrated value, single points of loss, irreversible commitments, fragile dependencies, and conditions under which ordinary recovery becomes impossible. Semantic canonical mapping retained the complete legacy component record: {"slug":"exposure_concentration_and_irreversibility_map","name":"Exposure, Concentration, and Irreversibility Map","role":"Locates concentrated value, single points of loss, irreversible commitments, fragile dependencies, and conditions under which ordinary recovery becomes impossible.","notes":"Large impact often comes from exposure architecture rather than event frequency. Reducing concentration and irreversible coupling can matter more than refining probability.","component_type":"required_structural_component","reuse_scope":"cross_domain","maturity":"provisional","host_archetypes":["black_swan_preparedness"],"not_a_mechanism_because":"This is a persistent preparedness responsibility, not a particular reserve, drill, contract, dashboard, or emergency tool."} |
| Tail Dependence and Common-Mode Review ↗ | Tests whether nominally diverse assets, regions, suppliers, models, or defenses fail together under stress. Semantic canonical mapping retained the complete legacy component record: {"slug":"tail_dependence_and_common_mode_review","name":"Tail Dependence and Common-Mode Review","role":"Tests whether nominally diverse assets, regions, suppliers, models, or defenses fail together under stress.","notes":"Ordinary correlation can understate crisis dependence. Shared infrastructure, incentives, climate, finance, software, or governance can collapse diversification when it is most needed.","component_type":"required_structural_component","reuse_scope":"cross_domain","maturity":"provisional","host_archetypes":["black_swan_preparedness"],"not_a_mechanism_because":"This is a persistent preparedness responsibility, not a particular reserve, drill, contract, dashboard, or emergency tool."} |
| Impact Cascade and Second-Order Consequence Map ↗ | Traces direct shock, propagation, feedback, substitution, behavioral response, legitimacy effects, and delayed consequences across system boundaries. Semantic canonical mapping retained the complete legacy component record: {"slug":"impact_cascade_and_second_order_consequence_map","name":"Impact Cascade and Second-Order Consequence Map","role":"Traces direct shock, propagation, feedback, substitution, behavioral response, legitimacy effects, and delayed consequences across system boundaries.","notes":"The initiating event may be unknowable while cascade pathways remain designable. Mapping consequence structure avoids scenario-specific tunnel vision.","component_type":"required_structural_component","reuse_scope":"cross_domain","maturity":"provisional","host_archetypes":["black_swan_preparedness"],"not_a_mechanism_because":"This is a persistent preparedness responsibility, not a particular reserve, drill, contract, dashboard, or emergency tool."} |
| Slack, Reserve, and Capacity Floor ↗ | Maintains protected financial, material, staffing, attention, time, and infrastructure capacity for shocks outside the forecast set. Semantic canonical mapping retained the complete legacy component record: {"slug":"slack_reserve_and_capacity_floor","name":"Slack, Reserve, and Capacity Floor","role":"Maintains protected financial, material, staffing, attention, time, and infrastructure capacity for shocks outside the forecast set.","notes":"Reserve must be real, accessible, and protected from routine consumption. Idle-looking capacity is an option against model error.","component_type":"required_structural_component","reuse_scope":"cross_domain","maturity":"provisional","host_archetypes":["black_swan_preparedness"],"not_a_mechanism_because":"This is a persistent preparedness responsibility, not a particular reserve, drill, contract, dashboard, or emergency tool."} |
| Modularity, Firebreak, and Blast-Radius Control ↗ | Partitions systems so failure, compromise, shortage, or misinformation cannot propagate without limit. Semantic canonical mapping retained the complete legacy component record: {"slug":"modularity_firebreak_and_blast_radius_control","name":"Modularity, Firebreak, and Blast-Radius Control","role":"Partitions systems so failure, compromise, shortage, or misinformation cannot propagate without limit.","notes":"Boundaries should allow isolation and graceful degradation while preserving essential exchange and avoiding abandonment of vulnerable parts.","component_type":"required_structural_component","reuse_scope":"cross_domain","maturity":"provisional","host_archetypes":["black_swan_preparedness"],"not_a_mechanism_because":"This is a persistent preparedness responsibility, not a particular reserve, drill, contract, dashboard, or emergency tool."} |
| Redundancy, Diversity, and Independence Design ↗ | Creates genuinely different ways to perform critical functions, with explicit dependency and correlated-failure checks. Semantic canonical mapping retained the complete legacy component record: {"slug":"redundancy_diversity_and_independence_design","name":"Redundancy, Diversity, and Independence Design","role":"Creates genuinely different ways to perform critical functions, with explicit dependency and correlated-failure checks.","notes":"Copies are not resilient when they share the same platform, geography, model, supplier, authority, or failure assumption.","component_type":"required_structural_component","reuse_scope":"cross_domain","maturity":"provisional","host_archetypes":["black_swan_preparedness"],"not_a_mechanism_because":"This is a persistent preparedness responsibility, not a particular reserve, drill, contract, dashboard, or emergency tool."} |
| Optionality, Reversibility, and Exit Portfolio ↗ | Preserves multiple viable courses of action, delayed commitment, rollback, substitution, and escape routes before uncertainty resolves. Semantic canonical mapping retained the complete legacy component record: {"slug":"optionality_reversibility_and_exit_portfolio","name":"Optionality, Reversibility, and Exit Portfolio","role":"Preserves multiple viable courses of action, delayed commitment, rollback, substitution, and escape routes before uncertainty resolves.","notes":"Options have carrying cost, but they prevent one forecast from locking the whole system into an unrecoverable path.","component_type":"required_structural_component","reuse_scope":"cross_domain","maturity":"provisional","host_archetypes":["black_swan_preparedness"],"not_a_mechanism_because":"This is a persistent preparedness responsibility, not a particular reserve, drill, contract, dashboard, or emergency tool."} |
| Weak-Signal, Anomaly, and Sentinel Network ↗ | Monitors distributed anomalies, boundary violations, near misses, local knowledge, and emerging conditions without requiring a known event template. Semantic canonical mapping retained the complete legacy component record: {"slug":"weak_signal_anomaly_and_sentinel_network","name":"Weak-Signal, Anomaly, and Sentinel Network","role":"Monitors distributed anomalies, boundary violations, near misses, local knowledge, and emerging conditions without requiring a known event template.","notes":"Signals are used to shorten surprise and response delay, not to claim reliable prediction of the event class.","component_type":"required_structural_component","reuse_scope":"cross_domain","maturity":"provisional","host_archetypes":["black_swan_preparedness"],"not_a_mechanism_because":"This is a persistent preparedness responsibility, not a particular reserve, drill, contract, dashboard, or emergency tool."} |
| Trigger, Escalation, and Emergency Authority ↗ | Defines who may declare exceptional conditions, release reserves, isolate components, suspend rules, and coordinate response, with evidence and limits. Semantic canonical mapping retained the complete legacy component record: {"slug":"trigger_escalation_and_emergency_authority","name":"Trigger, Escalation, and Emergency Authority","role":"Defines who may declare exceptional conditions, release reserves, isolate components, suspend rules, and coordinate response, with evidence and limits.","notes":"Ambiguous authority wastes the brief period when containment and survival actions remain possible; unbounded authority turns preparedness into abuse.","component_type":"required_structural_component","reuse_scope":"cross_domain","maturity":"provisional","host_archetypes":["black_swan_preparedness"],"not_a_mechanism_because":"This is a persistent preparedness responsibility, not a particular reserve, drill, contract, dashboard, or emergency tool."} |
| Decentralized Improvisation and Local Agency ↗ | Equips local actors with objectives, boundaries, resources, communication, and permission to adapt when central plans are obsolete or unreachable. Semantic canonical mapping retained the complete legacy component record: {"slug":"decentralized_improvisation_and_local_agency","name":"Decentralized Improvisation and Local Agency","role":"Equips local actors with objectives, boundaries, resources, communication, and permission to adapt when central plans are obsolete or unreachable.","notes":"Surprise invalidates detailed scripts. Local agency must be competent and bounded, not abandoned without support or accountability.","component_type":"required_structural_component","reuse_scope":"cross_domain","maturity":"provisional","host_archetypes":["black_swan_preparedness"],"not_a_mechanism_because":"This is a persistent preparedness responsibility, not a particular reserve, drill, contract, dashboard, or emergency tool."} |
| Continuity, Mutual Aid, and Substitution Network ↗ | Prearranges alternate suppliers, reciprocal support, manual modes, cross-training, temporary facilities, and interoperable handoffs. Semantic canonical mapping retained the complete legacy component record: {"slug":"continuity_mutual_aid_and_substitution_network","name":"Continuity, Mutual Aid, and Substitution Network","role":"Prearranges alternate suppliers, reciprocal support, manual modes, cross-training, temporary facilities, and interoperable handoffs.","notes":"Mutual aid works only if capacity, priority, activation, reimbursement, and dependency assumptions are tested before simultaneous demand.","component_type":"required_structural_component","reuse_scope":"cross_domain","maturity":"provisional","host_archetypes":["black_swan_preparedness"],"not_a_mechanism_because":"This is a persistent preparedness responsibility, not a particular reserve, drill, contract, dashboard, or emergency tool."} |
| Recovery, Reconstitution, and Adaptive Rebuild ↗ | Restores critical function in stages, preserves evidence, prevents repeated exposure, and decides what should be rebuilt, redesigned, or retired. Semantic canonical mapping retained the complete legacy component record: {"slug":"recovery_reconstitution_and_adaptive_rebuild","name":"Recovery, Reconstitution, and Adaptive Rebuild","role":"Restores critical function in stages, preserves evidence, prevents repeated exposure, and decides what should be rebuilt, redesigned, or retired.","notes":"Recovery is not automatic return to the fragile baseline. The shock can reveal new constraints and opportunities for safer structure.","component_type":"required_structural_component","reuse_scope":"cross_domain","maturity":"provisional","host_archetypes":["black_swan_preparedness"],"not_a_mechanism_because":"This is a persistent preparedness responsibility, not a particular reserve, drill, contract, dashboard, or emergency tool."} |
| Learning Without Story Overfit ↗ | Extracts structural lessons while resisting hindsight certainty, single-cause stories, false universality, and preparation for only the last event. Semantic canonical mapping retained the complete legacy component record: {"slug":"learning_without_story_overfit","name":"Learning Without Story Overfit","role":"Extracts structural lessons while resisting hindsight certainty, single-cause stories, false universality, and preparation for only the last event.","notes":"Black-swan narratives can make the improbable look obvious after the fact. Learning should improve general capacities and boundaries rather than rehearse one screenplay.","component_type":"required_structural_component","reuse_scope":"cross_domain","maturity":"provisional","host_archetypes":["black_swan_preparedness"],"not_a_mechanism_because":"This is a persistent preparedness responsibility, not a particular reserve, drill, contract, dashboard, or emergency tool."} |
| Legitimacy, Equity, and Safeguard Governance ↗ | Protects rights, priority fairness, transparency, appeal, vulnerable groups, emergency-power expiry, and accountable burden allocation before, during, and after surprise. Semantic canonical mapping retained the complete legacy component record: {"slug":"legitimacy_equity_and_safeguard_governance","name":"Legitimacy, Equity, and Safeguard Governance","role":"Protects rights, priority fairness, transparency, appeal, vulnerable groups, emergency-power expiry, and accountable burden allocation before, during, and after surprise.","notes":"Preparedness that saves aggregate capacity by abandoning low-power groups or normalizing permanent emergency authority is not mature resilience.","component_type":"required_structural_component","reuse_scope":"cross_domain","maturity":"provisional","host_archetypes":["black_swan_preparedness"],"not_a_mechanism_because":"This is a persistent preparedness responsibility, not a particular reserve, drill, contract, dashboard, or emergency tool."} |
Common Mechanisms¶
| Mechanism | Description |
|---|---|
| Reverse Stress and Failure-Budget Test (`reverse_stress_and_failure_budget_test`) ↗ | Type: stress_test Starts from unacceptable system loss and asks which combinations of failure could reach it without assigning a trusted probability. Selection constraints and retained implementation evidence: strengthen general surprise capacity rather than predict one event; protect critical functions and vulnerable groups; retain authority limits, traceability, and recovery; Complete legacy mechanism record retained: {"slug":"reverse_stress_and_failure_budget_test","name":"Reverse Stress and Failure-Budget Test","mechanism_type":"stress_test","role":"Starts from unacceptable system loss and asks which combinations of failure could reach it without assigning a trusted probability.","maturity":"provisional","instantiates_archetypes":["black_swan_preparedness"],"selection_constraints":["strengthen general surprise capacity rather than predict one event","protect critical functions and vulnerable groups","retain authority limits, traceability, and recovery"],"not_an_archetype_because":"This is a concrete standard, reserve, drill, review, monitoring process, gate, or agreement used inside the broader preparedness lifecycle."} |
| Minimum Viable Service Floor (`minimum_viable_service_floor`) ↗ | Type: service_standard Defines critical outputs, recipients, restoration order, and tolerable degradation under severe disruption. Selection constraints and retained implementation evidence: strengthen general surprise capacity rather than predict one event; protect critical functions and vulnerable groups; retain authority limits, traceability, and recovery; Complete legacy mechanism record retained: {"slug":"minimum_viable_service_floor","name":"Minimum Viable Service Floor","mechanism_type":"service_standard","role":"Defines critical outputs, recipients, restoration order, and tolerable degradation under severe disruption.","maturity":"provisional","instantiates_archetypes":["black_swan_preparedness"],"selection_constraints":["strengthen general surprise capacity rather than predict one event","protect critical functions and vulnerable groups","retain authority limits, traceability, and recovery"],"not_an_archetype_because":"This is a concrete standard, reserve, drill, review, monitoring process, gate, or agreement used inside the broader preparedness lifecycle."} |
| Protected Contingency Reserve (`protected_contingency_reserve`) ↗ | Type: reserve Maintains releasable capacity with access, replenishment, anti-raiding, and audit rules. Selection constraints and retained implementation evidence: strengthen general surprise capacity rather than predict one event; protect critical functions and vulnerable groups; retain authority limits, traceability, and recovery; Complete legacy mechanism record retained: {"slug":"protected_contingency_reserve","name":"Protected Contingency Reserve","mechanism_type":"reserve","role":"Maintains releasable capacity with access, replenishment, anti-raiding, and audit rules.","maturity":"provisional","instantiates_archetypes":["black_swan_preparedness"],"selection_constraints":["strengthen general surprise capacity rather than predict one event","protect critical functions and vulnerable groups","retain authority limits, traceability, and recovery"],"not_an_archetype_because":"This is a concrete standard, reserve, drill, review, monitoring process, gate, or agreement used inside the broader preparedness lifecycle."} |
| Modular Isolation and Firebreak Drill (`modular_isolation_and_firebreak_drill`) ↗ | Type: exercise Tests whether components can be isolated, degraded, or disconnected without collapsing critical function. Selection constraints and retained implementation evidence: strengthen general surprise capacity rather than predict one event; protect critical functions and vulnerable groups; retain authority limits, traceability, and recovery; Complete legacy mechanism record retained: {"slug":"modular_isolation_and_firebreak_drill","name":"Modular Isolation and Firebreak Drill","mechanism_type":"exercise","role":"Tests whether components can be isolated, degraded, or disconnected without collapsing critical function.","maturity":"provisional","instantiates_archetypes":["black_swan_preparedness"],"selection_constraints":["strengthen general surprise capacity rather than predict one event","protect critical functions and vulnerable groups","retain authority limits, traceability, and recovery"],"not_an_archetype_because":"This is a concrete standard, reserve, drill, review, monitoring process, gate, or agreement used inside the broader preparedness lifecycle."} |
| Common-Mode Dependency Red Team (`common_mode_dependency_red_team`) ↗ | Type: review Challenges claims of diversification by tracing shared suppliers, infrastructure, data, models, geography, incentives, and authority. Selection constraints and retained implementation evidence: strengthen general surprise capacity rather than predict one event; protect critical functions and vulnerable groups; retain authority limits, traceability, and recovery; Complete legacy mechanism record retained: {"slug":"common_mode_dependency_red_team","name":"Common-Mode Dependency Red Team","mechanism_type":"review","role":"Challenges claims of diversification by tracing shared suppliers, infrastructure, data, models, geography, incentives, and authority.","maturity":"provisional","instantiates_archetypes":["black_swan_preparedness"],"selection_constraints":["strengthen general surprise capacity rather than predict one event","protect critical functions and vulnerable groups","retain authority limits, traceability, and recovery"],"not_an_archetype_because":"This is a concrete standard, reserve, drill, review, monitoring process, gate, or agreement used inside the broader preparedness lifecycle."} |
| No-Script Adaptive Response Exercise (`no_script_adaptive_response_exercise`) ↗ | Type: exercise Withholds the familiar scenario and tests objective-based local improvisation, communication loss, authority, and escalation. Selection constraints and retained implementation evidence: strengthen general surprise capacity rather than predict one event; protect critical functions and vulnerable groups; retain authority limits, traceability, and recovery; Complete legacy mechanism record retained: {"slug":"no_script_adaptive_response_exercise","name":"No-Script Adaptive Response Exercise","mechanism_type":"exercise","role":"Withholds the familiar scenario and tests objective-based local improvisation, communication loss, authority, and escalation.","maturity":"provisional","instantiates_archetypes":["black_swan_preparedness"],"selection_constraints":["strengthen general surprise capacity rather than predict one event","protect critical functions and vulnerable groups","retain authority limits, traceability, and recovery"],"not_an_archetype_because":"This is a concrete standard, reserve, drill, review, monitoring process, gate, or agreement used inside the broader preparedness lifecycle."} |
| Sentinel Anomaly and Near-Miss Register (`sentinel_anomaly_and_near_miss_register`) ↗ | Type: monitoring Aggregates unusual events, boundary breaches, local reports, and near misses while preserving uncertainty and dissent. Selection constraints and retained implementation evidence: strengthen general surprise capacity rather than predict one event; protect critical functions and vulnerable groups; retain authority limits, traceability, and recovery; Complete legacy mechanism record retained: {"slug":"sentinel_anomaly_and_near_miss_register","name":"Sentinel Anomaly and Near-Miss Register","mechanism_type":"monitoring","role":"Aggregates unusual events, boundary breaches, local reports, and near misses while preserving uncertainty and dissent.","maturity":"provisional","instantiates_archetypes":["black_swan_preparedness"],"selection_constraints":["strengthen general surprise capacity rather than predict one event","protect critical functions and vulnerable groups","retain authority limits, traceability, and recovery"],"not_an_archetype_because":"This is a concrete standard, reserve, drill, review, monitoring process, gate, or agreement used inside the broader preparedness lifecycle."} |
| Emergency-Authority Activation and Sunset Gate (`emergency_authority_activation_and_sunset_gate`) ↗ | Type: governance Requires bounded triggers, logged actions, independent review, expiry, renewal, and restoration of ordinary authority. Selection constraints and retained implementation evidence: strengthen general surprise capacity rather than predict one event; protect critical functions and vulnerable groups; retain authority limits, traceability, and recovery; Complete legacy mechanism record retained: {"slug":"emergency_authority_activation_and_sunset_gate","name":"Emergency-Authority Activation and Sunset Gate","mechanism_type":"governance","role":"Requires bounded triggers, logged actions, independent review, expiry, renewal, and restoration of ordinary authority.","maturity":"provisional","instantiates_archetypes":["black_swan_preparedness"],"selection_constraints":["strengthen general surprise capacity rather than predict one event","protect critical functions and vulnerable groups","retain authority limits, traceability, and recovery"],"not_an_archetype_because":"This is a concrete standard, reserve, drill, review, monitoring process, gate, or agreement used inside the broader preparedness lifecycle."} |
| Mutual-Aid and Substitution Agreement (`mutual_aid_and_substitution_agreement`) ↗ | Type: contract Predefines interoperable assistance, priority, capacity, reimbursement, liability, activation, and simultaneous-demand limits. Selection constraints and retained implementation evidence: strengthen general surprise capacity rather than predict one event; protect critical functions and vulnerable groups; retain authority limits, traceability, and recovery; Complete legacy mechanism record retained: {"slug":"mutual_aid_and_substitution_agreement","name":"Mutual-Aid and Substitution Agreement","mechanism_type":"contract","role":"Predefines interoperable assistance, priority, capacity, reimbursement, liability, activation, and simultaneous-demand limits.","maturity":"provisional","instantiates_archetypes":["black_swan_preparedness"],"selection_constraints":["strengthen general surprise capacity rather than predict one event","protect critical functions and vulnerable groups","retain authority limits, traceability, and recovery"],"not_an_archetype_because":"This is a concrete standard, reserve, drill, review, monitoring process, gate, or agreement used inside the broader preparedness lifecycle."} |
| Post-Shock Boundary and Rebuild Review (`post_shock_boundary_and_rebuild_review`) ↗ | Type: review Reexamines exposure, cascade, survivor bias, safeguards, and whether restoration should reproduce or redesign the prior system. Selection constraints and retained implementation evidence: strengthen general surprise capacity rather than predict one event; protect critical functions and vulnerable groups; retain authority limits, traceability, and recovery; Complete legacy mechanism record retained: {"slug":"post_shock_boundary_and_rebuild_review","name":"Post-Shock Boundary and Rebuild Review","mechanism_type":"review","role":"Reexamines exposure, cascade, survivor bias, safeguards, and whether restoration should reproduce or redesign the prior system.","maturity":"provisional","instantiates_archetypes":["black_swan_preparedness"],"selection_constraints":["strengthen general surprise capacity rather than predict one event","protect critical functions and vulnerable groups","retain authority limits, traceability, and recovery"],"not_an_archetype_because":"This is a concrete standard, reserve, drill, review, monitoring process, gate, or agreement used inside the broader preparedness lifecycle."} |
- Common-Mode Dependency Red Team
- Emergency-Authority Activation and Sunset Gate
- Minimum Viable Service Floor
- Modular Isolation and Firebreak Drill
- Mutual-Aid and Substitution Agreement
- No-Script Adaptive Response Exercise
- Post-Shock Boundary and Rebuild Review
- Protected Contingency Reserve
- Reverse Stress and Failure-Budget Test
- Sentinel Anomaly and Near-Miss Register
Parameter / Tuning Dimensions¶
- Survival floor: The minimum services, rights, people, and assets protected.
- Shock horizon: How long the system must operate before external support or recovery.
- Reserve depth: Protected capacity relative to demand uncertainty and replenishment time.
- Modularity: How much failure can be isolated without destroying essential exchange.
- Dependency diversity: The degree of independence across suppliers, platforms, geography, models, and authorities.
- Option portfolio: The number, quality, reversibility, and carrying cost of alternative paths.
- Authority decentralization: How much local action is predelegated and within which boundaries.
- Escalation sensitivity: Evidence needed to release reserves or exceptional authority.
- Emergency-power lifetime: Expiry, renewal, review, and restoration constraints.
- Sentinel breadth: Coverage of boundaries, local knowledge, anomalies, and near misses.
- Mutual-aid capacity: Real assistance available under simultaneous demand.
- Recovery objective: Return, temporary continuity, transformation, or retirement.
- Equity floor: Minimum protection and access for high-risk or low-power groups.
- Learning breadth: How strongly lessons generalize beyond the last event.
- Exercise ambiguity: How much scenario information is withheld to test improvisation.
- Rebuild threshold: Evidence required before restoring prior concentrated structures.
These parameters interact. Greater modularity can reduce pooling benefits; more local authority can speed response but require stronger safeguards; deeper reserves can be raided by routine demand; tighter triggers can delay action; broader sentinel networks can create warning fatigue. Tune for survival and legitimate adaptation, not maximum control.
Invariants to Preserve¶
- Critical survival floors and protected populations remain explicit.
- Model limits and unknown dependencies remain visible.
- Reserves are real, accessible, protected, and replenishable.
- Redundancy is tested for common-mode dependence.
- Failure blast radius remains bounded.
- Options and exit paths remain usable before irreversible commitment.
- Local actors retain bounded agency, communication, and support.
- Emergency authority is triggered, logged, reviewed, appealable, and temporary.
- Recovery does not silently recreate the same exposure.
- Learning preserves uncertainty and avoids hindsight overfit.
Preparedness must preserve legitimacy as well as function. A system that survives technically by abandoning rights, vulnerable groups, or ordinary accountability has failed an essential invariant.
Target Outcomes¶
- critical function survives forecast failure
- smaller and more isolatable blast radius
- genuine diversity and lower common-mode risk
- protected capacity under sudden demand
- faster bounded action despite missing scripts
- effective substitution and mutual aid
- legitimate triage and temporary emergency authority
- adaptive recovery instead of fragile restoration
- general lessons without last-event fixation
- lower irreversible exposure to unknown event classes
Success is not proof that every shock was anticipated. It is evidence that surprise produces bounded degradation, preserved agency, legitimate decisions, and recoverable systems rather than catastrophic cascade.
Tradeoffs¶
- Efficiency versus slack: the balance depends on irreversible consequence, model confidence, response latency, reserve carrying cost, and the rights affected by failure or intervention.
- Prediction investment versus general capacity: the balance depends on irreversible consequence, model confidence, response latency, reserve carrying cost, and the rights affected by failure or intervention.
- Central coordination versus local agency: the balance depends on irreversible consequence, model confidence, response latency, reserve carrying cost, and the rights affected by failure or intervention.
- Standardization versus diversity: the balance depends on irreversible consequence, model confidence, response latency, reserve carrying cost, and the rights affected by failure or intervention.
- Integration versus modularity: the balance depends on irreversible consequence, model confidence, response latency, reserve carrying cost, and the rights affected by failure or intervention.
- Reserve availability versus routine utilization: the balance depends on irreversible consequence, model confidence, response latency, reserve carrying cost, and the rights affected by failure or intervention.
- Rapid emergency action versus procedural safeguards: the balance depends on irreversible consequence, model confidence, response latency, reserve carrying cost, and the rights affected by failure or intervention.
- Recovery speed versus adaptive redesign: the balance depends on irreversible consequence, model confidence, response latency, reserve carrying cost, and the rights affected by failure or intervention.
- Information sensitivity versus warning fatigue: the balance depends on irreversible consequence, model confidence, response latency, reserve carrying cost, and the rights affected by failure or intervention.
- Option carrying cost versus irreversible exposure: the balance depends on irreversible consequence, model confidence, response latency, reserve carrying cost, and the rights affected by failure or intervention.
Preparedness costs are distributed. Redundancy, reserves, and insurance can raise prices; emergency exercises consume time; modularity can reduce scale efficiency. Those burdens should be compared with who bears catastrophic loss, not only with aggregate expected value.
Failure Modes¶
Scenario Capture¶
Cause. Preparedness optimizes for a vivid named scenario and remains fragile to different surprise.
Mitigation. Prioritize general capacities, reverse stress, and no-script exercises. Re-test critical function, equity, authority, and recovery after remediation.
Probability False Precision¶
Cause. Unreliable tail probabilities are treated as decision-grade certainty.
Mitigation. Use consequence thresholds, ranges, model humility, and survival requirements. Re-test critical function, equity, authority, and recovery after remediation.
Reserve Raiding¶
Cause. Slack and reserves are consumed by routine efficiency pressure.
Mitigation. Protect purpose, access authority, replenishment, and audit. Re-test critical function, equity, authority, and recovery after remediation.
Correlated Redundancy¶
Cause. Backups share the same supplier, platform, location, model, or governance failure.
Mitigation. Map dependencies and require meaningful diversity. Re-test critical function, equity, authority, and recovery after remediation.
Brittle Emergency Script¶
Cause. Detailed plans fail when event structure differs from rehearsal.
Mitigation. Train objectives, boundaries, agency, communication, and improvisation. Re-test critical function, equity, authority, and recovery after remediation.
Central Authority Bottleneck¶
Cause. Local actors wait for decisions from a center that lacks information or connectivity.
Mitigation. Predelegate bounded authority and resources with escalation paths. Re-test critical function, equity, authority, and recovery after remediation.
Permanent Emergency Power¶
Cause. Exceptional authority survives after the trigger or becomes a vehicle for abuse.
Mitigation. Use activation evidence, expiry, independent review, appeal, and restoration. Re-test critical function, equity, authority, and recovery after remediation.
Inequitable Survival Floor¶
Cause. Aggregate continuity is preserved by abandoning vulnerable or low-power groups.
Mitigation. Define rights and minimum service by affected population, not only totals. Re-test critical function, equity, authority, and recovery after remediation.
Recovery To Fragile Baseline¶
Cause. Restoration recreates the same concentration and cascade pathways.
Mitigation. Require boundary review and adaptive rebuild decisions. Re-test critical function, equity, authority, and recovery after remediation.
Hindsight Overfit¶
Cause. One surprising event is retold as obvious and becomes the template for all preparation.
Mitigation. Preserve uncertainty, rival explanations, and general structural lessons. Re-test critical function, equity, authority, and recovery after remediation.
Warning Fatigue¶
Cause. Weak signals and anomaly monitoring generate noise until real escalation is ignored.
Mitigation. Tier evidence, diversify sentinels, calibrate escalation, and retire low-value signals. Re-test critical function, equity, authority, and recovery after remediation.
Preparedness Theater¶
Cause. Plans, drills, and dashboards exist but reserves, handoffs, authority, and recovery are untested.
Mitigation. Test failure, release, substitution, withdrawal, and restoration end to end. Re-test critical function, equity, authority, and recovery after remediation.
Neighbor Distinctions¶
tail_risk_preservation¶
Protects important rare cases from common-case optimization; black-swan preparedness protects whole-system survival and adaptive response to unmodeled high-impact events.
risk_pooling_reinsurance_layering_strategy¶
Transfers quantifiable correlated or tail financial layers; preparedness also addresses nontransferable technical, institutional, ecological, and legitimacy shocks.
correlation_structure_analysis_for_pooling_effectiveness¶
Analyzes pooling dependence; common-mode review is one evidence component inside broader preparedness.
deviant_case_analysis¶
Uses an observed anomaly to refine theory; preparedness acts before, during, and after surprise to preserve function.
scenario_portfolio_planning¶
Explores named plausible futures; preparedness builds capacities that survive failure of the scenario set.
weak_signal_triage¶
Prioritizes emerging signals; sentinel monitoring is one input and does not replace reserves, modularity, authority, recovery, or safeguards.
robust_solution_selection¶
Chooses options performing acceptably across modeled conditions; preparedness also governs unknown model failure and emergency response architecture.
antifragile_experimentation¶
If present, seeks gains from volatility through bounded experiments; preparedness first protects survival and rights.
graceful_degradation¶
Maintains reduced service under failure; it is one system behavior within a larger surprise lifecycle.
fault_tolerant_distributed_consensus¶
Maintains agreement under bounded fault models; preparedness addresses failure beyond trusted models and across broader functions.
business_continuity_design¶
If present, restores named business functions; preparedness emphasizes model failure, unknown cascades, local improvisation, and adaptive rebuild.
crisis_response_coordination¶
Coordinates an active crisis; preparedness also restructures exposure and capacity before shock and learning after it.
The strongest frozen boundary is Tail-Risk Preservation. Its legacy source prime black_swan should normalize to canonical q44, but its intervention protects important rare cases from common-case optimization. Black-Swan Preparedness instead reorganizes whole-system survival, response, and recovery under deep surprise.
Cross-Domain Examples¶
Infrastructure¶
A utility defines minimum service, isolates network sections, preserves manual modes, stocks repair capacity, and tests cross-region mutual aid. Survival floor, blast radius, reserve, local agency, and staged recovery interact. The design documents survival floor, model limits, common modes, reserves, authority, equity, and recovery evidence.
Finance¶
A fund reverse-stresses liquidity, common counterparties, margin calls, and correlated exits while preserving capital and operational options. Tail dependence, concentration, reserve, optionality, and governance dominate. The design documents survival floor, model limits, common modes, reserves, authority, equity, and recovery evidence.
Public Health¶
A region preserves surveillance, local authority, reserve supplies, interoperable staffing, and rights safeguards for an unmodeled outbreak. Sentinels, capacity, improvisation, mutual aid, legitimacy, and adaptive learning are required. The design documents survival floor, model limits, common modes, reserves, authority, equity, and recovery evidence.
Digital Systems¶
A platform limits tenant blast radius, diversifies critical dependencies, tests control-plane loss, and preserves independent recovery paths. Common mode, modularity, redundancy, local control, and evidence-bearing recovery matter. The design documents survival floor, model limits, common modes, reserves, authority, equity, and recovery evidence.
Community And Governance¶
A community builds trusted local response cells, accessible reserves, communication substitutes, fair triage, and emergency-power sunset. Central scripts may fail while legitimacy and local agency determine survival. The design documents survival floor, model limits, common modes, reserves, authority, equity, and recovery evidence.
Extended regional-water example¶
A regional water system begins with a survival floor for drinking, sanitation, fire response, and medically vulnerable users. It maps concentrated treatment dependencies, shared power and communications, irreversible contamination paths, and common-mode suppliers. Protected reserves, manual operating modes, modular isolation, alternate treatment, and cross-region mutual aid are tested through a no-script exercise in which the initiating event is withheld. Local operators receive bounded authority to isolate and substitute; central authority releases reserves and coordinates public information under logged emergency rules. Recovery preserves evidence, restores minimum service first, reviews equity and rights effects, and decides which dependencies must be redesigned rather than simply rebuilt.
Across domains, the event differs but the intervention is stable: reduce catastrophic exposure, preserve options and capacity, enable legitimate adaptation, and learn without rebuilding fragility.
Non-Examples¶
- Assigning exact probabilities to every unknown unknown
- Buying one insurance policy and calling the system prepared
- Protecting rare users from common-case optimization only
- Explaining an anomaly after it occurs
- Maintaining unused reserves with no release or replenishment rule
- Running a scripted drill whose scenario and answers are known in advance
An unlikely event is not automatically a black swan, and a risk register is not automatically preparedness. The archetype requires consequence-first architecture, tested adaptive capacity, bounded authority, equitable survival, and recovery.
Related Abstractions¶
Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.
Built directly on (1)
- Black Swan (High-Impact, Low-Probability Events): High-impact unexpected events.
Also references 24 related abstractions
- Adaptation: Systems adjust to conditions.
- Antifragility: A system that gains capability from stressors and volatility, not merely withstands them.
- Buffering: A maintained intermediate capacity that absorbs excess and releases it during shortfall, smoothing variation and decoupling a source from a consumer whose rates do not match.
- Equity: Context-sensitive fairness.
- Fault Tolerance: Continue operating under failure.
- Foresight: Disciplined anticipation of plural possible futures to keep present action adaptive across the range of plausible outcomes.
- Future Wheel: Map cascading consequences.
- Heavy-Tailed Distributions: Distributions where rare, extreme events carry most of the weight.
- Margin of Safety: Buffer capacity.
- Modularity: Breaks systems into smaller units.
Variants¶
Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.
Infrastructure Surprise Preparedness · domain variant · recognized
Protect critical physical or digital services against unmodeled disruptions through isolation, manual modes, reserve capacity, and staged recovery.
- Distinct from parent: The parent also covers financial, institutional, ecological, and social surprise.
- Use when: service interruption has cascading harm; infrastructure dependencies are concentrated; manual or alternate modes are possible.
- Typical domains: energy, water, communications, cloud services
- Common mechanisms: minimum viable service floor, modular isolation and firebreak drill
Financial and Capacity Tail-Shock Preparedness · risk or failure variant · recognized
Preserve solvency and operational capacity through heavy-tail, correlated, liquidity, and counterparty shocks that exceed ordinary variance assumptions.
- Distinct from parent: The parent is not limited to quantifiable financial loss or transferable risk.
- Use when: loss distributions are heavy-tailed; correlation rises under stress; liquidity or capacity failure cascades.
- Typical domains: finance, insurance, supply chain, public budgeting
- Common mechanisms: reverse stress and failure budget test, protected contingency reserve
Institutional Legitimacy-Shock Preparedness · governance variant · recognized
Maintain legitimate decision, communication, rights, and accountability when surprise overwhelms ordinary governance arrangements.
- Distinct from parent: Other settings may be governed mainly by technical or capacity controls.
- Use when: emergency powers may be invoked; trust is a critical response resource; resource triage affects rights and vulnerable groups.
- Typical domains: public governance, health emergency, organizational crisis, community response
- Common mechanisms: emergency authority activation and sunset gate, no script adaptive response exercise
Ecological and Sociotechnical Cascade Preparedness · scale variant · recognized
Prepare for shocks whose impacts cross ecological, technical, organizational, and social boundaries through coupled cascades.
- Distinct from parent: Some shocks remain bounded within one organization or system.
- Use when: dependencies cross sectors; feedback changes behavior and exposure; no single authority controls the cascade.
- Typical domains: climate adaptation, public health, food systems, regional infrastructure
- Common mechanisms: sentinel anomaly and near miss register, mutual aid and substitution agreement, post shock boundary and rebuild review
Near names: Extreme-Event Preparedness, Unknown-Unknown Resilience, Tail-Shock Preparedness.