Skip to content

Asymmetric Screening

Core Idea

This prime names the structural pattern in which a cheap, imperfect first-pass filter is deliberately tuned to allow one kind of error while forbidding the other, so that an expensive, authoritative check runs only on the items that survive the first pass. The asymmetry is the design feature, not an accident of imperfect tuning. In the canonical case, false negatives are unacceptable — a missed instance is expensive or unsafe — so the cheap filter is tuned for high sensitivity at the cost of specificity, and the resulting false positives are routed to the expensive check. The defining structural commitment is a cascade with an intentional error asymmetry: at least two tiers, with the upstream tier shedding only confident-negatives and the downstream tier resolving the false positives the upstream tier deliberately admitted.

The structural force is in making error-cost asymmetry a design parameter of the upstream tier. The pattern is not "build a better filter" but "build a deliberately leaky filter whose leak direction is safe and whose throughput savings on the downstream tier are large." This reframing matters because the naive instinct — minimise total error — is wrong whenever the two error types carry sharply different costs. The prime makes the cheap tier's job explicit: shed the easy, confident cases in the safe direction, and pass everything else down to where it can be resolved authoritatively, sizing the downstream tier to absorb the load the cheap tier's bias creates.

How would you explain it like I'm…

The Beeping Detector

A metal detector at the airport beeps for lots of harmless things like belt buckles, but it almost never misses a real weapon. That's on purpose: it's better to check a few extra people than to miss something dangerous. The cheap beep catches a lot, and a careful guard checks only the people who beep.

The Safe-Leak Filter

Asymmetric screening uses a cheap, fast first test that is deliberately a little wrong in a safe direction, followed by an expensive, careful test that only runs on whatever the first test flagged. In a lot of cases, missing a real problem is dangerous, so the cheap test is set up to never miss — it would rather raise a few false alarms than let a real one slip by. Those false alarms then get sent to the slow, trustworthy test to sort out. The clever part is that this is not 'build a better filter'; it's 'build a leaky filter that leaks in the safe direction' so you save a lot of work on the costly test. You also have to make the costly test big enough to handle all the alarms the cheap one creates.

Cheap Sieve, Costly Judge

Asymmetric screening is the pattern where a cheap, imperfect first-pass filter is deliberately tuned to allow one kind of error while forbidding the other, so that an expensive, authoritative check runs only on the items that survive the first pass. The asymmetry is the design feature, not an accident of bad tuning. In the canonical case false negatives are unacceptable — a missed instance is costly or unsafe — so the cheap filter is tuned for high sensitivity at the expense of specificity, and the resulting false positives get routed to the expensive check. The defining structure is a cascade with an intentional error asymmetry: at least two tiers, the upstream one shedding only confident negatives and the downstream one resolving the false positives the upstream tier deliberately admitted. The key reframe is that minimizing total error is the wrong goal when the two error types carry very different costs; instead you make the cheap tier shed easy confident cases in the safe direction and pass everything else down, sizing the downstream tier to absorb that load.

 

Asymmetric screening names the structural pattern in which a cheap, imperfect first-pass filter is deliberately tuned to allow one kind of error while forbidding the other, so that an expensive, authoritative check runs only on the items that survive the first pass. The asymmetry is the design feature, not an accident of imperfect tuning. In the canonical case, false negatives are unacceptable — a missed instance is expensive or unsafe — so the cheap filter is tuned for high sensitivity at the cost of specificity, and the resulting false positives are routed to the expensive check. The defining structural commitment is a cascade with an intentional error asymmetry: at least two tiers, with the upstream tier shedding only confident-negatives and the downstream tier resolving the false positives the upstream tier deliberately admitted. The structural force is in making error-cost asymmetry a design parameter of the upstream tier. The pattern is not 'build a better filter' but 'build a deliberately leaky filter whose leak direction is safe and whose throughput savings on the downstream tier are large.' This matters because the naive instinct — minimize total error — is wrong whenever the two error types carry sharply different costs. The prime makes the cheap tier's job explicit: shed the easy, confident cases in the safe direction, and pass everything else down to where it can be resolved authoritatively, sizing the downstream tier to absorb the load the cheap tier's bias creates.

Structural Signature

a stream of items to be classifieda cheap first-pass filter with tunable biasthe deliberate error-direction asymmetry (one error forbidden, the other tolerated)an expensive authoritative check downstreamthe gating relation (only survivors of the cheap pass reach the check)the downstream-cost budget that sizes the cascade

