Duty to Rescue¶
Impose a jurisdiction-specific legal obligation to take reasonable, feasible steps to aid or summon aid for a person in serious peril when a recognized trigger applies and assistance does not create disproportionate danger or conflict.
Core Idea¶
Duty to rescue is a legal obligation, recognized only under the governing jurisdiction and facts, to take reasonable and feasible steps when another person faces sufficiently serious peril. The required response may be direct assistance, warning, or summoning competent aid; it is not necessarily physical intervention. The trigger, protected persons, required knowledge, feasible response, self-risk limit, conflicting duties, and civil or criminal consequence must all come from applicable law rather than from a free-floating moral intuition.
Legal systems locate the duty differently. A broad rescue statute may impose a bystander obligation when an accident, common danger, or emergency creates a need for necessary assistance that can reasonably be expected without substantial danger to the rescuer or violation of other important duties.
Scope of Application¶
Duty-to-rescue analysis is literal in comparative criminal law, tort law, regulatory obligations, and institutional roles when liability turns on failure to provide or summon feasible assistance after a legally recognized trigger.
- General rescue statutes. Some jurisdictions impose a bounded duty on capable bystanders during specified emergencies.
- Risk creation. A person whose conduct creates a danger may have an affirmative duty to prevent or reduce resulting harm.
- Voluntary undertaking. Beginning aid can create obligations to exercise reasonable care or avoid worsening reliance-based risk.
- Special relationships. Defined relationships can support affirmative duties of protection or assistance.
- Custody and control. Institutions or custodians may owe duties because another person cannot protect themselves normally.
- Professional or official roles. Employment, licensure, office, or contract can activate role-specific assistance obligations.
- Maritime and transportation settings. Specialized statutes and conventions may impose rescue or reporting duties.
- Comparative legal research. The construct makes different trigger and exception architectures comparable without pretending they are identical.
Clarity¶
Begin with the jurisdiction, date, authority, and civil, criminal, regulatory, or professional pathway. State who is allegedly obligated, who is protected, what peril existed, what the actor knew, and which fact activates the duty. Identify feasible responses without prescribing unsafe action, and state the statutory or doctrinal safety, competence, and conflicting-duty limits. Separate existence of duty from breach, causation, defenses, immunity, and remedy. Distinguish a duty to summon aid from a duty to provide hands-on treatment.
Manages Complexity¶
The abstraction converts a large fact pattern into an ordered legal inquiry: governing source, trigger, knowledge, capacity, feasible response, limits, omission, and consequence. It prevents the emotionally intuitive question—why did the person not help?—from replacing the legally antecedent question—what law imposed which act on this person here? It also exposes differences between systems that impose general bystander duties and systems that proceed through enumerated exceptions.
Abstract Reasoning¶
- Fix jurisdiction, relevant date, and the type of liability or enforcement being considered. 2. Identify authoritative statutes, cases, restatements, regulations, contracts, or role rules. 3. Characterize the peril and the person within the authority's protected scope. 4. Test each possible duty trigger: risk creation, undertaking, relationship, custody, role, contract, or general statute. 5. Determine the actor's legally relevant knowledge, ability, opportunity, and available safe responses.
Knowledge Transfer¶
The strict parent is Accountability: duty to rescue makes a person legally answerable for failing to take a required action after a recognized trigger. Responsibility Attribution and Threshold-Triggered Rule Activation illuminate parts of the analysis, but the former identifies responsibility more generally and the latter presumes a continuous observable threshold not present in every rescue rule. The legal residual is affirmative omission liability bounded by authority, relationship, feasibility, and safety.
Relationships to Other Abstractions¶
Current abstraction Duty to Rescue Domain-specific
Parents (1) — more general patterns this builds on
-
Duty to Rescue is a kind of Accountability Prime
Accountability is the strict parent because duty-to-rescue rules make a legally covered person answerable for omitting specified assistance.
Hierarchy path (1) — routes to 1 parentless root
- Duty to Rescue → Accountability → Authority
Neighborhood in Abstraction Space¶
Duty to Rescue sits in a sparse region of the domain-specific corpus (95th percentile for distinctiveness): few abstractions share its structure, so a faithful description tends to retrieve it precisely.
Family — Unclustered & Miscellaneous (1565 abstractions)
Nearest neighbors
- Civil death — 0.79
- Non-retroactivity — 0.77
- Unowned Property — 0.77
- Non Bis in Idem — 0.76
- Injury (law) — 0.76
Computed from structural-signature embeddings · 2026-09-08