Skip to content

Located-In Relation

Prime #
968
Origin domain
Biology & Ecology
Subdomain
mereotopology and containment → Biology & Ecology

Core Idea

A located-in relation says that one entity is situated within the region of another: an organ within a body cavity, a component within a subassembly, a person within a room, a subsidiary within a jurisdiction, a variable within a lexical scope. The relation is not parthood — the located thing need not be constitutive of the location, as a foreign body within a tissue is located in it but is no part of it — and it is not mere adjacency, since something can border a region without being inside it. It is the more general claim that "this thing's place is within that thing's region," where the region may be spatial, contextual, organizational, jurisdictional, or scoping. The structural commitments are four: a locatum, the entity being located; a location, the entity whose region contains it; an inclusion region, the specific region of the location within which the locatum sits; and a relation-time, the interval over which the relation holds. The last is essential and easily forgotten: located-in is not eternal — the person leaves the room, the subsidiary re-incorporates, the variable falls out of scope — so the relation is always indexed to a time.

What makes this a distinct relational primitive rather than a loose sense of "in" is the explicit separation from its mereotopological neighbors. Parthood, strict containment, located-in, and adjacency are four different relations with four different inference rules, and reasoning breaks when they are conflated. The located-in relation is precisely the inside-of relation shorn of any claim that the locatum is part of, or permanently enclosed by, the location — which is why it can hold transiently and asymmetrically, and why "where" becomes a substrate-independent question answered by substrate-dependent machinery.

How would you explain it like I'm…

Cat in the Box

When you say the cat is in the box, you mean the cat's spot is inside the box's space, even though the cat is not a piece of the box and can climb out later. Located-In Relation is just saying where something is by telling which thing's space it sits inside right now.

Inside, Not Part Of

A Located-In Relation says one thing is sitting inside the region of another thing, like a person in a room or a toy in a drawer. It is not the same as being a part of it: a splinter in your finger is inside your finger but is not a part of you. It is also more than just being next to something, because you can be beside a room without being inside it. And it is not forever: the person walks out of the room later, so this relation always comes with a time when it is true. Four things matter: the thing being located, the thing it is inside, the exact region it sits in, and the time.

Where-It-Sits, For Now

A Located-In Relation says one entity is situated within the region of another: an organ within a body cavity, a person within a room, a subsidiary within a jurisdiction, a variable within a lexical scope. It is not parthood, since the located thing need not be constitutive of the location (a foreign body in tissue is located in it but is no part of it), and it is not mere adjacency, since something can border a region without being inside it. It is the more general claim that this thing's place is within that thing's region, where the region may be spatial, contextual, organizational, jurisdictional, or scoping. Four commitments fix it: a locatum (the thing being located), a location (whose region contains it), an inclusion region (the specific region it sits in), and a relation-time (the interval over which it holds). The time is essential and easily forgotten, because located-in is not eternal: the person leaves the room, the variable falls out of scope. Keeping it distinct from parthood, strict containment, and adjacency matters, since each has different inference rules and reasoning breaks when they are conflated.

 

A located-in relation says that one entity is situated within the region of another: an organ within a body cavity, a component within a subassembly, a person within a room, a subsidiary within a jurisdiction, a variable within a lexical scope. The relation is not parthood (the located thing need not be constitutive of the location, as a foreign body within a tissue is located in it but is no part of it) and it is not mere adjacency (something can border a region without being inside it). It is the more general claim that this thing's place is within that thing's region, where the region may be spatial, contextual, organizational, jurisdictional, or scoping. The structural commitments are four: a locatum, the entity being located; a location, the entity whose region contains it; an inclusion region, the specific region of the location within which the locatum sits; and a relation-time, the interval over which the relation holds. The last is essential and easily forgotten: located-in is not eternal (the person leaves the room, the subsidiary re-incorporates, the variable falls out of scope), so the relation is always indexed to a time. What makes this a distinct relational primitive rather than a loose sense of in is the explicit separation from its mereotopological neighbors. Parthood, strict containment, located-in, and adjacency are four different relations with four different inference rules, and reasoning breaks when they are conflated. Located-in is precisely the inside-of relation shorn of any claim that the locatum is part of, or permanently enclosed by, the location, which is why it can hold transiently and asymmetrically.

Structural Signature