The pattern is present when each of the following holds:

  • A population of items. A stream of candidates must each be sorted into a safety-relevant class and its complement, where membership cannot be read off cheaply with certainty.
  • A cheap upstream filter. A low-cost, imperfect test issues a provisional verdict on every item; its threshold is a free design parameter, not a fixed property.
  • Error-cost asymmetry. The two misclassification errors carry sharply different costs. One direction is unacceptable (the forbidden error); the other is merely wasteful. This asymmetry is the load-bearing design fact.
  • Asymmetric tuning invariant. The cheap filter is biased so it (almost) never commits the forbidden error, accepting an inflated rate of the tolerable error as the price. Tuning it for symmetric accuracy breaks the pattern.
  • An authoritative downstream check. A high-cost test resolves the items the cheap filter passes through, committing neither error but too expensive to run on everything.
  • The gating relation. The expensive check runs only on items the cheap filter admits; the cheap filter's bias determines the downstream load, and the cascade is justified only when total cost falls below running the authoritative check on all items.

The components compose into a cost-asymmetric cascade: the cheap tier sheds the easy, confident cases in the safe direction and defers the rest, while the expensive tier absorbs the false-positive load the bias deliberately creates — a system to be sized and tuned as a whole, never as an isolated filter.

What It Is Not

  • Not generic screening. screening is any cheap pre-test that filters candidates before a costlier evaluation; asymmetric screening adds the deliberate one-sided error bias — the cheap tier is tuned to forbid one error type and tolerate the other, sized against a downstream-cost budget. Symmetric screening tuned for total accuracy is not this prime.
  • Not bias. bias is a systematic directional error to be reduced; asymmetric screening engineers a directional error on purpose because the two error costs differ sharply. The "bias" is a design feature, not a defect.
  • Not sampling representativeness. sampling_representativeness concerns whether a drawn sample mirrors the population; asymmetric screening concerns how a filter's threshold is set on every item, not how items are selected for measurement.
  • Not signaling. signaling is a party emitting a costly cue to reveal hidden type; asymmetric screening is a receiver-side cascade that classifies items, with no strategic emitter required.
  • Not opportunity asymmetry. opportunity_asymmetry is about unequal access to options; asymmetric screening is about unequal error costs driving a two-tier filter design.
  • Common misclassification. Tuning the cheap tier for an F1 score or "best accuracy" in a setting where one error is catastrophically costlier than the other. Catch it by asking which error is forbidden and whether the filter's objective is one-sided error control under a downstream budget — if total error is being minimised, the cascade is mis-specified.

Broad Use

The pattern recurs across computing, medicine, security, and detection science. In computer science it is the Bloom filter and the Cuckoo filter — the canonical case, where false positives are allowed but false negatives are impossible by construction — along with spam quarantine queues, branch prediction with rollback, hash-based deduplication front-ends, tiered cache lookups, and approximate-nearest-neighbour search before exact rerank. In medical screening it is mammography, PSA testing, lateral-flow tests, and prenatal screening, all designed for high sensitivity at the cost of specificity, with downstream diagnostic follow-up resolving the false positives. In security and safety gating it is metal detectors and body scanners that alarm liberally before a hand search, contraband-scanning canines, and explosive-trace detectors. In content moderation it is flag-then-review pipelines that err toward over-flagging because the cost of letting harmful content through dominates reviewer time. The pattern also appears in spell-check and tokenisation, hiring funnels that reject only confident no's, legal probable-cause thresholds that license investigation rather than punishment, industrial quality assurance that flags suspect units for human inspection, and astronomy and physics event detection, where cheap real-time triggers gate expensive downstream analysis pipelines.

Clarity

Naming the pattern clarifies a design decision that is often made implicitly and badly. Many filtering pipelines are tuned symmetrically — to minimise total error rate — when the costs of the two error types are sharply asymmetric. The asymmetric-screening pattern makes the asymmetry a first-class design parameter: identify which error type is unacceptable, tune the upstream tier accordingly, ensure capacity at the downstream tier to absorb the resulting false-positive load, and budget the two tiers' cost ratios so that the cascade is cheaper than running the authoritative check on everything. It also clarifies a recurring failure mode — tuning the cheap filter for "accuracy" or for an F1 score rather than for one-sided error control. A Bloom filter tuned for best accuracy is a broken Bloom filter; a screening mammogram tuned for lowest total error is one that misses cancers; a content-moderation classifier tuned for balanced precision and recall lets harmful content through at the rate balanced precision tolerates. The clarifying move is to insist that the cheap tier's objective is one-sided error control under a downstream-cost budget, not symmetric accuracy.

