Skip to content

Recusal and Firewall Protocol

Governance control — instantiates Outside-Authority Influence Channel Mapping

Once a conflict is identified, removes the conflicted party from the decision and walls the channel off from it — redrawing the boundary of who may touch the protected decision.

Where its siblings map, score, and diagnose, Recusal and Firewall Protocol is the one that acts. Once a conflict or high-risk influence route has been identified, the protocol removes the compromised party from the decision (recusal) or seals the channel off from it (a firewall, or information barrier) — and in doing so it redraws the boundary of exactly who and what may reach the protected decision. Its one distinguishing idea is that it is an intervention on structure, not an assessment: it does not find conflicts and it does not weigh them; it takes one already identified and changes the actual pattern of access so that route can no longer bend the outcome. It is the mechanism with teeth, and the only sibling that alters participation rather than describing it.

Example

A municipal planning board is voting on a mixed-use development. Disclosure has already surfaced that one board member owns a parcel adjacent to the site — a live conflict. The protocol executes. The member is recused from the vote, but recusal alone would be porous, so a firewall follows: the member is removed from the closed deliberation session, cut from the distribution list for the staff report and the applicant's financials, and barred from lobbying colleagues on the matter off the record.

Crucially, the protocol pins the scope: the firewall covers this application and this decision, not the member's unrelated board work, and it lifts when the decision is final. That precision is what keeps the wall from being either leaky (letting the member back in through a side channel) or over-broad (stripping a competent member off every unrelated vote). The outcome is a decision the conflicted member demonstrably could not shape.

How it works

  • Trigger on an identified conflict or high-risk channel — the protocol presupposes a diagnosis; it does not generate one.
  • Select the control — recuse the person, or firewall the channel or unit, or both.
  • Specify the exact scope — which decisions, which information, and for how long the barrier holds.
  • Enforce it at the level of access — attendance, document distribution, system permissions — not merely by asking nicely.
  • Document the barrier so its boundary is auditable after the fact.

The distinguishing move is that it changes the structure of access: it re-establishes and enforces the boundary of the protected decision against a specific identified route.

Tuning parameters

  • Control type — recusal of a person, or a firewall around a channel or unit. Recusal is targeted; a firewall covers a standing relationship.
  • Scope breadth — this one decision, or a standing class of them. Broader is safer but strips more capacity.
  • Duration — a one-off for a single vote, or a permanent wall. Permanence is robust but costly to legitimate expertise.
  • Porousness — a hard barrier, or a softer disclosed-contact-only regime. Harder resists leakage; softer preserves useful information flow.
  • Enforcement strength — honor system, or access-controlled and audited. Access control is what makes a wall real rather than declared.

When it helps, and when it misleads

Its strength is that it actually restores the decision owner's ability to decide free of the identified route — it converts a finding into a fact on the ground. A well-built information barrier is a proven governance instrument, used wherever one part of an organization must be sealed from another's interests.[n1]

Its central failure mode is that firewalls leak. A wall that exists in the policy binder but not in the seating chart or the email thread launders influence while advertising its absence — worse than no wall, because it confers false assurance. Recusal is gameable too: a party recused from the vote can still have shaped the agenda and the options beforehand. And an over-broad firewall strips out legitimate expertise the decision genuinely needs. The discipline that keeps it honest is to scope the wall precisely, enforce it at the level of access rather than good intentions, and audit it against the actual record — a firewall is only as real as its leakiest gap. Because it acts on a diagnosis it does not produce, walling off the wrong party protects nothing.

How it implements the components

  • formal_authority_boundary_map — the firewall re-establishes and enforces the formal boundary of who may access, deliberate on, and act within the decision, cutting the identified route out of it.
  • sovereign_decision_domain_definition — the protocol pins down the exact protected decision the wall encloses — which choices, which information, for how long — so the control is neither leaky nor over-broad.

It executes a control but does not surface or assess the conflict it acts on — that disclosure-and-check step (external_input_transparency_protocol, opacity_and_access_asymmetry_check) is the Conflict-of-Interest Disclosure Review, its nearest twin: that review diagnoses, this protocol acts. And it applies one control rather than selecting from the full menu of graded responses (proportionate_channel_response, the Influence-Response Decision Tree).

Editorial Notes

Form Classification

Form family: Structure, Architecture & Configuration

Rationale: Recusal And Firewall Protocol operates by maintains an enforced access and decision barrier around the conflicted person, channel, or unit. That concrete deployed or enacted form is Structure, Architecture & Configuration under the frozen taxonomy.

Nearest alternative: Intervention, Treatment & Transformation — Although Intervention, Treatment & Transformation can support this mechanism, the frozen evidence makes its operative form the act that maintains an enforced access and decision barrier around the conflicted person, channel, or unit; the alternative is therefore secondary rather than defining.

Review outcome: Adjudicated after independent review; high confidence.

Origin Attribution

Primary origin: Law & Governance

Origin pattern: Cross-disciplinary synthesis

Present-day reach: Multi-domain

Rationale: Removing conflicted decision-makers and separating protected matters are legal-governance controls.

Related originating lineages:

Review resolution: Both blind reviewers agree that law_governance is the primary origin. Explicit reconciliation of alternate origin disagreement, encyclopedia synthesis disagreement adopts reviewer_a's classification because removing conflicted decision-makers and separating protected matters are legal-governance controls. The resulting lineage records alternates=security_intelligence, origin_mode=cross_disciplinary_synthesis, and domain_reach=multi_domain; these describe formative provenance separately from later applicability.

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

The protocol is downstream of almost everything else: it can only act on a route the matrix, the interlock diagram, the refusal-cost test, or the disclosure review has already identified, and it usually acts on the response the Influence-Response Decision Tree selected. Deployed on its own it has nothing to wall off; deployed on the wrong finding it walls off the wrong party. Its value is entirely in being aimed well.

[n1] An information barrier — historically called a "Chinese wall" — is a governance structure that seals one part of an organization off from another's information and influence, classically between an investment bank's advisory and trading functions. Its long-known weakness is enforcement: a barrier is only as strong as the access controls behind it, which is why declared walls that are never enforced routinely fail.