the locatum (entity being located) — the location (entity whose region contains it) — the inclusion region — the relation-time interval — the within-not-part-of inclusion test — the separation from parthood, strict containment, and adjacency

The pattern is present when each of the following holds:

  • A locatum. Some entity is the thing being located — an organ, a component, a person, a subsidiary, a variable.
  • A location. Some entity whose region the locatum sits within — a cavity, a subassembly, a room, a jurisdiction, a scope.
  • An inclusion region. The specific region of the location within which the locatum sits; the inclusion-region test is decided by substrate-dependent machinery (geometric containment, set membership, scope rules, tenancy).
  • A relation-time. An interval over which the relation holds. This is essential and easily forgotten: located-in is not eternal — the person leaves the room, the subsidiary re-incorporates, the variable falls out of scope — so the relation is always indexed to a time.
  • The within-not-part-of invariant. The locatum's place is within the location's region without the locatum being part of, or strictly contained by, the location. This is the load-bearing distinction: a foreign body within a tissue is located in it but no part of it, so inferences valid for parthood (transitivity, permanence, constitution) are invalid here.

The relation is one of four mereotopological neighbors with distinct inference rules — parthood (constitutive belonging), strict containment (mereological enclosure), located-in (within-a-region-at-a-time), and adjacency (bordering without inclusion) — and reasoning breaks when they are conflated. Each missing commitment yields a determinate error: a missing relation-time gives stale-location bugs; located-in-as-parthood gives the transient-occupant-mistaken-for-part error; located-in-as-adjacency gives the bordering-mistaken-for-containment error.

What It Is Not

  • Not a bare relation. A relation is any structured tie between relata; located-in is the specific mereotopological relation of within-a-region-at-a-time, with its own inference rules (no transitivity into parthood, time-indexed, non-constitutive). The generic relation carries none of these constraints.
  • Not parthood (a use of composition). Parthood is constitutive belonging — the part is part of the whole, transitively and constitutively; located-in's locatum is within the location's region without being part of it. A gallstone is located in the gallbladder but is no part of it.
  • Not containment in the strict sense. Strict containment is mereological enclosure of one region by another; located-in does not require the locatum to be enclosed or constitutive, only situated within a region. The two have different permanence and constitution entailments.
  • Not boundary or adjacency. A boundary or adjacency relation has things bordering without inclusion; located-in requires the inclusion-region test to pass. Bordering a region is not being inside it, and conflating them grants false access or jurisdiction entailments.
  • Not dimension. Dimension concerns the axes along which a space is measured; located-in concerns position within a region of a location at a time. One is about the coordinate structure; the other about a within-relation indexed to an interval.
  • Not allocation. Allocation assigns a resource or share to a recipient; located-in merely situates an entity within a region. Being located in a place is not being allocated to it — the relation carries no distributive or assignment content.
  • Common misclassification. Over-extending "in" to any relationship that connects two things — the user likes the venue, the subsidiary trades with the jurisdiction. The catch is the inclusion-region test: if the candidate only borders, associates with, or relates to the location without satisfying inclusion at the relevant time, it is not located-in and the relation's entailments do not fire.

Broad Use

The four commitments recur across substrates with the inclusion-region test decided differently in each. In biological modeling, organs are located in cavities, cells in tissues, molecules in organelles, pathogens in host tissues, and the relation is given formal semantics distinct from parthood and strict containment precisely because conflating them corrupts anatomical reasoning. In engineering, components are located in subassemblies without being permanent parts of them — removable, replaceable, transferable. In geographic and political modeling, settlements are located in countries, properties in jurisdictions, events at venues, and topological predicates of within and contains are first-class. In legal and organizational modeling, subsidiaries are located in jurisdictions, assets in trusts, cases in courts, each with consequences (tax treatment, governing law, regulatory regime) that depend on the relation holding at the relevant time. In computing, variables are located in scopes, processes in containers, files in directories, rows in partitions, users in tenants. In cognitive and social settings, people are located in conversations, meetings, and contexts, and reasoning about who can access or affect what often reduces to "where are they, and what does being located there entail?" In every case the substrate machinery varies; the four-commitment abstraction is constant.

Clarity

