Rare-Case Carveout¶

Policy / service rule — instantiates Tail-Risk Preservation

Writes an explicit exception into a mainstream rule so a named set of low-frequency cases gets a protected path instead of the rejection the general rule would hand them.

A Rare-Case Carveout is a specific, written exception embedded in an otherwise-general rule: the mainstream rule works for almost everyone, but a small, nameable set of cases predictably fails it for the wrong reasons, so the carveout gives exactly those cases an alternate qualifying path. Its defining move is that it operates at the level of the rule itself — it enumerates which rare cases are exempt and by what criteria they qualify, rather than reasoning about groups (an Equity Carveout) or setting a service level (a Minimum Service Floor). Because a carveout is a valuable exemption, its two inseparable parts are the entry rule and the guard against people gaming into it.

Example¶

A health plan's drug formulary decides coverage with a standard cost-effectiveness threshold — sensible for common conditions with large trial populations. But that same rule automatically rejects treatments for very rare diseases, whose tiny patient counts make the per-patient cost look wildly high and whose trials can never reach the statistical power the rule expects. A Rare-Case Carveout writes an explicit exception: therapies with a recognized rare-disease (orphan) designation are evaluated on a modified pathway rather than bounced by the standard threshold.^[1] The carveout enumerates precisely which conditions qualify (the mapped tail), states the alternate criteria they must meet, and — because the designation confers a valuable exemption — pairs it with controls against relabeling an ordinary drug to slip through the rare-disease door.

How it works¶

Map the qualifying cases. The carveout rests on a concrete list or definition of the rare cases it covers — the tail made explicit, not gestured at — so the exception is bounded and checkable.
Write the alternate path. It specifies the criteria a mapped case must meet to take the protected route, tied to why the general rule misfires for it.
Guard the door. Because entry is advantageous, the carveout attaches controls — verification, tight definitions, audit — so ordinary cases cannot be dressed up to qualify.

Tuning parameters¶

Definition tightness — how narrowly the qualifying set is drawn. Tight resists gaming but risks excluding genuine cases just outside the line; loose captures more but invites abuse.
Alternate-criteria stringency — how demanding the protected path's own bar is, trading accessibility for the exemption against protecting its integrity.
Verification burden — how much proof a case must show to claim the carveout, balancing gatekeeping against access friction for the very cases it exists to help.
Anti-gaming intensity — how hard the controls work to keep ordinary cases out, weighed against the cost and delay they impose on legitimate ones.
Review / re-mapping cadence — how often the qualifying map is refreshed as new rare cases appear or old ones mainstream.

When it helps, and when it misleads¶

Its strength is surgical: it fixes a known, specific failure of a general rule without rewriting the rule for everyone, preserving the efficiency of the mainstream path while rescuing the enumerated tail. It is the standard instrument wherever one rule serves most people well but predictably wrongs a small, identifiable set.

Its failure modes orbit the door. A carveout with weak controls becomes a loophole — the exemption is more attractive than the rule, so effort flows into qualifying for it rather than meeting the real bar, and the tail protection is diluted by impostors. Drawn too tightly, it strands the genuine cases sitting just outside its definition, recreating the exclusion it was meant to cure. And a stale carveout keeps protecting cases whose rationale has lapsed while missing new ones. The discipline that keeps it honest is tying the qualifying map to an explicit reason the general rule fails those cases, pairing it with real verification, and re-mapping on a cadence so the exception tracks the actual tail.

How it implements the components¶

exception_rule — the mechanism is the explicit, bounded rule by which a mapped rare case bypasses the mainstream path.
abuse_or_gaming_control — the verification and tight-definition guards that keep a valuable exemption from being gamed by ordinary cases.
tail_case_map — the enumerated set of qualifying rare cases that bounds the carveout and makes it checkable.

It does not articulate the fairness rationale or protect a whole group's standing — that is the Equity Carveout; nor does it set the service level a qualifying case then receives (that is the Minimum Service Floor).

Instantiates: Tail-Risk Preservation — carves a protected path in a general rule for a named set of low-frequency cases.
Sibling mechanisms: Equity Carveout · Minimum Service Floor · Emergency Reserve · Exception Budget · Catastrophic Case Protocol · Long-Tail Support Tier · Manual Review Route · Rare-Event Sampling · Rotating Tail Attention Cycle · Sentinel Event Monitoring · Tail Case Registry

References¶

[1] An orphan drug designation, established by rare-disease legislation such as the U.S. Orphan Drug Act, carves treatments for low-prevalence conditions out of the incentives and evaluation logic tuned for common diseases — the real-world exemplar of a rule-level carveout for a named rare-case set. ↩