Manages Complexity

The pattern compresses a wide range of two-tier cascade designs into a single diagnostic: which error is unacceptable, what is the throughput cost of the cheap tier, what is the per-item cost of the expensive tier, and what is the expected false-positive load on the expensive tier as a function of the cheap tier's tuning? The intervention space sorts cleanly into a small set of moves. One can move the cheap tier's threshold — more aggressive tuning yields more false positives and fewer false negatives. One can reduce the cost of the expensive tier, so that more false positives become tolerable. One can add intermediate tiers, cascading filters of increasing cost and specificity. And one can introduce calibration loops, monitoring downstream outcomes and adjusting the cheap tier's threshold to hold the target false-negative rate. The same four moves apply whether the cascade is a Bloom filter in front of a disk lookup, a rapid triage score in front of a clinical workup, or a classifier in front of a human moderator. The complexity reduction is that a sprawling family of pipeline designs becomes one structural object — a cost-asymmetric cascade — with one tuning vocabulary and one set of levers.

Abstract Reasoning

The pattern supports a precise cost model. Let p be the prior probability of the safety-relevant class; let the per-item costs of the cheap and expensive tiers be fixed parameters; let FP and FN be the cheap tier's false-positive and false-negative rates; and let the loss per false negative be potentially unbounded for unsafe instances. The total system cost is dominated by the false-negative loss term, which drives the design toward driving FN toward zero even at large FP. The throughput savings come from the expensive tier running only on the small fraction of items the cheap tier admits — large when the prior is small and the false-positive rate moderate. The tuning trade-off is therefore explicit and quantitative rather than a matter of taste. The reasoning also supports cascading: a three-tier system of cheap-screen, medium-check, and authoritative-check is justified whenever the medium check's incremental cost is less than the expensive-check load it saves. The structural insight the model makes precise is that asymmetric-screening cascades have an economic logic and should be designed as a system, not as an isolated filter optimised in ignorance of the tiers downstream.

Knowledge Transfer

The structure transfers cleanly because its design parameters — error-cost asymmetry, the cheap/expensive cost ratio, item volume, and prior class probability — are substrate-free. A radiologist designing a mammography programme is performing the same design as a computer scientist designing a Bloom filter and the same design as a content-moderation team designing a flag-then-review queue: identify the unacceptable error, tune the cheap tier asymmetrically against it, size the downstream tier to absorb the false-positive load, and monitor the downstream rate to recalibrate. The interventions transfer with the recognition. Tightening the threshold means more recalls or more flagged content; expanding the downstream tier means more radiologists or more reviewers; reducing the downstream tier's cost means better imaging or better reviewer tooling; adding an intermediate tier means ultrasound, AI assistance, or a medium-cost classifier. Because each move has the same effect on the same parameters in every substrate, an engineer who has tuned one cascade can reason about another without retooling. The pattern also transfers in the failure-mode direction: every substrate exhibits the same characteristic failure — tuning the cheap tier for symmetric accuracy and missing the unacceptable error — and the same characteristic fix — re-framing the design around one-sided error control with a downstream-cost budget. This shared failure mode is itself a portable warning: whenever a practitioner sees a single filter being optimised for total accuracy in a setting where one error is far costlier than the other, the asymmetric-screening prime tells them the filter is mis-specified and points directly to the cascade structure that repairs it. The vocabulary of cascades and error asymmetry is generic enough to travel without friction, and although the pattern carries a faint institutional tinge from its screening and hiring instances, its core is bare structure: a cost-asymmetric two-tier cascade that any designer in any domain can recognise and tune.

Examples

Formal/abstract