The pattern is sharp at its operational test: for a given locatum and putative location at a given time, is the locatum's place within the location's region? The test is decidable substrate by substrate — geometric containment, set membership in a jurisdiction, scope rules in a programming language, membership in a cost center — and the pattern is bright at its edges, because failure of any of the four commitments is recognizable. A missing relation-time produces the classic error of asserting a location that was true only until some date and is now stale. Treating located-in as parthood produces the anatomical and engineering errors where a transient occupant is mistaken for a constitutive part. Treating it as adjacency produces the geographic and access-control errors where bordering is mistaken for containment. Naming the relation thus disciplines reasoning: loose associations — the user likes the venue, the subsidiary trades with the jurisdiction — do not instantiate located-in, because they fail the inclusion-region test, and the pattern is exactly the discipline that prevents over-extending "in" to any relationship that merely connects two things.

Manages Complexity

Real systems contain many entities, and without a located-in relation every interaction must be reasoned about from first principles. With it, vast amounts of structural reasoning collapse into location lookups whose answers constrain everything downstream. Tax law uses jurisdictional location to determine treatment; anatomy uses location to predict the diffusion of a signal or the reach of a therapy; programming uses scope to predict variable visibility; access control uses tenancy to authorize operations. In each, "where is it?" is a single query whose answer determines a large set of further facts, so that the relation acts as a hub through which much else is computed rather than re-derived. The relation also composes with time cleanly: because located-in is indexed to an interval, a system can record the history of an entity's locations and reason about what was true when — which jurisdiction governed at the moment of a transaction, which scope a closure captured at the moment of its creation — without confusing a past location for a present one. This time-indexing is what lets the relation manage the complexity of entities that move through regions rather than staying put.

Abstract Reasoning

Located-in is one of the basic mereotopological relations that any region-based ontology eventually distinguishes, and reasoning about a system requires identifying which of them is in play and applying its own inference rules. Parthood is structural belonging: the part is constitutive of the whole. Strict containment is mereological enclosure: the whole's region encloses the part's region without making it a part. Located-in is the locatum's place being within the location's region, at a time, with no parthood or strict-containment claim. Adjacency is borders touching without inclusion. These are not interchangeable, and the formal-ontology tradition spent decades disentangling them precisely because biological, medical, and engineering reasoning broke whenever they were collapsed — a tumor in a lung is located in it but not part of it, and inferences valid for parthood are invalid for located-in. The abstract payoff is that recognizing the relation lets a reasoner ask, of any "in" claim, which of the four relations is meant, and then apply only the inferences that relation licenses. This prevents the characteristic error of importing parthood's transitivity or permanence into a relation that has neither, and it makes "where" a tractable question with well-defined inference rather than an ambiguous one.

Knowledge Transfer

The four-commitment diagnostic transfers across substrates because it interrogates the relation rather than the domain. What is the locatum? What is the location? What region of the location does the locatum sit in? Over what interval does the relation hold? These four questions, asked of a body within a cavity, a component within an assembly, a subsidiary within a jurisdiction, a variable within a function, or a person within a room, produce the same kind of structural answer and surface the same kind of bug when an answer is missing. The transfer is mechanical, not analogical: a practitioner who has learned to demand a relation-time when modeling corporate domicile holds exactly the tool needed to avoid the stale-location bug in an anatomical model or a closure-capture analysis, because the missing commitment is the same in each. The deepest carry is the distinction from parthood, which is the load-bearing modeling move in every substrate the relation touches. Recognizing that a therapeutic agent is located in a target region but not part of it lets a modeler predict both its action (it acts where it is located) and its clearance (it leaves when the relation ceases to hold), and the identical structure governs a vehicle located in a garage (with consequences for access and billing), a body incorporated in one jurisdiction (with consequences for governing law until reincorporation), and a closure variable located in an outer scope (with consequences for what the closure can read during its lifetime). A reasoner who has internalized the non-parthood of located-in in one domain carries it intact into all the others, because the relation is the same and the inference rules it licenses are the same.

Examples

Formal/abstract

