Skip to content

Fallacy of Accident

The inferential mistake of applying a general rule mechanically to a case that satisfies its terms but lies outside its intended scope — treating a defeasible generalisation, carrying an implicit ceteris paribus clause, as an exceptionless universal.

Core Idea

The fallacy of accident (fallacia accidentis, named by Aristotle) is the inferential mistake of applying a general rule to a particular case that falls under the rule's terms grammatically but lies outside its intended scope because of an accidental feature — in Aristotle's sense, an inessential, context-dependent property the rule did not contemplate. The schoolbook example: "Returning borrowed property is right; therefore you should return this borrowed knife to its owner who has since gone mad." The general rule was articulated against a default background in which returning the item poses no special danger; the homicidal-owner case is accidental to the rule's normal range. The structural diagnosis is that the inferer has treated a defeasible generalisation as an exceptionless universal: the rule always carried an implicit ceteris paribus clause — "absent special circumstances" — and the case at hand instantiates circumstances that the rule's framers would have recognised as defeating it. Every general rule of action, legal or moral, is formulated for a normal range of cases; the fallacy consists in carrying it mechanically into cases where the background conditions that justified the rule have failed. The equivalent diagnosis in modern philosophy of law is the rule/standard distinction: a rule specifies outcomes for defined cases, but where a case is accidental to the rule's intended scope, the underlying standard — the purpose the rule serves — must override its literal terms.

Structural Signature

Sig role-phrases:

  • the general rule — a defeasible generalization carrying an implicit ceteris paribus clause ("absent special circumstances") and a default scope
  • the particular case — an instance that satisfies the rule's surface terms grammatically
  • the accidental feature — a context-dependent, inessential property of the case that places it outside the rule's intended scope
  • the inferer's mistake — treating the defeasible generalization as an exceptionless universal, carrying it mechanically past the failed background conditions
  • the spurious conclusion — derived correctly from the rule's words yet at odds with the purpose the rule serves
  • the scope-condition check — the single diagnostic that routes the case: do the background conditions that justified the rule still hold here?
  • the standard-overrides-the-letter remedy — articulate the violated scope condition explicitly and let the underlying purpose govern the accidental case
  • the converse-accident boundary — the mirror error (hasty generalization, a special case wrongly elevated to a rule) from which this misfire is distinguished by the direction it runs

What It Is Not

  • Not a flaw in the rule. The general rule is sound for its normal range; the error is the inferer's, who carries a defeasible generalization mechanically into a case whose accidental feature lies outside the rule's intended scope. "Return what you borrow" is not defective — applying it to the homicidal owner is.
  • Not "accident" in the sense of chance. The Aristotelian accident is an inessential, context-dependent property the rule did not contemplate, not a coincidence or random event. The homicidal-owner case is "accidental" because the owner's madness is incidental to the borrowing relation the rule was framed around, not because anything happened by luck.
  • Not decided by the rule's surface terms. The case satisfies the rule's words — that is precisely why the bad inference looks valid — yet violates its intended scope. The whole diagnosis turns on separating "does this fall under the rule's words?" from "do the background conditions that justified the rule still hold here?", so surface satisfaction never settles soundness.
  • Not converse accident (hasty generalization). The fallacy of accident forces a general rule onto a special case outside its scope; its mirror runs the opposite direction, wrongly elevating a special case into a general rule. Conflating the two loses the direction of the misfire, which is exactly what distinguishes them.
  • Not a structure that travels beyond argument-evaluation. As a fallacy, it is a label for a failure-to-attend within one cognitive task — arguing, judging, or teaching argument — so the named mistake does not arise outside rule-evaluation. What recurs across domains is the structural fact it presupposes — that general rules are defeasible and admit exceptions when background conditions fail — carried by defeasibility, exception, generalization, and context_dependence, not by the fallacy itself.

Scope of Application

