Crisis Scenario Catalog¶
Reference artifact — instantiates Wild-Card Contingency Mapping
Maintains a curated, plausibility-screened library of low-probability/high-impact event classes, so the whole set of what could go wrong can be seen and reasoned about at once.
The Crisis Scenario Catalog is the standing library of wild-card event classes a system has decided are worth taking seriously — each one named, described at a workable grain, and kept or cut by an explicit plausibility screen. Its distinguishing job is breadth held in one place: not tracing any single disruption in depth, nor holding the responses, but making the whole portfolio of imaginable shocks visible so gaps and clusters show up. A catalog entry is a short, disciplined card — "sudden multi-day port closure," "regional undersea-cable cut," "insider sabotage of the control system" — pitched specifically enough to reason about yet broadly enough that preparedness never hinges on predicting the exact trigger. Where a routine risk register drifts toward the familiar and comfortable, the catalog's whole value is that it deliberately keeps the uncomfortable, easy-to-dismiss entries on the page.
Example¶
A mid-size coastal city's emergency-management office has solid plans for the hazards it faces yearly — hurricanes, flooding — but keeps being blindsided by everything else. It builds a Crisis Scenario Catalog to hold the rest. Entries accumulate from horizon scanning, staff workshops, and peer cities: ransomware locking the water utility's control system, a chemical release from the rail line that bisects downtown, sudden collapse of the region's only fuel-import terminal, a heat dome running weeks past anything on record. Each is written as a class, not a prophecy — "control-system ransomware at the water plant," not "the water plant is hit on a Tuesday in March."
The discipline is the plausibility screen. A proposed entry — "coordinated drone swarm closing the airport" — is kept only if someone can say why it could happen and point to a real analogue or constraint; "an asteroid strike downtown" is logged as out of scope and cut. The payoff isn't any single entry but the view across them: laid side by side, the catalog reveals that four unrelated scenarios all route through the same single fuel terminal — which reframes where the city's next preparedness dollar should go.
How it works¶
- Enumerate as classes. Each entry names an event class at the grain where reasoning is possible without prediction; too-narrow entries are widened, too-vague ones split.
- Screen at the plausibility boundary. Every candidate must clear "why could this happen, and what supports it?" — entries with no mechanism or analogue are cut, so the catalog resists both normalcy bias (dismissing the uncomfortable) and fantasy planning (hoarding the absurd).
- Organize for cross-reading. Entries are grouped and tagged so shared exposures, common precursors, and clusters surface — the catalog's real output is the pattern across entries, not any one card.
- Curate over time. Entries are added, merged, retired, or re-scoped as the world changes; the catalog is a maintained collection, not a one-off brainstorm dump.
Tuning parameters¶
- Grain of an event class — how specific each entry is. Finer entries reason more concretely but multiply and drift toward prediction-dependence; coarser entries stay robust but vague.
- Plausibility bar height — how much supporting mechanism or analogue an entry must show to be retained. A high bar keeps the catalog credible but can quietly re-admit normalcy bias by excluding the genuinely unprecedented; a low bar invites fantasy.
- Breadth vs. depth — how many classes to carry. A wide catalog surfaces more blind spots but spreads attention thin; a narrow one goes deep but re-creates the tunnel vision it exists to break.
- Sourcing mix — how much to draw from horizon scanning, internal workshops, peer analogues, and near-miss history.
- Refresh trigger — calendar cadence versus event-driven revisits after a near-miss or a peer's shock.
When it helps, and when it misleads¶
Its strength is making the set of shocks visible and comparable, so blind spots and shared choke points surface that no single-scenario plan would reveal — and so uncomfortable possibilities get a durable place on the page instead of being talked out of the room.
Its central failure mode is the catalog that becomes a museum: entries accumulate, nobody screens or connects them, and it decays into a list of scary labels that reassures without changing any decision. It also skews toward the imaginable — vivid, recent, media-salient scenarios crowd out the dull-but-deadly, a live instance of normalcy bias working at the level of the whole list.[n1] And a catalog can be quietly gamed: padded with exotica to look thorough while the plausible, politically awkward entry stays off the page. The discipline that guards against all three is the plausibility screen applied honestly in both directions — cutting the absurd and forcing in the uncomfortable — plus a standing rule that entries with no downstream use get retired.
How it implements the components¶
The Crisis Scenario Catalog fills the inventory side of the archetype — naming and screening what belongs in scope, nothing downstream of that:
wild_card_event_class— each catalog entry is a named event class, pitched at a grain that supports reasoning without exact prediction.plausibility_boundary— the retention screen is that boundary made operational: an entry stays only if it clears "why could this happen?", which is what keeps the collection between normalcy bias and fantasy.
It does not trace how any class propagates or what it exposes — that is Contingency Map; it holds no response moves — those live in the Contingency Option Register; and it does not watch for early warnings — that is the Precursor Watchlist.
Related¶
- Instantiates: Wild-Card Contingency Mapping — the catalog supplies the event classes the rest of the archetype maps, prepares for, and reviews.
- Consumes: Wild-Card Workshop — the workshop's generated and challenged event classes are what the catalog curates into a standing library.
- Sibling mechanisms: Contingency Map · Contingency Option Register · Strategic Reserve Plan · Red-Team Disruption Challenge · Precursor Watchlist · Disruption Playbook · Tabletop Exercise · Readiness Drill · Wild-Card Workshop
Editorial Notes¶
Form Classification¶
Form family: Representation, Specification & Plan
Rationale: Crisis Scenario Catalog operates as a non-executable information artifact that externalizes static or prospective structure because it maintains a curated, plausibility-screened library of low-probability/high-impact event classes, so the whole set of what could go wrong can be seen and reasoned about at once.
Independent corroboration: The frozen evidence defines Crisis Scenario Catalog as 'Maintains a curated, plausibility-screened library of low-probability/high-impact event classes, so the whole set of what could go wrong can be seen and reasoned about at once', so its operative form is Representation, Specification & Plan.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Futurism & Strategic Foresight
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Strategic foresight cohered curated wild-card and low-probability/high-impact scenario portfolios; crisis catalogs combine that plausibility discipline with all-hazards planning and intelligence threat assessment.
Related originating lineages:
- Disaster Management & Risk Reduction — Hazard planning supplies all-hazards scenario libraries at a grain usable for preparedness.
- Security Studies & Intelligence Analysis — Threat assessment supplies curation of uncomfortable adversarial shocks often omitted from routine risk registers.
Review resolution: Foresight supplies the portfolio-wide scenario method and explicit plausibility boundary, while FEMA's THIRA process demonstrates its institutionalization in emergency planning.
Review outcome: Researched adjudication after independent review; high confidence.
Sources consulted:
Notes¶
The catalog is an input inventory, not preparedness itself. A thick, well-organized catalog can create a dangerous illusion of readiness when nothing downstream — pathways, options, reserves — has actually been built. Its job ends at "here is what we take seriously"; everything after that belongs to its siblings.
[n1] Normalcy bias — the tendency to underestimate the likelihood or impact of a disruption because it lies outside ordinary experience, so warning signs get rationalized as normal. A crisis scenario catalog exists partly to counteract it by giving low-probability classes a standing, legitimate place on the page. ↩