Biomedical anatomy ontologies give the relation its most rigorously formalized worked instance, precisely because conflating it with parthood corrupted reasoning until the relations were disentangled. Consider a gallstone located in the gallbladder. The locatum is the stone; the location is the gallbladder; the inclusion region is the organ's lumen, with the inclusion test decided by geometric containment; and the relation-time is the interval before the stone is passed or removed. The within-not-part-of invariant is the whole point: the stone is located in the gallbladder but is no part of it — it is not constitutive of the organ, did not develop with it, and leaves without diminishing it. This blocks exactly the inferences that parthood would license. Parthood is transitive (a part of a part is a part of the whole) and tends toward permanence and constitution; located-in is none of these. So from "the stone is located in the gallbladder" and "the gallbladder is part of the digestive system" one may say the stone is located in the digestive system's region, but one may not infer the stone is a part of the digestive system — the chain that would be valid for parthood is invalid here. The four mereotopological neighbors are kept distinct by their inference rules: a tumor located in a lung is not part of it (so resection logic differs from removing a lung lobe, which is a part); the pleura adjacent to the lung borders without inclusion. The relation-time commitment prevents the stale-location bug: an anatomical assertion true only during an episode must be indexed to that interval, or downstream reasoning will treat a transient occupant as a permanent fixture.

Mapped back: The gallstone-in-gallbladder case instantiates all four commitments — locatum, location, inclusion region, relation-time — and the within-not-part-of invariant is exactly what bars parthood's transitivity and permanence from corrupting the anatomical inference.

Applied/industry

Two practitioner cases run the identical four-commitment relation on substrates anatomy shares nothing with. In corporate and tax law, a subsidiary is located in a jurisdiction. The locatum is the subsidiary; the location is the jurisdiction; the inclusion region is the legal territory, with the inclusion test decided by incorporation and tenancy rules rather than geometry; and the relation-time is the interval until reincorporation. The within-not-part-of invariant matters: the subsidiary is located in the jurisdiction's regime without being a constitutive part of the state, so it can relocate, and the consequences — governing law, tax treatment, regulatory regime — depend on the relation holding at the relevant time, which is why the relation-time commitment is load-bearing. A model that omits the time index produces the stale-location bug in its costliest form: applying the governing law of a jurisdiction the entity has since left to a transaction, or vice versa. In programming-language semantics, a variable is located in a lexical scope. The locatum is the variable; the location is the scope (a function or block); the inclusion region is the lexical extent, with the inclusion test decided by scope rules; and the relation-time is the variable's lifetime — it falls out of scope, so the relation is not eternal. The within-not-part-of distinction governs closure capture: a closure captures variables located in an outer scope at the moment of its creation, and reasoning about what it can read depends on the relation holding during its lifetime, not on the variable being a permanent part of the closure. The same four questions — what is the locatum, what is the location, what region, over what interval — produce structurally comparable answers in a tax model and a closure-capture analysis, and the same missing commitment (relation-time) produces the same stale-location bug in both.

Mapped back: Corporate domicile and lexical scope span law and software; in each, the four-commitment relation indexes a within-a-region claim to a time interval, and the non-parthood invariant plus the relation-time index are what license correct inference about governing law or closure visibility while preventing the stale-location bug.

Structural Tensions

T1 — Located-In versus Parthood (coupling). The load-bearing distinction is that the locatum is within the location's region but not part of it, which bars parthood's transitivity, permanence, and constitution. The two relations are constantly conflated because "in" reads as both. The failure mode is importing parthood inferences — chaining transitivity, assuming permanence — into a relation that licenses none, so a transient occupant is reasoned about as a constitutive part. Diagnostic: ask whether the locatum is constitutive of the location (does removing it diminish the location?); if not, it is located-in, and parthood's inference rules are invalid.

T2 — Relation-Time versus Eternal Assertion (temporal). Located-in always holds over an interval — the person leaves, the subsidiary reincorporates, the variable falls out of scope — but assertions are routinely stored without a time index. The failure mode is the stale-location bug: applying a location that was true only until some date as if it were current, the costliest version being a transaction governed by a jurisdiction the entity has since left. Diagnostic: ask over what interval the located-in claim holds; a location asserted with no time index is a latent staleness bug, and the absence of relation-time is the single most common omission the prime names.

T3 — Located-In versus Adjacency (scopal). The relation requires the locatum to be within the region, not merely bordering it — adjacency touches without inclusion. The boundary is where the prime stops, and it is easy to over-extend "in" to anything that connects two things. The failure mode is treating bordering or association as containment, granting a locatum the consequences (access, jurisdiction, visibility) of being inside when it is only adjacent. Diagnostic: apply the inclusion-region test (geometric, set-membership, scope, tenancy); if the candidate only borders or relates to the location without satisfying inclusion, it is adjacency and the located-in entailments do not fire.