The fallacy of accident lives within the one practice of evaluating and applying defeasible rules, realized in several sectors; as a named mistake it does not arise outside argument-evaluation at all, so the structural fact it presupposes — that general rules carry an implicit ceteris paribus clause and admit exceptions when background conditions fail — is what recurs elsewhere, carried by defeasibility / exception / generalization / context_dependence, not by the fallacy itself.

  • Informal logic — a standard taxonomy entry under fallacies of presumption, teaching attention to scope conditions and unstated background assumptions.
  • Applied ethics — the engine of casuistry, testing whether morally relevant particulars defeat a principle (the lie told to the murderer at the door).
  • Legal reasoning — the doctrine of exceptions and the rule/standard distinction, where self-defense is a carve-out from the prohibition on harming and statutory generality yields to its purpose.
  • Pedagogy of reasoning — introductory logic texts using the fallacy to train students to separate a rule's surface terms from its intended scope.

Clarity

Naming the fallacy of accident makes visible the implicit ceteris paribus clause that every general rule of action carries but rarely states: "absent special circumstances." Without the label, an argument that returns the borrowed knife to its now-homicidal owner looks valid — the premises are true and the case plainly falls under the rule's terms — and a critic must reconstruct the whole defeasibility analysis to say what has gone wrong. With it, the practitioner can pinpoint the error precisely: the inferer has treated a defeasible generalization as an exceptionless universal, carrying a rule mechanically into a case whose accidental features lie outside the normal range the rule was framed for. The concept thereby separates two things ordinary reasoning conflates — the rule's surface terms, which the case satisfies, and the rule's intended scope, which it violates.

This sharpens the question a reasoner asks of any rule-application from "does this case fall under the rule's words?" to "do the background conditions that justified the rule still hold here?" — which is exactly the move casuistry formalizes when it tests whether morally relevant particulars defeat a principle, and which legal reasoning names as the rule/standard distinction: where a case is accidental to a rule's scope, the underlying standard, the purpose the rule serves, must override its literal terms. The label also locates the remedy as the mirror of the diagnosis — articulate the violated scope condition explicitly, carve out the exception — and marks its own boundary against the converse mistake of hasty generalization, where a special case is wrongly elevated into a general rule rather than a general rule wrongly forced onto a special case.

Manages Complexity

A reasoner evaluating rule-applications confronts what looks like an endless variety of distinct breakdowns: the knife returned to the madman, the lie told to the murderer at the door, the speeding ambulance ticketed for crossing the red light, the literal contract term enforced against its evident purpose. Treated case by case, each demands its own from-scratch defeasibility analysis — a fresh reconstruction of why an argument whose premises are true and whose case plainly falls under the rule's words nonetheless fails. The fallacy of accident compresses that whole class into a single diagnosis: in every instance the inferer has treated a defeasible generalization as an exceptionless universal, carrying a rule whose implicit ceteris paribus clause — "absent special circumstances" — was satisfied in the normal range into a case whose accidental features fall outside it. The sprawl of bad rule-applications collapses to one recognizable shape, and the labour of catching it drops from reconstructing the analysis anew each time to flagging the named move. What the practitioner tracks is no longer the endlessly varied content of each argument but two things and the relation between them: the rule's surface terms, which the case satisfies, and the rule's intended scope, which it may violate.

The decisive compression is that this reduces the open question "is this rule-application sound?" — which on its face requires weighing the whole argument — to a single tracked diagnostic the reasoner reads off directly: do the background conditions that justified the rule still hold in this case? That one question routes every rule-application into a clean branch structure. If the conditions hold, the case is within the normal range and the literal rule governs; if an accidental feature has defeated them, the case is outside scope and the underlying standard — the purpose the rule serves, which legal reasoning names as the rule overridden by its standard — must govern instead. The remedy falls out of the same structure as the mirror of the diagnosis, requiring no separate derivation: articulate the violated scope condition explicitly and carve out the exception. And the framework draws its own boundary as part of the compression, distinguishing this failure in one move from its converse, hasty generalization, where the error runs the other direction — a special case wrongly elevated into a general rule rather than a general rule wrongly forced onto a special case. So a domain that would otherwise present an unbounded catalogue of misfired inferences, each litigated on its own, reduces to one diagnosis, one scope-condition check, one two-way branch, and one boundary against the converse error.

Abstract Reasoning

The fallacy of accident licenses a set of moves for evaluating rule-applications, all running off a single scope-condition check and the two-way branch it opens, plus a remedy that mirrors the diagnosis and a boundary against the converse error.

