Post-Seal Displacement Check¶
A diagnostic check — instantiates Leakage Path Containment and Recapture
After a leak is sealed, verifies that total loss actually fell rather than merely relocating to the next-easiest path.
Sealing a leak feels like a win, but the pressure that drove the leak does not vanish when one path closes — it looks for the next opening. Post-Seal Displacement Check is the verification that distinguishes a real reduction from a displaced one: after a path is sealed, it re-measures total loss across the whole boundary, not just at the patched spot, and asks whether the quantity stopped escaping or simply found another route. Its defining idea is that the driving gradient is conserved — close the cheapest path and flow migrates to the second-cheapest — so a leak that "disappears" locally while system-wide loss holds steady was never contained; it moved. The check exists precisely because local success is the most persuasive form of false progress.
Example¶
A city plagued by catalytic-converter thefts from one open-air commuter lot installs lighting, cameras, and serial-etching there. Thefts in that lot fall to near zero, and the intervention is declared a success. A Post-Seal Displacement Check looks wider: it compares converter-theft reports across all nearby lots and streets for the months before and after. The patched lot is down about 90%, but two unlit lots a few blocks away are up by a combined amount that nearly matches — the thieves didn't stop, they walked. This is textbook crime displacement[n1]. The check's verdict is not "the fix failed" but "the fix moved the loss; the driving pressure — easy converter resale — is untouched," which redirects effort from hardening one lot toward the gradient itself.
Because the check reasons about where the pressure re-routes, it can also report the happier case: if the surrounding area stayed flat or fell too, the reduction was real and the gradient genuinely weakened.
How it works¶
Its distinguishing move is measuring the whole system, before and after, not just the patched path:
- Establish the wider baseline. Capture total loss across every known path — not only the one about to be sealed — for a comparable period beforehand.
- Re-measure whole-boundary after the seal. Recount across all paths; a real fix lowers the system total, a displaced one merely redistributes it.
- Attribute via the gradient. Read which unsealed path absorbed the flow and why it is now the easiest exit, so the finding names the next target instead of just raising an alarm.
Tuning parameters¶
- Observation window — how long you watch after the seal. Too short and displacement hasn't appeared yet; too long and unrelated changes contaminate the comparison.
- Boundary breadth — how wide you cast the "other paths" net. Narrow misses displacement to routes you didn't think of; wide is expensive and dilutes the signal with noise.
- Attribution threshold — how much correlated rise elsewhere counts as displacement versus coincidence. Strict risks calling a moved leak "contained"; loose blames the intervention for unrelated drift.
- Gradient depth — whether you stop at "loss moved here" or push to "loss moved here because this is now the cheapest exit." Deeper analysis costs more but is what turns the check into a next-target finder.
When it helps, and when it misleads¶
Its strength is that it defeats the single most flattering illusion in leak work — the locally-vanished loss — and it reframes remediation around the gradient rather than the hole, which is the only framing under which sealing reduces total loss instead of relocating it.
It misleads when the window or the boundary is drawn too narrowly: displacement to a path you weren't watching reads as success, and the check will happily certify a fix that only moved the problem out of view. It is also vulnerable to attribution error — an external trend such as a seasonal dip or an unrelated crackdown can masquerade as either displacement or genuine reduction. And it is easily run to reassure: measuring only the patched path and reporting "leak gone" is the check performed in name while skipping its entire point. The discipline is to fix the wider baseline before sealing, and to treat a flat system-wide total after a local "win" as displacement until proven otherwise.
How it implements the components¶
Post-Seal Displacement Check fills the verification slice of the archetype — confirming that a containment action changed the total, not just the map:
displacement_check— it is the direct instantiation: the before/after, whole-boundary comparison that catches leakage relocating to a new path.escape_gradient_analysis— it reads the conserved driving gradient to explain which unsealed path absorbed the flow and why, turning a negative result into the next target.
It does not perform the sealing itself (Seal-and-Retune Patch) or size the original total loss (Mass-Balance Audit); it consumes both and judges whether the seal held.
Related¶
- Instantiates: Leakage Path Containment and Recapture — it closes the containment loop by proving a seal reduced rather than relocated the loss.
- Consumes: Seal-and-Retune Patch (the action it verifies) and a whole-boundary loss measure such as Mass-Balance Audit.
- Sibling mechanisms: Seal-and-Retune Patch · Mass-Balance Audit · Red-Team Exfiltration Probe · Side-Channel Scan · Recapture or Recall Protocol · Leakage Path Walkthrough · Anomaly or Shrinkage Alert · Leakage Budget Dashboard · Exception Log Review · Controlled Release Valve · Canary Token or Tracer Dye
Editorial Notes¶
Form Classification¶
Form family: Assessment, Review & Assurance
Rationale: Post-Seal Displacement Check operates as a bounded evaluation of existing evidence or work that produces a finding or disposition because it after a leak is sealed, verifies that total loss actually fell rather than merely relocating to the next-easiest path.
Independent corroboration: The frozen evidence defines Post-Seal Displacement Check as 'After a leak is sealed, verifies that total loss actually fell rather than merely relocating to the next-easiest path', so its operative form is Assessment, Review & Assurance.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Engineering & Design
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Testing whether sealing one leak merely moved flow to another path is a reliability and containment-engineering practice.
Related originating lineages:
- Physics — Physics supplies conservation and pressure-flow reasoning behind displacement across alternative paths.
Review resolution: Both blind reviewers agree that engineering design is the primary origin. Reconciliation resolves origin mode disagreement, encyclopedia synthesis disagreement. Formative alternate lineages are retained as physics; later breadth of use is recorded separately as domain_reach=multi_domain, while origin_mode=cross_disciplinary_synthesis describes the relationship among origin lineages.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
Displacement is not automatically failure. Moving a loss from a high-harm path to a low-harm one — or from an untraceable route to one you can meter — can be a deliberate goal, the same logic as a Controlled Release Valve. The check's job is to make the movement visible and priced, not to insist every leak vanish: a displaced loss you chose is fine, a displaced loss you mistook for a fix is not.
[n1] Crime displacement — the criminology finding that situational interventions can relocate offending (to another place, time, target, or method) rather than prevent it; its studied counterpart, diffusion of benefits, is when nearby areas improve too. The concept generalizes to any leak whose driving pressure survives the seal. ↩