The Bloom filter is the canonical formal instance, and its construction makes the error asymmetry provable rather than tuned. The stream of items is a set of keys being tested for membership in a large set; the cheap upstream filter is a fixed-size bit array indexed by several independent hash functions; the authoritative downstream check is an exact lookup against the backing store on disk or over the network. To insert a key, set the bits at each of its hash positions; to query, check whether all those bits are set. The deliberate error asymmetry is structural: if any of the bits is clear, the key is certainly absent, so a false negative is impossible by construction. A false positive can occur — all the queried bits happen to be set by other keys — so the filter forbids one error and tolerates the other by design, not by threshold choice. The gating relation is exact: only keys the filter reports as possibly-present trigger the expensive lookup. The downstream-cost budget is quantitative and tunable: the false-positive probability falls roughly as a function of the bit-array size and the number of hash functions per stored element, so a designer sizes the array to push the false-positive rate low enough that the expensive backing-store lookups it provokes stay within budget. The intervention space is precisely the prime's: enlarge the array to cut false positives, accept a higher false-positive rate to save memory, or cascade a second filter. Tuning a Bloom filter for "best accuracy" is incoherent — the false-negative rate is already zero — which is exactly the prime's warning that the cheap tier's objective is one-sided error control, not symmetric accuracy.

Mapped back: The Bloom filter instantiates the full cost-asymmetric cascade with the rare luxury of a provably one-sided error, showing the prime's roles — cheap biased filter, forbidden error, authoritative check, gating relation, downstream budget — as exact structural facts rather than tuning choices.

Applied/industry

Population cancer screening is the same cascade on a medical substrate, where the asymmetry is a deliberate clinical-design choice. The stream of items is a screened population; the cheap upstream filter is a low-cost imaging test such as screening mammography; the authoritative downstream check is a diagnostic workup — additional imaging, biopsy, histopathology. The forbidden error is the false negative — a missed cancer is potentially fatal — so the programme is deliberately tuned for high sensitivity at the cost of specificity, accepting an inflated false-positive (recall) rate as the price. The gating relation is that the expensive, invasive, anxiety-inducing workup runs only on the women the cheap screen flags; the downstream-cost budget is the radiology and pathology capacity that must absorb the recall load the screen's bias deliberately creates. The prime's diagnostic immediately exposes a common policy error: arguments to "reduce screening false positives" by tuning the screen toward balanced accuracy are arguments to miss more cancers, because they treat a deliberately one-sided filter as if it should minimise total error. The interventions are the prime's catalogue made concrete: move the threshold (recall criteria) to trade recall volume against missed cancers; reduce the downstream cost (faster, cheaper diagnostic follow-up) so more false positives become tolerable; add an intermediate tier (ultrasound or AI triage between screen and biopsy); or run a calibration loop monitoring the interval-cancer rate to confirm the screen's false-negative rate is holding. A content-moderation flag-then-review pipeline exhibits the identical structure — an over-flagging classifier gating scarce human reviewers, with the forbidden error being letting genuinely harmful content through — so a designer who has tuned one cascade reasons about the other without retooling.

Mapped back: Cancer screening and content moderation are the same cost-asymmetric cascade as the Bloom filter, with a clinically or editorially chosen one-sided bias replacing the Bloom filter's structural one; in each the cheap tier's job is to shed confident negatives safely and defer the rest to an authoritative check sized to absorb the deliberate false-positive load.

Structural Tensions

T1 — Local Tier versus Global Cascade (Scalar). The prime insists the cheap tier be tuned for one-sided error, not accuracy — but that is a local objective; the cascade's justification is global, that total cost falls below running the authoritative check on everything. A cheap tier perfectly tuned for one-sided error can still be the wrong design if its false-positive load overwhelms the downstream tier. The failure mode is optimising the filter in isolation and discovering the cascade is more expensive than the brute-force check it replaced. Diagnostic: compute the downstream load the bias creates and compare end-to-end cost against running the authoritative check on the full stream.

T2 — Forbidden-Error Bias versus Base-Rate Reality (Measurement). Tuning for near-zero false negatives is correct only relative to the prior class probability; when the safety-relevant class is very rare, even a well-tuned filter floods the downstream tier with false positives whose absolute number swamps the true cases. The failure mode is the base-rate fallacy at the system level — a "high sensitivity" screen whose flagged pool is overwhelmingly false, eroding downstream trust and inviting alert fatigue. Diagnostic: report the downstream tier's positive predictive value, not the cheap tier's sensitivity, and watch whether reviewers begin rubber-stamping a queue that is mostly noise.

T3 — Static Threshold versus Drifting Stream (Temporal). The cost model fixes the prior, the error rates, and the cost ratio, but real streams drift — the prevalence shifts, adversaries adapt, the population changes — and a threshold tuned once silently slides off its target false-negative rate. The failure mode is a screen that was safe at deployment quietly starting to miss the forbidden error as conditions move. Competing prime: feedback supplies the calibration loop the static cascade lacks. Diagnostic: monitor a downstream outcome (interval cancers, escaped harms) that reveals the missed error, since the cheap tier by construction cannot see its own false negatives.