Diagnostic — infer the violated scope from a sound-looking but misfiring application. The signature move catches an argument whose premises are true and whose case plainly falls under the rule's words yet whose conclusion is wrong, and infers the specific defect: the inferer has treated a defeasible generalization as an exceptionless universal, carrying a rule whose implicit ceteris paribus clause was satisfied in the normal range into a case whose accidental feature lies outside it. From the wrongness of returning the borrowed knife to its now-homicidal owner, the reasoner infers that the rule "return what you borrow" always carried an unstated "absent special circumstances," and that the homicidal-owner case instantiates exactly the circumstances the rule's framers would have recognized as defeating it. The diagnostic separates two things ordinary reasoning conflates — the rule's surface terms, which the case satisfies, and the rule's intended scope, which it violates — and locates the accidental feature as the context-dependent property that places the case outside the normal range. The signature to look for is a conclusion derived correctly from the rule's words but at odds with the purpose the rule serves.

Interventionist — articulate the violated scope condition, and let the standard override the rule's letter. The remedy falls out as the mirror of the diagnosis, requiring no separate derivation: make the implicit scope condition explicit and carve out the exception, so the rule is restated to exclude the accidental case it was never meant to govern. Where a case is accidental to a rule's scope, the move is to let the underlying standard — the purpose the rule serves, which legal reasoning names as the rule overridden by its standard — govern in place of the literal terms, and the prediction is that the correct outcome is restored: the knife is withheld, the lie is told to the murderer at the door, the ambulance is not ticketed. Each such carve-out is a claim that the articulated exception captures precisely the background condition whose failure defeated the rule, checkable by testing whether the revised rule now yields the right result on the accidental case while leaving the normal range untouched.

Boundary-drawing — separate the rule's words from its scope, and the fallacy from its converse. The construct's central discipline is the cut between "does this case fall under the rule's words?" and "do the background conditions that justified the rule still hold here?" — and the move includes refusing to let surface satisfaction of the terms settle soundness, insisting instead on the scope check. The construct also draws its own boundary against the converse mistake: the fallacy of accident forces a general rule onto a special case that lies outside its scope, whereas hasty generalization runs the error the other direction, wrongly elevating a special case into a general rule — so the analyst specifies which direction the misfire runs rather than conflating the two. This bounds the diagnosis to one recognizable shape, distinct in one move from the mirror failure with which it is easily confused.

Predictive — where the background conditions fail, the literal rule yields a conclusion at odds with its purpose. The framework supports a forward prediction the reasoner can make of any rule-application before the conclusion is drawn: route the case by the single scope-condition check, and the two-way branch predicts the outcome. If the conditions that justified the rule still hold, the case is within the normal range and the literal rule governs soundly; if an accidental feature has defeated them, the case is outside scope and the literal rule is predicted to deliver a conclusion that contradicts the purpose it serves — a result the underlying standard must then override. So the analyst forecasts in advance which applications will misfire, identifying the cases where mechanical adherence to the rule's terms will betray its point, and reserves the standard for exactly those, rather than litigating each rule-application's soundness from scratch.

Knowledge Transfer

Within the rule-applying disciplines the fallacy of accident transfers as mechanism. The diagnosis — a defeasible generalization treated as an exceptionless universal — the scope-condition check, the standard-overrides-the-letter remedy, and the boundary against converse accident all carry intact across the practices that articulate and apply rules. In informal logic it is a standard taxonomy entry teaching attention to scope conditions and unstated background assumptions. In applied ethics it is the engine of casuistry, which tests whether morally relevant particulars defeat a principle (the lie told to the murderer at the door). In legal reasoning it is the doctrine of exceptions and the rule/standard distinction — self-defense as a carve-out from the prohibition on harming, the statutory generality yielding to its purpose. Across these the same move (check whether the background conditions that justified the rule still hold; if not, let the standard govern) applies without translation, because they share one substrate: the evaluation and application of defeasible rules.

