Non-refoulement¶
A legal principle barring a state from transferring a person to a territory where specified persecution, torture, or other grave harm faces a real risk.
Core Idea¶
Non-refoulement constrains expulsion, deportation, extradition, rejection at borders, or indirect transfer under treaty, customary, refugee, and human-rights regimes with differing scope and exceptions. Authorities assess destination risk, personal circumstances, chain transfer, jurisdiction, applicable instrument, procedural safeguards, and any legally available exception before removal. The abstraction is therefore identified by a declared carrier, a transformation or constraint over that carrier, and an invariant that tells an analyst whether the named structure is genuinely present.
The load-bearing residual is not the broad topic of international refugee and human rights law. It is the domain-specific identity determined by person, transferring authority, destination and onward-transfer chain, protected harm, risk standard, jurisdiction, governing legal source, procedure, exception, and remedy are identified.
Scope of Application¶
Non-refoulement belongs to international refugee and human rights law and is useful where the analyst can specify the typed international refugee and human rights law carrier, defining objects and relations, parameters, conventions, evidence, boundary cases, and comparison targets, then evaluate person, transferring authority, destination and onward-transfer chain, protected harm, risk standard, jurisdiction, governing legal source, procedure, exception, and remedy are identified. The scope is broad within that domain but bounded by the need for person, transferring authority, destination and onward-transfer chain, protected harm, risk standard, jurisdiction, governing legal source, procedure, exception, and remedy are identified. Descriptive international-law identity only; application is fact- and jurisdiction-sensitive and this is not legal advice.
Clarity¶
The abstraction clarifies a crowded vocabulary by making person, transferring authority, destination and onward-transfer chain, protected harm, risk standard, jurisdiction, governing legal source, procedure, exception, and remedy are identified the center of the account. A claim should name the carrier, the governing operation or relation, the applicable assumptions, and the recognition test. A bare label is insufficient because the name Non-refoulement can be used for a formal identity, an implementation, or a neighboring result unless carrier and convention are stated.
Manages Complexity¶
Without the abstraction, an analyst must reason directly over many local details: the carrier roles, admissibility assumptions, competing conventions, derived invariants, boundary cases, and proof or validation obligations specific to Non-refoulement. Non-refoulement compresses them into the roles in the structural signature. That compression permits comparison across instances without erasing the variables that determine validity. It also exposes which details may be varied safely and which are constitutive.
Abstract Reasoning¶
- Identify the carrier. State what the elements, states, objects, or observations are: the typed international refugee and human rights law carrier, defining objects and relations, parameters, conventions, evidence, boundary cases, and comparison targets. Reject examples whose alleged carrier belongs to a different problem. 2. Lock the constitutive rule. Express person, transferring authority, destination and onward-transfer chain, protected harm, risk standard, jurisdiction, governing legal source, procedure, exception, and remedy are identified independently of one notation or implementation.
Knowledge Transfer¶
Knowledge transfers strongly among subfields of international refugee and human rights law because they reuse the typed international refugee and human rights law carrier, defining objects and relations, parameters, conventions, evidence, boundary cases, and comparison targets, Authorities assess destination risk, personal circumstances, chain transfer, jurisdiction, applicable instrument, procedural safeguards, and any legally available exception before removal., and type the carrier, state every parameter and convention in the definition, test that person, transferring authority, destination and onward-transfer chain, protected harm, risk standard, jurisdiction, governing legal source, procedure, exception, and remedy are identified, compare the nearest accepted identity, and report counterexamples, uncertainty, and limiting cases.
Relationships to Other Abstractions¶
Current abstraction Non-refoulement Domain-specific
Parents (1) — more general patterns this builds on
-
Non-refoulement is a kind of Rights vs. Freedoms Prime
The proposed strict upward parent is
prime:rights_vs_freedoms.
Hierarchy paths (2) — routes to 2 parentless roots
- Non-refoulement → Rights vs. Freedoms → Normativity → Constraint
- Non-refoulement → Rights vs. Freedoms → Authority
Neighborhood in Abstraction Space¶
Non-refoulement sits in a crowded region of the domain-specific corpus (37th percentile for distinctiveness): several abstractions share nearly its structure, so a description that fits it tends to fit its neighbors too.
Family — Legal Interpretation & Doctrine (45 abstractions)
Nearest neighbors
- Equality before the law — 0.92
- Linguistic rights — 0.91
- Alien (law) — 0.90
- Partial agreement — 0.90
- Substantive equality — 0.90
Computed from structural-signature embeddings · 2026-09-08