T4 — Asymmetric Filter versus Adversarial Input (Coupling). Screening assumes items are drawn from a fixed distribution, but when an adversary controls the input they can probe the cheap filter and craft items that exploit its tolerated-error direction — Bloom-filter pollution, spam tuned to pass the triage, content engineered to read as benign. The deliberate leak the prime celebrates becomes an attack surface. The failure mode is treating the false-positive bias as merely wasteful when an adversary turns the false-negative gap into a reliable bypass. Diagnostic: ask whether anyone benefits from defeating the screen and can observe its responses; if so, adversarial_robustness constraints override pure cost tuning.

T5 — Two Error Types versus a Continuum of Stakes (Scopal). The signature collapses misclassification into one forbidden and one tolerated error, but in many domains the tolerated error is not uniformly cheap — a false positive that triggers a biopsy, a job rejection, or a wrongful flag carries real, unevenly distributed harm. Treating false positives as merely "wasteful throughput" hides costs borne by the people downstream of them. The failure mode is a cascade tuned as if only the forbidden error matters, externalising the tolerated error's harm onto those it lands on. Diagnostic: price the tolerated error's human cost explicitly rather than booking it as reviewer time alone.

T6 — Cheap Tier as Filter versus as De Facto Decision (Sign/Authority). The gating relation says only survivors reach the authoritative check — which means a confident-negative from the cheap tier is final, never reviewed. When the cheap tier's "confident negatives" are in fact uncertain, its shed cases become unappealable decisions made by the cheapest, least authoritative component. The failure mode is the cheap filter quietly becoming the real decision-maker for everything it rejects, with no recourse path. Diagnostic: audit a sample of the cheap tier's negatives, not just the flagged pool; the gating structure guarantees those errors are otherwise invisible.

Structural–Framed Character

Asymmetric Screening sits at the structural end of the structural–framed spectrum, with only a faint institutional tinge — consistent with its near-zero aggregate of 0.2. At its core it is a cost-asymmetric cascade: a cheap, deliberately one-sided-error filter gating an expensive authoritative check, a shape stated entirely in substrate-free parameters (error-cost asymmetry, prior class probability, the cheap/expensive cost ratio, the downstream load).

Most diagnostics read purely structural. The vocabulary travels freely: the identical cascade is told as a Bloom filter in computing, a screening mammogram in medicine, a metal detector before a hand search in security, and a flag-then-review queue in content moderation, each domain narrating it in its own words with no lexicon that must come along. It carries no inherent approval or disapproval — the engineered one-sided error is neither virtue nor defect until you specify the stakes, which is why the prime works hard (in its contrast with bias) to insist the directional error is load-bearing design rather than pathology. And invoking it recognises a pattern already present — a filter whose objective is one-sided error control under a downstream budget — rather than importing an interpretive frame; the diagnostic is simply "which error is forbidden, and is the cheap tier tuned around it?"

Two criteria carry a half-weight rather than zero, and honestly so. The institutional_origin and human_practice_bound scores (0.5 each) register that the prime's most salient cases — screening programmes, hiring funnels, content-moderation pipelines, legal probable-cause thresholds — are engineered, often institutional, classification systems with human reviewers as the authoritative downstream tier. The pattern leans on designed cascades more than on indifferent physical substrates; its astronomy and Bloom-filter instances keep it from being purely human-practice-bound, but the centre of gravity is engineered systems. That genuine engineered tinge is exactly what the half-scores encode, and it is not enough to pull the prime off the structural side: the relational skeleton — a cheap biased filter feeding an expensive check — is bare structure that any designer in any domain can recognise and tune.

Substrate Independence