Beyond that substrate the honest reading is (B), with a twist specific to a fallacy: the named mistake does not even arise outside argument-evaluation, while the structural fact it polices recurs everywhere through its parents. The fallacy of accident is a label for a failure to attend within one cognitive task — arguing, judging, or teaching argument — so there is no substrate "outside rule-evaluation" in which the fallacy itself operates; logic, ethics, and law are not three distinct substrates here but three sectors of the one rule-application practice. What genuinely travels across domains is not the fallacy but the structural fact it presupposes — general rules are defeasible; they carry an implicit ceteris paribus clause and admit exceptions when background conditions fail — and that fact is already carried by the parents defeasibility, exception, generalization, and context_dependence (with bounded_rationality in the background). Stripped of "general rule," "particular case," and "fallacy," the construct reduces to "rules can have exceptions," which those parents supply. So the remedies (carve out the exception explicitly; attend to scope conditions; let the standard override the letter) are practices internal to careful rule-articulation, not interventions that port to non-rule-applying substrates — and the construct's mirror, converse accident (hasty generalization), clusters the same way: both are domain-specific instances of the scope-respecting-versus-scope-violating application of a generalization, not independent travelers. The honest move is to carry defeasibility / exception / context_dependence when the lesson is that general rules bend to special circumstances, and to keep "fallacy of accident," as a named diagnostic, within the argument-evaluation practice where it does its work (see Structural Core vs. Domain Accent).

Examples

Canonical

The defining instance descends from Plato's Republic Book I, where Cephalus proposes that justice is telling the truth and returning what one has borrowed. Socrates answers with a counterexample: if you borrowed weapons from a friend who was then sane, but he comes back for them in a fit of madness, returning them would not be just — no one would call it right to hand deadly weapons to a person who has lost his mind. The rule "return what you have borrowed" is sound across its normal range, but the case of the maddened owner satisfies the rule's words while lying outside the situation the rule was framed for. Aristotle later named the pattern fallacia accidentis: an inference that carries a general rule mechanically onto a case whose incidental feature — here the owner's madness — defeats the background conditions that justified the rule.

Mapped back: "Return what you borrow" is the general rule carrying an unstated "absent special circumstances"; the maddened friend's demand is the particular case that satisfies its surface terms. The owner's insanity is the accidental feature placing the case outside scope; handing over the weapons would be the spurious conclusion derived correctly from the words yet against the rule's purpose. Socrates' refusal applies the scope-condition check — the conditions that made returning right no longer hold.

Applied / In Practice

Legal reasoning meets the same structure in Riggs v. Palmer (New York, 1889). Elmer Palmer, named in his grandfather's will, murdered the grandfather to secure the inheritance before it could be changed. The statute of wills, read literally, contained no exception for a beneficiary who kills the testator, so its plain terms awarded Elmer the estate. The court nonetheless denied him, holding that the statute must be read against the deeper standard that "no one shall be permitted to profit by his own fraud, or to take advantage of his own wrong." The literal rule, applied mechanically to a case its drafters never contemplated, would have produced an outcome flatly at odds with the law's purpose; the underlying standard overrode the letter.

Mapped back: The statute of wills is the general rule and Elmer's claim the particular case satisfying its terms; his murder of the testator is the accidental feature outside the rule's intended scope. Awarding him the estate would be the spurious conclusion faithful to the words but contrary to purpose, and the court's "no one shall profit by his own wrong" is the standard-overrides-the-letter remedy in its textbook legal form.

Structural Tensions

T1: Mechanical application as vice versus as virtue (the remedy sacrifices what rules are for). The fallacy names the harm of carrying a rule rigidly past its scope, and its remedy is to let the underlying standard override the literal terms. But mechanical application is not only a failure mode — it is much of the point of having rules: a rule that applies by its words, without reweighing its purpose in each case, delivers predictability, constrains arbitrary judgment, and lets subjects rely on it in advance. The remedy that cures over-rigid application reopens exactly the discretion rules exist to close, and taken to its limit it dissolves the rule into its standard, so that every inconvenient application can be challenged as "accidental to scope." The tension is that eliminating the fallacy of accident trades toward the opposite pathology — unbounded purposive override that destroys the rule's rule-ness — and the right point between them is not fixed by the diagnosis. Diagnostic: Does overriding the letter here restore the rule's evident purpose, or does it license the kind of case-by-case exception-making that would leave the rule unable to bind or guide anyone?

