Skip to content

Inhibitor and Poison Screen

Screening audit — instantiates Catalytic Pathway Enablement

Tests incoming cases and operating conditions for the contaminants, conflicts, and incompatibilities that would suppress or corrupt the facilitator — catching them before they reach it.

A facilitator's capacity can collapse abruptly while the facilitator still looks perfectly present — a poisoned catalyst, a conflicted mediator, an overloaded expert. Inhibitor and Poison Screen is the input-side gate that looks for exactly that: it tests incoming substrate and operating conditions for the agents that occupy, deactivate, or distort the facilitator, and classifies what it finds as reversible inhibition (lift the cause and activity returns) or irreversible poisoning (the active site is gone for good). Its distinguishing job is that it guards the facilitator against corruption from what flows into it, not against being merely busy and not against producing the wrong output — it is a contamination check on inputs and conditions, run before damage is done.

Example

A clinical reference lab runs a high-throughput immunoassay analyzer — the facilitator that transforms thousands of blood samples a day into reportable results. Two things can quietly poison it. A single sample can be hemolyzed or lipemic, containing interfering substances that skew the reaction; and a reagent lot can arrive degraded or contaminated, corrupting every result it touches. The screen sits ahead of the analyzer: each sample is checked for hemolysis and known interferents, each reagent lot is verified before it goes into service. A flagged sample is quarantined rather than run; a suspect lot is pulled.

The screen also classifies what it catches. A clogged sample probe is reversible — clean it, and the line recovers. A cross-contaminated reagent lot is an irreversible poison — no amount of rinsing restores the runs it touched, so the discipline is to discard and re-test. Getting that distinction right is the difference between a five-minute pause and a day of retractions, because the poison's damage is not to a single result but to trust in the entire line's output.

How it works

  • Screen inputs, not outputs. The check runs on incoming substrate and operating conditions — before the facilitator acts — so a contaminant is caught upstream rather than diagnosed in a corrupted result.
  • Classify reversible vs. irreversible. Each hit is sorted into inhibition that lifts when the cause is removed versus poisoning that permanently deactivates capacity, because the two demand opposite responses.
  • Gate admission. Cases and conditions that fail the screen are quarantined, rerouted, or held, so the facilitator only ever meets substrate it can safely act on.

Tuning parameters

  • Sensitivity vs. specificity — how aggressively the screen flags. Catching more true poisons also rejects more clean cases; the balance sets how much good substrate you starve the facilitator of to keep it safe.
  • Contaminant coverage — which poisons, conflicts, and conditions are actually tested for. A screen only catches what it is designed to look for; widening coverage costs time and complexity.
  • Reversible/irreversible threshold — where the line is drawn between "clean and retry" and "discard." Set it wrong and you either throw away recoverable capacity or trust poisoned output.
  • Screen placement — pre-admission gate versus inline sampling. Earlier catches more before harm; inline catches poisons that only emerge during operation.
  • Escalation on detection — whether a hit pauses one case or trips a broader stop; how a suspected systemic poison escalates.

When it helps, and when it misleads

Its strength is catching silent killers: because catalytic capacity can fail sharply while the facilitator appears intact, a screen that inspects inputs prevents a whole run of corrupted output and the loss of trust that follows — far cheaper than diagnosing the poisoning after the fact.

Its limits are the mirror of that. A screen catches only the poisons it was built to test for, so a novel contaminant passes clean; and an over-tight screen commits the opposite error, rejecting legitimate substrate and starving the facilitator of work (false poisons). The classic misuse is pretextual screening — running the check to manufacture grounds for a rejection already decided on, dressing exclusion as safety. The discipline is to validate the screen against known poisons, audit its false-reject rate, and keep the criteria public so "contaminated" cannot quietly mean "unwanted."[1]

How it implements the components

Inhibitor and Poison Screen fills the contamination-detection side of the archetype — protecting the facilitator's integrity from corrupting inputs — and nothing beyond it:

  • inhibitor_or_poison_monitor — its core: detecting the agents, contaminants, conflicts, and conditions that suppress or distort the facilitator, and distinguishing reversible inhibition from cumulative poisoning.
  • compatibility_check — the per-case test of whether an incoming substrate, reagent, or condition is compatible with the facilitator or would corrupt it, used to admit or quarantine.

It only detects; it does not restore a poisoned facilitator (that is Catalyst Regeneration Protocol), decide when to retire it (a deactivation rule owned by the steward), or measure its throughput and selectivity (that is Turnover and Selectivity Assay).

Notes

Detection and response are deliberately separate. The screen finds a poison; restoring the facilitator afterward is Catalyst Regeneration Protocol's work, and the decision to pull it from service is a deactivation rule the Accountable Catalyst Steward owns. Keeping them apart is what lets a lab tune its screen's sensitivity without also re-litigating its recovery and retirement policy.

References

[1] Reversible vs. irreversible inhibition — from enzyme kinetics: a reversible inhibitor's effect lifts once it is removed, while an irreversible poison permanently deactivates the active site. The distinction is what determines whether a screened-out facilitator can be cleaned and returned or must be discarded. ↩