Asymmetric Screening is a strongly substrate-independent prime — composite 4 / 5 on the substrate-independence scale. Its domain breadth is total: the deliberate one-sided-error cascade recurs with the same structural force in computer science (Bloom and Cuckoo filters, where false negatives are impossible by construction), in medicine (mammography, PSA, lateral-flow and prenatal screening tuned for sensitivity over specificity), in security (metal detectors and trace scanners that alarm liberally before a hand search), in content moderation (flag-then-review pipelines), in hiring funnels and legal probable-cause thresholds, and in astronomy and physics (cheap real-time triggers gating expensive analysis pipelines). Its structural abstraction is high but not total: the signature is stated in genuinely substrate-free parameters — error-cost asymmetry, prior class probability, the cheap/expensive cost ratio, the downstream-cost budget — yet the prime's centre of gravity leans on engineered, often institutional classification systems with human reviewers as the authoritative tier, which is the modest framing that holds the composite just below ceiling. Its transfer evidence is concrete: the identical cost model and four-move tuning catalogue carry from a Bloom filter to a screening programme to a moderation queue, so a designer who has tuned one cascade reasons about another without retooling, and the shared failure mode (tuning for symmetric accuracy and missing the forbidden error) is itself a portable warning. The engineered-systems tinge is the only thing keeping this from a 5.

  • Composite substrate independence — 4 / 5
  • Domain breadth — 5 / 5
  • Structural abstraction — 4 / 5
  • Transfer evidence — 4 / 5

Relationships to Other Primes

One-hop neighborhood: parents above, mutual partners to the right, children below.Asymmetric Screeningsubsumption: ScreeningScreening

Parents (1) — more general patterns this builds on

  • Asymmetric Screening is a kind of Screening

    The file: a 'specific, disciplined variant' of screening — a cheap first-pass filter DELIBERATELY tuned to forbid one error type and tolerate the other, sized against a downstream-cost budget. Generic accuracy-tuned screening is not this prime.

Path to root: Asymmetric ScreeningScreeningMechanism Design

Neighborhood in Abstraction Space

Asymmetric Screening sits in a moderately populated region (59th percentile for distinctiveness): it has near-neighbors but no dense thicket of synonyms.

Family — Unclustered & Miscellaneous (91 primes)

Nearest neighbors

Computed from structural-signature embeddings · 2026-06-14

Not to Be Confused With

The nearest neighbour is screening, and asymmetric screening is best understood as a specific, disciplined variant of it. Plain screening is the generic move of running a cheap test first to reduce the load on a costly one — any triage cascade qualifies, and the cheap test is typically tuned to minimise overall misclassification. Asymmetric screening adds a non-negotiable design commitment that generic screening lacks: a deliberate, one-sided error bias set by the sharply unequal costs of the two error types, with the cheap tier tuned to drive the forbidden error toward zero while tolerating an inflated rate of the cheap error, and the whole cascade sized against a downstream-cost budget. The discriminating test is the tuning objective: a screen optimised for accuracy or F1 is generic screening; a screen whose explicit objective is one-sided error control under a downstream budget is asymmetric screening. Conflating the two produces the prime's headline failure — tuning a deliberately leaky safety filter as if it should minimise total error, which means missing the very cases it exists to catch.

Asymmetric screening must also be separated from bias. In most of the catalog, bias is a pathology — a systematic directional error that distorts inference and should be detected and removed. Asymmetric screening manufactures exactly such a directional error and treats it as the correct design. The structural difference is normative direction: bias is something the analyst fights, whereas in asymmetric screening the one-sided error is the engineered solution to a cost asymmetry. The two meet, and can be confused, precisely at the point where someone proposes to "reduce the bias" of a screen — which, if the screen is a properly designed asymmetric one, is an argument to commit the forbidden error more often. Recognising the cascade as asymmetric screening rather than as biased screening is what tells the analyst that the directional error is load-bearing and must not be tuned away.

A thinner but real confusion is with sampling_representativeness. Both involve a cheap operation standing in for an exhaustive one, and both can fail through base-rate effects. But sampling representativeness governs whether a subset drawn for measurement mirrors the population — an inference-validity question about selection — while asymmetric screening governs how a per-item filter threshold is set when every item is tested and the two error costs differ. The base-rate trap appears in both, but in different roles: in sampling it threatens external validity; in asymmetric screening it floods the downstream tier with false positives whose absolute number swamps the true cases. A practitioner who reaches for representativeness diagnostics when the real issue is a mis-tuned cost-asymmetric cascade will audit the wrong property.

For a practitioner these distinctions decide which knob to turn. If the cascade is read as generic screening, the reflex is to maximise accuracy — wrong when error costs are asymmetric. If it is read as biased screening, the reflex is to debias — wrong when the bias is the design. If it is read as a sampling problem, the reflex is to fix selection — wrong when the issue is threshold cost-tuning. Naming the prime correctly directs attention to the one decision that matters: which error is forbidden, and is the cheap tier tuned, and the downstream tier sized, around that forbidden error.

Solution Archetypes

No catalogued solution archetypes reference this prime yet.