T2: Implicit ceteris paribus versus unenumerable exceptions (the carve-out that can never close). The diagnosis holds that every general rule carries an unstated "absent special circumstances," and the remedy is to articulate the violated scope condition explicitly and carve out the exception. But if the defeating conditions could be fully specified in advance, they would already be in the rule; their implicitness reflects that the space of circumstances capable of defeating a rule is open-ended, and each carve-out invites the next accidental case the revised rule still fails to contemplate. Defeasibility is not a finite list of exceptions but a standing liability to new ones. The tension is that the remedy presumes exceptions are enumerable enough to patch the rule, while the very defeasibility the fallacy exploits guarantees the patching is perpetually incomplete — a rule made exception-proof for today's accidental case remains exposed to tomorrow's. Diagnostic: Does carving out this exception close the rule against a bounded, foreseeable class of cases, or merely add one patch to a rule whose defeasibility no finite set of carve-outs can exhaust?

T3: Determinate scope-check versus smuggled preference (identifying a true accident). The construct routes every application through one check — do the background conditions that justified the rule still hold? — and treats a "no" as diagnostic of a case outside scope. The murderer-inheritance and homicidal-owner cases make the check look crisp. But the check has no hard criterion for what counts as a genuine defeating circumstance versus a merely unwelcome outcome, and it rests on a counterfactual about what the rule's framers "would have recognized as defeating" — itself contestable and reconstructable to fit the reasoner's preferred result. In borderline cases the scope-condition check can license disapplying a rule one dislikes under cover of "it was never meant for this." The tension is that the very instrument used to catch the fallacy of accident can, wielded loosely, become a device for evading rules whose plain application is simply inconvenient. Diagnostic: Is the claim that this case lies outside the rule's scope grounded in a background condition the rule genuinely presupposed, or in the reasoner's dislike of the literal outcome dressed as a scope violation?

T4: Fault in the inferer versus fault in the rule (blame allocation the diagnosis fixes in advance). The entry insists the general rule is sound for its normal range and the error belongs to the inferer who carries it past its scope — "return what you borrow" is not defective, applying it to the homicidal owner is. This locates the pathology cleanly in the reasoning, not the norm. But a rule that predictably misfires on foreseeable cases, framed without stating scope conditions its drafters could have anticipated, arguably shares the fault: the statute of wills that awards an estate to a murdering heir is, on one view, a badly framed rule, not merely a well-framed one badly applied. The tension is that assigning the error entirely to the applier immunizes rule-drafting from criticism, when the boundary between "sound rule, bad application" and "under-specified rule" is exactly what is in dispute. Diagnostic: Was the accidental case genuinely unforeseeable to the rule's framers (fault in the applier), or foreseeable and left unhandled (fault in the rule's framing)?

T5: Autonomy versus reduction (the named fallacy or the defeasibility it presupposes). The fallacy of accident is a named diagnostic with home cargo — the general rule / particular case / accidental feature vocabulary, the scope-check, the standard-overrides-letter remedy, the boundary against converse accident. But uniquely, as a fallacy it is a label for a failure-to-attend within one cognitive task and does not even arise outside argument-evaluation; logic, ethics, and law are sectors of one rule-application practice, not distinct substrates. What travels is not the fallacy but the structural fact it presupposes — general rules are defeasible, carrying an implicit ceteris paribus clause and admitting exceptions when background conditions fail — already carried by defeasibility, exception, generalization, and context_dependence. Stripped of "rule," "case," and "fallacy," the construct reduces to "rules can have exceptions," which those parents supply. The tension is between a named argument-evaluation diagnostic and the flatter defeasibility structure that is what actually recurs across domains. Diagnostic: Resolve toward defeasibility/exception/context_dependence when the lesson is that general rules bend to special circumstances; toward the fallacy of accident when diagnosing a misfired rule-application within argument, ethics, or law.

Structural–Framed Character

The fallacy of accident sits at the framed pole of the structural–framed spectrum, alongside ad hominem and the etymological fallacy: not a regularity about the world but a verdict rendered within the practice of evaluating arguments, and constituted top to bottom by that practice. All five criteria point framed, several to the maximum. On evaluative weight it scores high: to charge "fallacy of accident" is to convict a reasoning step — the term is a normative classification, a finding that an inference is defective, not a neutral description of a mechanism the way "defeasibility" or "context dependence" names something value-free. On human-practice-bound it is high in the strongest possible sense, sharper here than in most fallacies: the entry states outright that, as a fallacy, it is "a label for a failure-to-attend" that does not even arise outside argument-evaluation — strip away an arguer drawing a conclusion and there is no fallacy at all, only a rule and a case exhibiting defeasibility, with nothing for the label to grip. On institutional_origin it is furniture of specific traditions — Aristotle's fallacia accidentis, the informal-logic taxonomy of fallacies of presumption, the casuistical method in ethics, the rule/standard distinction in jurisprudence — all distinctions drawn inside the practice of articulating and applying rules, not substrate-neutral form. On vocab_travels it scores low, and on import_vs_recognize it patterns as import-by-analogy off its home practice: logic, ethics, and law are not distinct substrates but sectors of one rule-application practice, and there is no further substrate in which the fallacy recurs.

