Skip to content

Route Closure with Alternative

Intervention protocol — instantiates Revealed-Use Path Alignment

Blocks a revealed path that has been judged genuinely harmful while standing up a legitimate route that serves the same underlying need — so the need isn't punished along with the path.

Sometimes the trace is a true signal but the path itself cannot stand — it is unsafe, unlawful, or corrosive. Route Closure with Alternative is the change you make in exactly that case. It does two things as one inseparable move: it closes the harmful route and opens a sanctioned route that serves the underlying need the trace revealed. Its defining principle is the coupling — closure without a substitute merely drives the workaround somewhere less visible and often more dangerous, so the alternative is not a courtesy but the thing that makes the closure hold. It enacts one branch of the accommodation decision — block-and-reroute — the deliberate opposite of paving the path as it stands.

Example

At a company, staff routinely move large client files through a personal consumer file-sharing app because the sanctioned email system caps attachments at a few megabytes. It works, and it is a real data-security and compliance exposure — client data sitting in unmanaged personal accounts. The naïve response is to block the app at the firewall. But a bare block sends people to the next unmonitored tool; the need doesn't vanish, it just hides better. Route Closure with Alternative pairs the block with a sanctioned secure-transfer service that genuinely meets the need — large files, easy external sharing, one-click migration of in-flight transfers. The sequence matters: the sanctioned service goes live first, staff are shown how it maps onto what they were already doing, and only then is the risky app disabled. Because the underlying need is now served better than before, the block sticks instead of spawning a fresh workaround.

How it works

What distinguishes this protocol from a plain prohibition is that block and substitute are a single, sequenced move aimed at the need, not the behavior:

  • Name the need, not the shortcut. The target is the underlying requirement the trace exposed ("send big files easily"), not the specific tool people reached for.
  • Provision before you prohibit. The legitimate alternative is live before, or exactly as, the old route closes — never after.
  • Update the formal system on both sides. The change is real and paired: the sanctioned route is added and the harmful one is actually shut, with the reason explained.

The load-bearing discipline is simple and absolute: never close without a live, adequate substitute in hand.

Tuning parameters

  • Closure hardness — a hard technical block versus friction or gradual deprecation. A hard stop ends the harm fast but backfires if the alternative is weak.
  • Sequencing overlap — how long the alternative runs before the old route shuts. Too short and people fall back; too long and the harm persists.
  • Alternative fidelity — how fully the substitute meets the original need. A visibly worse alternative guarantees a new workaround somewhere else.
  • Explanation — how the closure and its reason are communicated. An unexplained block reads as punishment and breeds evasion; a reasoned one buys cooperation.
  • Enforcement stance — whether the old route is made technically impossible or merely discouraged, and how tightly that is policed.

When it helps, and when it misleads

Its strength is that it is the honest answer when a desire path is real but dangerous: it honors the need while refusing the harm, and by provisioning a genuine substitute it escapes the whack-a-mole that pure prohibition sets off.[1] Done well, it converts an adversarial cat-and-mouse into a supported migration.

Its failure modes almost all come from dropping the second half. Teams block and skip the alternative — relocating the workaround somewhere less visible and worse. Or the substitute is nominal, under-built, and slower than what it replaced, so people quietly route around it too. Or closure is wielded punitively against users who were, in fact, signaling a real gap. The classic misuse is to close now, promise the alternative "soon," and never ship it. The discipline is to gate the closure on a live, adequate substitute and to watch for displacement once it lands.

How it implements the components

Route Closure with Alternative realizes the decision-and-change side of the archetype's machinery — the block-branch, enacted:

  • accommodation_decision_rule — it is the block-and-reroute branch of the decision: honor the underlying need, refuse the exact path.
  • official_path_update — the sanctioned substitute plus the shutting of the old route is a concrete, paired change to the formal system.

It does not judge whether the path is harmful in the first place — that verdict comes from Safety and Accessibility Review — and it does not legitimize the revealed path unchanged; paving the path as-is is Informal Route Legalization Patch, the opposite branch of the same decision.

Notes

Closure is not self-verifying. Pair it with Trace Decay Review: confirm the old route actually falls out of use and that no worse trace pops up elsewhere. A closure nobody monitors can fail silently — the risky behavior simply migrates to a channel no one is watching.

References

[1] Shadow IT — the unsanctioned tools and services employees adopt to get their work done when the official ones fall short. It is the standing evidence that prohibition without an adequate sanctioned substitute does not remove a need; it only pushes the workaround further out of view. ↩