T4 — Substrate-Neutral Question versus Substrate-Specific Test (measurement). "Where is it?" is one abstract question, but the inclusion-region test is decided by wholly different machinery in each substrate — geometry, set membership, scope rules, tenancy. The abstraction can mislead if one substrate's test is silently applied to another. The failure mode is importing geometric intuitions (a thing is in exactly one place, containment is crisp) into a substrate where inclusion is non-geometric and can be multiple or fuzzy. Diagnostic: name the specific inclusion test for this substrate before reasoning; spatial intuitions about containment do not transfer to jurisdictional or scope inclusion without checking the actual rule.

T5 — Single Location versus Multiple Inclusion (scalar). Geometric containment suggests one location at a time, but in many substrates a locatum is located in several regions at once — a person in a room and in a jurisdiction and in an org unit, a subsidiary in overlapping legal regimes. The relation does not by itself say these are exclusive. The failure mode is assuming a unique location and missing a second inclusion with its own consequences (a second jurisdiction's tax claim, a second scope's visibility). Diagnostic: ask whether the locatum can be located in more than one location simultaneously at the relevant grain; if so, enumerate all inclusions, because each carries its own entailments and the salient one is not the only one.

T6 — Location as Hub versus Stale Cascade (coupling). The relation's power is that "where is it?" is one query whose answer determines a large downstream set of facts — tax, visibility, access, reach. But that leverage cuts both ways: if the location fact is wrong or stale, every fact computed from it is wrong in lockstep. The failure mode is a single mis-located entity silently corrupting a whole cascade of derived conclusions, because everything routed through the location hub inherits its error. Diagnostic: ask what downstream facts depend on this located-in assertion; the more that hang off it, the higher the cost of a stale or mistaken location, and the more the time-index and inclusion-test must be verified rather than assumed.

Structural–Framed Character

Located-in sits at the pure-structural pole of the structural–framed spectrum, an aggregate of 0.0 with every diagnostic reading structural. It is a mereotopological primitive — a locatum, a location, the inclusion region, and the relation-time over which the containment holds — shorn of any claim that the locatum is part of, or permanently enclosed by, the location.

Each diagnostic points one way. The pattern carries no home vocabulary that must travel with it: the same inside-of relation describes an organ within a body cavity, a component within a subassembly, a subsidiary within a jurisdiction, and a variable within a lexical scope, each stated in its own substrate's terms, so vocab_travels is 0. It carries no inherent approval or disapproval — that X is located in Y at time t is a neutral spatial fact — so evaluative_weight is 0. Its origin is formal, a relation defined purely by region-inclusion and time-indexing with no appeal to any institution, so institutional_origin is 0. It runs in physical and biological substrates indifferently — a foreign body is located in a tissue with no human practice involved — so human_practice_bound is 0. And invoking it RECOGNIZES a containment already obtaining in the world rather than importing an interpretive frame, so import_vs_recognize is 0. The relation's whole value is that "where is X?" becomes a substrate-independent question answered by substrate-dependent machinery; the pure-structural label is exactly right.

Substrate Independence

Located-in is about as substrate-independent as a prime can be — composite 5 / 5 on the substrate-independence scale. It is a mereotopological primitive — a locatum, a location, an inclusion region, and the relation-time over which the within-a-region claim holds — defined purely by region-inclusion and time-indexing with no commitment to any medium, so it is recognized rather than translated wherever it appears, which earns the maximal structural-abstraction mark. The domain breadth is maximal: the same inside-of relation holds for an organ within a body cavity (OBO RO located_in, biological anatomy), a component within an engineering subassembly, a settlement within a country (GIS topology), a subsidiary within a legal jurisdiction, a variable within a lexical scope and a process within a container (software), and a person within a meeting or conversation (social settings), with the inclusion-region test decided by whatever substrate-dependent machinery applies — geometry, set membership, scope rules, tenancy. Transfer evidence is correspondingly strong: the gallstone-in-gallbladder case, corporate domicile, and lexical-scope closure capture share not just the four commitments but the same within-not-part-of invariant and the same stale-location bug that follows from omitting the relation-time. Because the relation carries no evaluative or institutional load — a foreign body is located in a tissue indifferent to any human practice — every component reads at the ceiling, making this one of the catalog's canonical 5s.

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