The one structural-looking feature is the defeasibility skeleton — a general rule carries an implicit ceteris paribus clause and admits exceptions when the background conditions that justified it fail, so a case satisfying the rule's words may still lie outside its intended scope. That skeleton is genuinely portable and recurs across domains as the fact that general rules bend to special circumstances. But it does not pull the fallacy of accident off the framed pole, because that portable structure is precisely what the fallacy presupposes and instantiates from its parents (defeasibility, exception, generalization, context_dependence), not what makes "fallacy of accident" itself travel: the cross-domain reach belongs to the flat defeasibility fact, while the label's distinctive content — the diagnosis of a flawed inference, the scope-condition check, the standard-overrides-the-letter remedy, the boundary against converse accident — is exactly the argument-evaluation apparatus that does not lift. Its character: a normatively charged, practice-constituted fallacy label that does not even arise outside argument-evaluation, structural only in the defeasibility skeleton it presupposes from its parents and frames as a verdict.

Structural Core vs. Domain Accent

This section decides why the fallacy of accident is a domain-specific abstraction and not a prime, and it carries the case for its domain-specificity in the same breath — a case with a sharp twist, because as a fallacy the named mistake does not even arise outside argument-evaluation.

What is skeletal (could lift toward a cross-domain prime). Strip the argument-evaluation practice and a thin relational structure survives: a general rule carries an implicit ceteris paribus clause and admits exceptions when the background conditions that justified it fail, so a case satisfying the rule's surface terms may still lie outside its intended scope. The portable pieces are abstract — a defeasible generalization, a default scope, and a context-dependent feature that defeats the rule where the justifying conditions no longer hold. That structural fact is genuinely substrate-portable, and it is exactly the parent material the construct presupposes: defeasibility, exception, generalization, and context_dependence (with bounded_rationality in the background). Stripped of "general rule," "particular case," and "fallacy," the construct reduces to "rules can have exceptions," which those parents supply. But this is the fact the fallacy presupposes, not what makes it the specific named diagnostic it is.

What is domain-bound. Everything that makes this a fallacy is argument-evaluation furniture that does not survive extraction. The distinctive content is the diagnosis of a flawed inference — the inferer who treats a defeasible generalization as an exceptionless universal; the scope-condition check (do the background conditions that justified the rule still hold here?); the standard-overrides-the-letter remedy (articulate the violated scope condition, let the underlying purpose govern); and the boundary against converse accident (hasty generalization, the mirror misfire). The Aristotelian accident, the informal-logic taxonomy of fallacies of presumption, the casuistical method, and the jurisprudential rule/standard distinction are all traditions internal to the practice of articulating and applying rules. The worked cases — the maddened owner's knife (Plato's Republic), Riggs v. Palmer — are argument-evaluation material. The decisive and unusually strong test: as a fallacy it is a label for a failure-to-attend within one cognitive task, so strip away an arguer drawing a conclusion and there is no fallacy at all — only a rule and a case exhibiting defeasibility, with nothing for the label to grip.

