Triage Filter¶

A prioritization procedure — instantiates Search Space Pruning

Sorts incoming cases into urgency bands — act now, defer, route to routine, or set aside — allocating scarce attention by priority rather than excluding candidates outright.

Triage Filter narrows attention, not the candidate set. Faced with more cases than capacity, it sorts each into an urgency band — immediate, deferred, routine, or set aside — so scarce reviewers spend their limited time where it matters most. Its defining difference from the hard-exclusion siblings is that most of its "pruning" is deferral, not deletion: a low-priority case is pushed down the queue, not thrown away, and can resurface if its situation changes. The whole procedure is driven by an explicit reckoning with scarcity — how much evaluation capacity exists and what each case would cost to handle — and its output is a multi-way priority sort rather than a keep/cut binary. Because deferral must be reversible, a defined path back up the queue is essential.

Example¶

A hospital emergency department at 2 a.m. has more arrivals than clinicians. A Triage Filter — the real Emergency Severity Index is one such five-level system — sorts each arrival: a patient with chest pain and low oxygen goes to immediate; a broken wrist to urgent but wait; a minor rash to routine, low priority; a request that isn't an emergency at all is redirected to a clinic. Nobody is turned away — everyone is placed in a band that matches the scarce clinical attention to the acuity of the need.

Crucially, the bands are not frozen. A "wait" patient whose condition worsens in the waiting room is re-triaged upward — the reentry path that keeps deferral from becoming neglect. The filter never decides who is "in" or "out"; it decides, moment to moment, where finite attention goes first, and lets cases move between bands as their urgency and the available capacity change.

How it works¶

Estimate load against capacity — read how many cases are waiting and what each would cost to fully handle, relative to the attention available.
Sort into bands — apply fast rules to place each case into an urgency/priority category, not a simple keep-or-cut.
Allocate scarce attention — direct capacity to the top bands first; lower bands wait, route to routine handling, or are set aside.
Re-triage on change — a defined path lets a case move up (or down) as its urgency or the system's load shifts.

The distinctive logic is prioritization under scarcity with reversible deferral, driven by the cost of handling each case rather than by any absolute bar.

Tuning parameters¶

Band thresholds — where the cutlines between urgency levels sit. Set for the current load: under heavy load the "immediate" bar rises so the scarcest attention is reserved for the most acute.
Number of bands — finer gradations route attention more precisely but slow the sort and demand more judgment per case.
Sort speed vs. accuracy — how quickly each case is categorized; triage must be fast, so it trades depth for throughput and accepts some misclassification.
Re-triage cadence — how often deferred cases are re-checked so a worsening one is caught before its deferral does harm.
Capacity coupling — how tightly the thresholds track real-time capacity, so the sort tightens as the queue grows and relaxes as it clears.

When it helps, and when it misleads¶

Its strength is allocating a hard capacity limit well: when you cannot attend to everything, triage puts the scarcest attention where the stakes are highest and, by deferring rather than deleting, keeps low-priority cases recoverable. It is the humane, reversible face of pruning under overload.

It misleads through mis-set thresholds in either direction. Under-triage — banding an urgent case too low — is the dangerous failure, letting a serious case languish in a queue.^[1] Over-triage floods the top band until "immediate" means nothing and true emergencies drown in the crowd. And "deferred" quietly becomes "abandoned" whenever the re-triage path is neglected and the bottom band is never revisited. The disciplines are to tie thresholds to real capacity, to re-triage deferred cases on a cadence, and to treat under-triage of high-stakes cases as the error to guard against most.

How it implements the components¶

cost_of_evaluation_estimate — the sort is driven by an explicit read of scarce capacity against what each case costs to handle; that scarcity reckoning is what makes it triage.
reentry_or_exception_path — re-triage is built in: a deferred case can move back up the queue as its urgency or the system's load changes.
pruning_rule — the banding rule is a multi-way priority sort (immediate / defer / routine / set aside), deliberately soft rather than a hard keep-or-cut.

It sets no hard-requirement gate (Constraint Filtering) and makes no comparative dominance judgment (Dominated-Option Removal); it prioritizes attention rather than excluding candidates, and it carries no audit apparatus of its own — that is Sample Audit of Exclusions.

Instantiates: Search Space Pruning — Triage Filter is the prioritization-under-scarcity form of narrowing, where deferral stands in for deletion.
Sibling mechanisms: Red-Flag Screen · Shortlisting · Branch and Bound · Beam Search · Constraint Filtering · Decision Tree Pruning · Dominated-Option Removal · Eligibility Screening · Negative Keyword Filter · Safety or Compliance Exclusion · Sample Audit of Exclusions

References¶

[1] In triage systems, under-triage (assigning a high-acuity case too low a priority) is treated as far more serious than over-triage, because a missed emergency is dangerous while an over-prioritized minor case merely wastes capacity — an asymmetry deliberately built into where the band thresholds are set. ↩