Anti-Capture Rotation Protocol¶

Rotation protocol — instantiates Rent-Seeking Channel Closure

Reassigns gatekeepers and reviewers on a schedule so that no single relationship with a regulated party has time to harden into capture.

Anti-Capture Rotation Protocol closes the capture channel by keeping it moving. Capture is largely a product of tenure — the longer one examiner, buyer, or reviewer sits opposite the same counterparty, the more the relationship, the shared assumptions, and the anticipated future favours accumulate. The protocol makes prolonged pairing impossible by rotating personnel across assignments on a fixed cadence, so an official is moved on before "their" firm becomes a relationship to protect. Unlike a cooling-off period, which acts once at exit, rotation acts continuously during service; unlike an audit, which watches for capture after the fact, rotation is built so that capture never gets the standing time it needs to form.

Example¶

A banking supervisor assigns examiners to oversee individual banks. Left alone, an examiner may spend a decade on one institution — and slowly slide from independent scrutiny toward advocacy for "their" bank inside the agency, a drift nobody chooses but many drift into. The rotation protocol caps any examiner's tenure on a single bank at ≈3–4 years and reassigns on a staggered schedule, so the roster is always partly fresh and no bank ever faces the same lead examiner long enough to school them. When a supervisor's relationship-length creeps past the cap — say, a specialist quietly retained on one complex bank "because only she understands it" — that exception is itself the signal the protocol watches for, and it triggers either rotation or a documented, time-limited waiver.

How it works¶

Rotation's distinguishing logic is that it treats time-on-pairing as the risk variable and manages it directly. Assignments are scheduled so that tenure on any one counterparty is bounded and staggered across the team (never rotate everyone at once, or institutional memory collapses in a single quarter). The same tenure clock doubles as an early-warning signal: a pairing that resists rotation — the irreplaceable expert, the "we can't move her" exception — is flagged as a capture risk precisely because it is where rotation is being avoided. The protocol thus prevents and detects with one instrument: the schedule.

Tuning parameters¶

Rotation interval — short intervals sever relationships more aggressively but repeatedly discard hard-won, counterparty-specific expertise; long intervals preserve competence but let familiarity build.
Stagger pattern — how many people rotate at once. Full simultaneous rotation maximises the reset but risks losing all continuity; staggered rotation trades a slower reset for retained memory.
Scope — whole teams, lead roles only, or just the final decision-maker. Narrow rotation is cheaper but leaves the deputies who do the real work in place.
Waiver regime — how hard it is to keep a valued pairing in place. Loose waivers preserve expertise but reopen the channel; the tighter the waiver, the more the protocol bites — and the more good specialists it displaces.

When it helps, and when it misleads¶

Its strength is that it attacks capture at its root cause — elapsed relationship time — without anyone having to detect a specific act of favouritism first, and it turns the very reluctance to rotate into a visible warning. Its failure mode is the expertise cost: rotate too hard and you trade captured-but-competent oversight for independent-but-shallow oversight, and a supervisor who never learns the counterparty deeply may simply miss what a captured one would have caught. The classic misuse is the ceremonial rotation — reshuffling titles while the same people keep the same relationships, or granting a standing waiver to exactly the entrenched pairing the protocol exists to break, so the institution can claim rotation while the channel stays warm. The discipline that guards against this is to set the interval against how fast capture actually forms in the setting rather than to an administratively convenient number,^[1] and to treat every long-standing waiver as a finding, not a convenience.

How it implements the components¶

Anti-Capture Rotation Protocol fills the structural-prevention subset of the archetype's machinery:

capture_firewall — it is a firewall built out of movement: bounded, staggered tenure that stops any single official–counterparty relationship from consolidating.
capture_drift_monitor — the tenure clock is also a detector; a pairing that resists rotation is surfaced as the place capture is most likely forming.

It maps neither who is influencing whom nor whom decisions have benefited — that diagnostic belongs to Regulatory Capture Audit — and it does not bar the post-employment move on exit, which is Cooling-Off Period's job.

Instantiates: Rent-Seeking Channel Closure — rotation keeps the gatekeeper channel from setting hard.
Consumes: Regulatory Capture Audit — its drift findings can trigger an off-cycle rotation.
Sibling mechanisms: Cooling-Off Period · Regulatory Capture Audit · Auction with Rent Recapture · Beneficial Ownership and Influence Disclosure · Competitive Rebid or Retendering · Conflict-of-Interest and Recusal Rule · Sunset Clause Review · Entry-Barrier Sunset and Review · Independent Technical Evidence Panel · Performance-Based Clawback · Public Reason Docket · Randomized or Lottery Allocation · Rent-Seeking Audit · Standardized Scoring Rubric

References¶

[1] Mandatory rotation — of audit firms, engagement partners, or supervisory staff — is the established real-world form of this protocol; its perennial design tension, independence gained versus counterparty-specific expertise lost, is exactly the interval trade-off above. ↩