Why this does not clear the prime bar. A prime is a relational structure whose vocabulary travels and whose cross-domain transfer is recognition of the same mechanism, not analogy — and it must span substrates. The fallacy of accident's transfer is bounded in a distinctive way: it transfers as mechanism within the rule-applying disciplines — informal logic, applied ethics (casuistry), legal reasoning (the doctrine of exceptions) — but those are not distinct substrates, they are sectors of one rule-application practice, and the scope-condition check and standard-overrides-letter remedy carry across them without translation because the substrate is constant. Beyond that practice the fallacy itself does not arise at all — there is no substrate outside rule-evaluation in which the named mistake operates. What genuinely travels across domains is not the fallacy but the defeasibility fact it presupposes, already carried by defeasibility / exception / generalization / context_dependence; and the remedies (carve out the exception, attend to scope, let the standard override the letter) are practices internal to careful rule-articulation, not interventions that port to non-rule-applying substrates. So when the bare structural lesson — general rules bend to special circumstances — is needed cross-domain, it is already carried, in more general form, by those parents. The cross-domain reach belongs to them; "fallacy of accident," as named, is the argument-evaluation diagnostic of the scope-violating application of a generalization (its mirror, converse accident, being the same-substrate scope-violating overgeneralization), and its inference-diagnosis, scope-check, and standard-override apparatus are domain baggage that should stay home.

Relationships to Other Abstractions

Local relationship map for Fallacy of AccidentParents appear above the current abstraction, mutual partners to the right, and children below. Node labels state whether each abstraction is prime or domain-specific; colors identify relation types.Fallacy of AccidentDOMAINPrime abstraction: Context — is a decomposition ofContextPRIMEPrime abstraction: Informal Fallacy — is a kind ofInformal FallacyPRIME

Current abstraction Fallacy of Accident Domain-specific

Parents (2) — more general patterns this builds on

  • Fallacy of Accident is a kind of Informal Fallacy Prime

    Fallacy of Accident is the informal-fallacy subtype that applies a sound default rule to a case whose defeating circumstances put it outside scope.

  • Fallacy of Accident is a decomposition of Context Prime

    Removing the fallacy and rule vocabulary leaves a fixed foreground whose application changes when the surrounding state changes.

Hierarchy paths (2) — routes to 2 parentless roots

Not to Be Confused With

  • Converse accident (hasty generalization). The structural mirror: the fallacy of accident forces a general rule onto a special case outside its scope, while converse accident runs the error the other direction — wrongly elevating a special case into a general rule. Conflating them loses the direction of the misfire, which is exactly what distinguishes them. Tell: does the bad inference go general-to-special (a rule mechanically applied to an exceptional case — this entry) or special-to-general (an atypical case overgeneralized into a rule — converse accident)?

  • "Sweeping generalization" / dicto simpliciter ad dictum secundum quid. Not a separate fallacy but an alternate name for the fallacy of accident itself — applying an unqualified general rule to a case the qualification excludes. A reader meeting either label is meeting the same mistake. Tell: if the error is a qualified case treated as if the unqualified rule governed it, "sweeping generalization" and "fallacy of accident" name one thing (converse accident is hasty generalization, the opposite direction).

  • "No true Scotsman" (ad hoc exception-making). The near-inverse move: rather than ignoring a legitimate exception (the fallacy of accident), the arguer invents an illegitimate exception on the spot to shield a generalization from a counterexample. One under-attends to real scope conditions; the other manufactures fake ones. Tell: is a genuine defeating circumstance being wrongly overridden by the rule's letter (this entry), or a real counterexample being wrongly excluded by a fabricated "true" qualifier (no true Scotsman)?

  • The rule/standard distinction (jurisprudence). Not a rival but the legal co-framing of the same diagnosis: where a case is accidental to a rule's scope, the underlying standard (the rule's purpose) must override its literal terms. The fallacy-of-accident label is the informal-logic framing; rule/standard is the same insight inside law. Tell: are you naming the reasoning error in argument-evaluation terms (this entry) or the jurisprudential doctrine that operationalizes its remedy (rule/standard) — they diagnose the same misfire?

  • Defeasibility / exception / context-dependence (parents). The substrate-neutral structural fact the fallacy presupposes — general rules carry an implicit ceteris paribus clause and admit exceptions when background conditions fail — which is what genuinely travels across domains. The fallacy of accident is the argument-evaluation diagnostic built on that fact; the fact itself is carried by these parents. Tell: are you invoking the flat "rules bend to special circumstances" lesson anywhere it applies (the parents, treated more fully elsewhere), or convicting a specific misfired rule-application in argument, ethics, or law (this entry)?

Neighborhood in Abstraction Space

Fallacy of Accident sits in a sparse region of the domain-specific corpus (78th percentile for distinctiveness): few abstractions share its structure, so a faithful description tends to retrieve it precisely.

Family — Overgeneralization & Rule Misapplication (5 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-07-12