Intervention Displacement Stress Test¶

An anticipatory test method — instantiates Migration-Resistant Hazard Control

A pre-deployment probe that grants the control its local success and asks the harder question — where would the blocked pressure go, who would absorb it, and how long until it surfaces — before you commit.

Intervention Displacement Stress Test is the before-you-deploy probe of the archetype. Its defining move is counterfactual and anticipatory: it stipulates that the control will work locally — grants it the win — and spends all its effort forecasting the displacement that success would cause. It answers three questions a naïve pilot never asks: if this barrier holds, along what paths does the residual pressure re-express itself, which destinations are soft enough to absorb it, and how long is the lag before the transfer becomes visible? It is a planning projection, not a live adversarial exercise — it maps the field of where a hazard could migrate so the decision to deploy is made with the displacement already in view, rather than discovered a quarter later at someone else's site.

Example¶

A payments company plans to block a card-testing attack channel that has been probing stolen card numbers. Before shipping the block, a displacement stress test asks where the pressure goes if it works. It builds a migration-field model of the adversary's alternatives — rerouting to account-takeover attempts and gift-card cash-out — and a destination-vulnerability map ranking those routes by softness, which flags a downstream partner whose velocity checks are weaker as the likeliest landing spot. It then estimates the migration lag window: displacement would take roughly a few weeks to surface in chargeback data, well after the block's local success would be declared. The verdict is not "don't ship" but "ship the block, pre-harden the partner, and place a watch on the two predicted routes for the next two months" — deploying with the balloon-effect already anticipated rather than absorbed by a surprised third party.^[1]

How it works¶

Hold the local win fixed. Assume the control succeeds where it is aimed; the test is not about whether it works but about what its working displaces.
Model the migration field. Lay out the paths the residual pressure can take — other actors, channels, phases, populations — rather than a single expected reroute.
Rank destinations by softness. Score candidate landing sites by how weak their controls and measurement are, since pressure flows to where resistance and detection are lowest.
Estimate the lag. Put a horizon on how long displacement takes to become visible, so a "success" reported inside that window is not mistaken for elimination.

Tuning parameters¶

Adversariality — how creatively displacement paths are hypothesized; too tame and the real reroute is never on the list.
Field breadth — how many kinds of destination (actor, channel, phase, population) are considered before the model is called complete.
Lag horizon — how far out displacement is projected before a "no displacement" conclusion is allowed; a short horizon hides slow transfers.
Vulnerability weighting — how strongly soft, weakly-measured sites are favored as predicted destinations over merely adjacent ones.
Evidence base — how much the forecast leans on analogs from past interventions versus pure modeling, and how that mix is disclosed.

When it helps, and when it misleads¶

Its strength is that it turns "we'll find out" into a testable displacement hypothesis before commitment, and by sizing the lag it stops a within-window "success" from being read as a genuine reduction. It is the mechanism that lets a team deploy a barrier and pre-position protection at the destination in the same decision.

Its weakness is inherent to forecasting: it is only as good as the paths it imagined, and an unimagined route is a false all-clear. Because it deals in projected destinations, it risks tipping into the neighboring work of hardening weak points as an end in itself — but here the destination map exists to anticipate displacement, not to catalog hotspots to fortify. Its classic misuse is to run backwards: a light-touch stress test staged to bless a decision already made, or a lag horizon set short so the displacement falls out of frame. The discipline is to pair every forecast with a live Migration Sentinel Network that checks it against reality, and to treat the unimagined path — not the modeled one — as the main risk.

How it implements the components¶

Intervention Displacement Stress Test realizes the anticipatory forecasting side of the archetype — projecting the migration before it happens:

migration_field_model — the projected field of paths the residual pressure could take if the control holds.
destination_vulnerability_map — the ranked map of candidate landing sites by how softly-controlled and weakly-measured they are.
migration_lag_window — the estimated delay before displacement surfaces, which sets how long a claimed success must be held provisional.

It does not watch for the migration live (that's Migration Sentinel Network) or reduce the pressure at its source (that's Source-Reduction or Safe-Dissipation Plan); it forecasts so those can be aimed and timed.

Instantiates: Migration-Resistant Hazard Control — it supplies the pre-deployment displacement forecast the appraisal depends on.
Consumes: a generative model of how the hazard is produced (e.g., Causal Loop Diagram or Whole-System Impact Map) to seed the field of paths.
Sibling mechanisms: Migration Sentinel Network · Boundary Expansion Review · Cross-Boundary Hazard Ledger · Cross-Jurisdiction Incident Review · Pressure-Absorption Redesign Workshop · Source-Reduction or Safe-Dissipation Plan · Whole-System Impact Map · System-Wide Net-Risk Dashboard · Before–After–Elsewhere Evaluation · Adaptive Circumvention Red Team · Causal Loop Diagram · Agent-Based Experiment or Simulation · Fault Tree Analysis · Mass Balance · Hazard Analysis

References¶

[1] Balloon effect — squeeze a hazard in one place and it bulges out in another, the way pressing one part of a balloon pushes air elsewhere. Named from drug-enforcement experience, it is the exact phenomenon this stress test tries to forecast before, rather than after, the squeeze. ↩