Skip to content

Conditional Control-Rotation Protocol

Switching protocol — instantiates Adaptive Barrier-Circumvention Response

Switches or alternates among genuinely independent controls on evidence-based triggers rather than a predictable schedule, spreading selection pressure so no single blind spot is rewarded long enough to take over.

Apply one control relentlessly and it becomes the whole selection environment — whatever survives it inherits the field. Conditional Control-Rotation Protocol manages that environment directly: it rotates, alternates, or narrows among genuinely independent controls, but only on evidence-based triggers and never on a predictable calendar, so selection pressure stays heterogeneous and no single blind spot is rewarded consistently enough to take over. Its defining move separates it from every one-shot decision in the set — it is an ongoing pressure-management rule, gated by two preconditions (verified independence of the controls, and a coverage-decay trigger) that together distinguish real rotation from rotation as ritual. The goal is not change for its own sake; it is spreading pressure across a budget so escape is never handed a stable target.

Example

An ICU antibiotic-stewardship team manages selection pressure across drug classes. Continuously favoring one class selects for resistance to it — but the intuitive fix, a fixed monthly rotation ("cycling"), is itself a predictable pattern and can create troughs where a class returns before resistance to it has faded. The protocol instead defines eligible classes that are genuinely independent in mechanism of action (a fact it takes from a common-mode check, not from the drugs' brand names), sets triggers tied to resistance signals rather than the calendar, plans overlap so no patient is left uncovered during a switch, and revalidates population-level coverage after each change.

In practice it often leans toward mixing — heterogeneous use across patients at the same time — rather than synchronized cycling, because concurrent heterogeneity spreads pressure without offering a schedule to track. Whether cycling or mixing better slows resistance is a genuinely unsettled question in stewardship; the protocol's contribution is not to declare a winner but to keep pressure diverse and evidence-triggered, always above a hard floor of adequate protection for the individual patient.

How it works

  • Define eligible controls and prove independence. Only controls shown to be meaningfully independent are rotation partners; rotating among ones that share a blind spot is cosmetic.
  • Set coverage-decay and safety triggers. Switching is driven by evidence that the in-use control is losing ground, not by a fixed schedule an adversary could anticipate.
  • Plan overlap, communication, and rollback. Old and new controls co-run across the switch so no protection gap opens, with a tested way back.
  • Revalidate population-level coverage after each change. Every rotation is followed by a check that overall protection actually held.

Tuning parameters

  • Trigger basis — evidence-based versus scheduled. Scheduled is simpler but predictable and can create resistance troughs; evidence-based is the whole point but demands good monitoring.
  • Independence bar — how strict the test that eligible controls are genuinely independent. A lax bar produces rotation that just moves pressure around the same trap.
  • Rotation vs mixing — synchronized switching versus heterogeneous concurrent use. Mixing spreads pressure without a schedule but is harder to coordinate and audit.
  • Overlap window — how long old and new controls co-run during a switch. More overlap closes gaps but costs more and can blunt the pressure relief the switch was meant to deliver.
  • Safety floor — the non-negotiable minimum protection rotation may never dip below. In safety-critical settings this is a hard invariant, not a tunable preference.

When it helps, and when it misleads

Its strength is managing the selection environment rather than merely hardening one filter: it spreads pressure so no single blind spot is consistently rewarded, and it ties change to evidence so rotation happens neither too early (needless churn) nor too late (escape already entrenched).

Its failure mode is that rotation is not automatically beneficial. A predictable schedule is a pattern an adaptive population can track, and rotating among controls that share a blind spot is cosmetic — pressure moves but the trap stays.[1] Cargo-culted, "we rotate our controls" becomes a virtue signal detached from independence or triggers, and rotating a control away before its replacement covers the gap breaches the safety floor. The discipline is the two preconditions plus overlap: evidence-triggered switching, independence-verified partners, a co-run window, and a floor that rotation may never cross.

How it implements the components

  • renewal_rotation_and_switching_rule — its core: the evidence-based conditions under which controls are rotated, alternated, narrowed, or switched as coverage decays or common-mode risk rises.
  • selection_pressure_budget — it operationalizes the budget, capping how intensely, uniformly, and continuously any one control is applied before pressure is redistributed to hold escape risk down.

It relies on independence it does not itself verify (that's Common-Mode Escape Review), does not decide a specific permanent replacement (that's Champion–Challenger Barrier Revalidation), and does not rehearse the operational cutover (that's the Safe Transition and Rollback Drill). This protocol sets when and how pressure rotates; siblings verify, replace, and rehearse.

Notes

The anti-pattern this protocol most exists to prevent is rotation as ritual. Rotating on a calendar among controls whose independence was never proven is worse than not rotating: it spends effort, offers a predictable schedule to exploit, and manufactures a false sense of resilience. The two preconditions — an evidence trigger and verified independence — are precisely what separate genuine pressure management from cargo-cult rotation.

References

[1] The antibiotic cycling-versus-mixing debate is a live, unresolved question in stewardship: scheduled cycling is itself a predictable regime, and heterogeneous "mixing" is often argued to spread selection pressure more effectively — a caution this protocol generalizes by preferring evidence-triggered switching over fixed schedules. ↩