Relationships to Other Primes

One-hop neighborhood: parents above, mutual partners to the right, children below.Located-In Relationsubsumption: RelationRelation

Parents (1) — more general patterns this builds on

  • Located-In Relation is a kind of Relation

    The file: located_in IS a relation but the SPECIFIC mereotopological within-a-region-at-a-time relation with its own inference rules (no transitivity into parthood, time-indexed, non-constitutive) the generic relation lacks.

Path to root: Located-In Relation → Relation

Neighborhood in Abstraction Space

Located-In Relation sits in a sparse region of abstraction space (95th percentile for distinctiveness): few abstractions share its structure, so a faithful description tends to retrieve it precisely rather than landing on a neighbor.

Family — Boundaries, Rules & Discretion (14 primes)

Nearest neighbors

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

Not to Be Confused With

The embedding-nearest neighbor is the bare relation (similarity 0.91), and the confusion is structural: located-in is a relation, so the temptation is to treat it as just one more link with nothing special about it. But a relation in the abstract imposes no inference rules — it is any tie between relata, of any arity, with no built-in constraints on transitivity, time-indexing, or constitution. Located-in adds exactly the constraints that make it useful and dangerous to misuse: it holds within a region, it is indexed to a time interval, and it is non-constitutive (the locatum is not part of the location). These three commitments license a precise inference profile — you may infer the locatum is within the location's larger region, but you may not infer parthood, permanence, or constitution — that a generic relation does not carry. The practical cost of collapsing located-in into bare relation is reasoning poverty in one direction and error in the other: a system that records only "X relates to Y" cannot answer "where is X at time t and what does that entail?", while a system that treats located-in as an unconstrained relation will chain it like parthood or assert it eternally, producing exactly the transitivity and staleness bugs the prime exists to prevent.

The deepest and most consequential confusion is with parthood, the relation the formal-ontology tradition spent decades disentangling from located-in (and which lives in the catalog as a use of composition). Parthood is constitutive belonging: the part is part of the whole, the relation is transitive (a part of a part is a part of the whole), and it tends toward permanence and constitution — removing the part diminishes the whole. Located-in claims only that the locatum's place is within the location's region, with none of these entailments. The canonical case is decisive: a tumor located in a lung, or a gallstone in a gallbladder, is located in it but is no part of it — not constitutive, not developed with it, leaving without diminishing it. From "the stone is located in the gallbladder" and "the gallbladder is part of the digestive system" one may say the stone is located in the digestive system's region, but one may not infer the stone is a part of the digestive system, because located-in does not chain through parthood's transitivity. Conflating the two imports parthood's inference rules into a relation that licenses none, which is precisely how anatomical, surgical, and engineering reasoning broke before the relations were separated — a transient occupant reasoned about as a constitutive component.

A third confusion is with strict containment. Containment in the strict mereotopological sense is enclosure of one region by another — the container's region fully encloses the contained region — and it can carry permanence and crispness intuitions (a thing is contained, fully, in exactly one container). Located-in is more general and more permissive: it requires only that the locatum sit within a region of the location, not that it be enclosed, and (tension T5) it explicitly allows a locatum to be located in several regions at once — a person in a room and a jurisdiction and an org unit simultaneously. Importing containment's single-location, crisp-enclosure intuitions into located-in (tension T4) is a real error, because in jurisdictional, scoping, and organizational substrates inclusion is non-geometric, can be multiple, and is not crisp. The practitioner who treats located-in as strict containment will assume a unique location and miss a second inclusion that carries its own consequences — a second jurisdiction's tax claim, a second scope's visibility.

These distinctions matter because each protects a different feature of the prime. Holding located-in apart from bare relation preserves its specific inference profile — within-a-region, time-indexed, non-constitutive. Holding it apart from parthood preserves the within-not-part-of invariant that bars transitivity, permanence, and constitution from corrupting the inference. And holding it apart from strict containment preserves the substrate-specific, possibly-multiple, time-indexed character of inclusion. In every case the discipline is the same: name the inclusion-region test, index the claim to a time, and refuse parthood's entailments.

Solution Archetypes

No catalogued solution archetypes reference this prime yet.