Skip to content

Site

Prime #
1075
Origin domain
Philosophy
Subdomain
spatial and relational ontology → Philosophy

Core Idea

A site is a defined region or position whose identity is given by its capacity to host or contain entities, not by being a material object itself. The site exists as a slot in a larger structure, and what sits in the slot can change without changing the slot. Three coupled commitments travel with the pattern. Independent existence: the site persists when empty — a parking space is still a parking space with no car in it, a network port is still the port with no service bound to it. A hosting condition: the site has a specified rule about what it can contain — a shape, a capacity, an interface, a credential — and that rule is a structural feature of the site, not of the occupant. And persistent identity across occupants: occupants come and go, but the site's identity, address, and rules survive the turnover, so that a seat in a deliberative body outlives any member and a memory address outlives any value stored there.

A site is therefore not a thing in the ordinary sense; it is the location-shape that a thing can fit into. Physical sites — a niche, a parking space, a socket — are the most intuitive cases, but the pattern is fully present in non-spatial substrates: organizational positions, mount points, network ports, configuration slots, seats at a table, lots in a zoning code. The cost of the pattern is forward design: the system must commit to the slot's interface before knowing all its occupants. The payoff is interchangeability — occupants can be replaced, upgraded, or scheduled into and out of the slot without disturbing anything that addresses the slot from outside.

How would you explain it like I'm…

The Parking Spot

A Site is like a parking spot painted on the ground. The spot stays there even when no car is parked in it, and it's still that same spot when a new car pulls in. It's a place that's ready to hold something.

A Slot That Stays

A Site is a spot that exists to hold something, not the thing itself. Think of a chair at the dinner table: the chair is still your chair even when you're not sitting in it, and a guest can sit there tonight without changing whose chair it is. The Site has rules about what fits — a parking space is sized for one car — and those rules belong to the spot, not to whoever uses it. People or things come and go, but the spot stays put.

The Slot That Outlives Its Occupant

A Site is a defined slot in a bigger structure whose identity comes from its capacity to host something, not from being a physical object. Three things travel together: it keeps existing while empty (an empty parking space is still a parking space), it has a rule about what can occupy it (a shape, a size, a required key or interface), and its identity survives as occupants swap in and out. Unlike the occupant, which is a real thing, the Site is the location-shape the occupant fits into. A seat in a parliament outlives every member who has ever held it; a memory address outlives every value stored there.

 

A Site is a region or position whose identity is given by its capacity to host or contain entities, rather than by being a material object. It functions as a slot within a larger structure, and the occupant of the slot can change without changing the slot. Three coupled commitments define it. Independent existence: the Site persists when empty — a network port is still that port with no service bound to it. A hosting condition: the Site specifies what it can contain (a shape, a capacity, an interface, a credential), and that rule is a structural feature of the Site, not of the occupant. And persistent identity across occupants: the address and rules survive turnover. The cost of this pattern is forward design — you must commit to the slot's interface before knowing all its occupants. The payoff is interchangeability: occupants can be replaced, upgraded, or scheduled in and out without disturbing anything that addresses the slot from outside. The pattern is fully present in non-spatial substrates: organizational positions, mount points, configuration slots, lots in a zoning code.

Structural Signature

the addressable position (slot) — its independent existence when empty — the hosting condition (rule about admissible occupants) — the interchangeable occupant — the persistent identity across occupant turnover — the separation of where-something-is from what-is-there

The pattern is present when each of the following holds:

  • An addressable position. A defined region or position is a first-class entity with its own identity and address — a slot in a larger structure — rather than a material object.
  • Independent existence. The position persists when empty: a parking space with no car, a port with no bound service, a memory address with no value. If the identity dissolves when vacated, what is in view is an occupant, not a site.
  • A hosting condition. A rule specifies what the position can contain — a shape, capacity, interface, or credential — and this rule is a structural feature of the position, not of any occupant. A region with no specified hosting rule is not a site.
  • An interchangeable occupant. Something can sit in the position, but what sits there can change without changing the position.
  • Persistent identity across occupants. Occupants come and go while the position's identity, address, and rules survive the turnover — a seat outlives any member, an address outlives any stored value.
  • The where/what separation invariant. The position is promoted to a first-class entity separate from any occupant, so "what positions does the system have?" (structural) is decided independently of "who is in them now?" (operational). This is what makes interchangeability, succession, capacity planning, and anonymous addressing possible.

The three-question test — survives emptiness? hosting rule belongs to the slot? occupant changeable while address stays fixed? — discriminates a site from a material object, a transient assignment, or a one-off arrangement. The pattern's cost is forward design (commit the interface before knowing all occupants); its payoff is interchangeability.

What It Is Not

  • Not dimension. A dimension is an axis along which positions are measured; a site is a single addressable position with a hosting rule and an occupant. Dimensions are the coordinate system; a site is one slot located within it, with structure a bare coordinate lacks.
  • Not containment. Containment is one region enclosing another; a site is an occupiable position with persistent identity whose hosting rule and address survive turnover. A container can move with its contents and dissolve when emptied; a site persists vacant and is addressed independently of any occupant.
  • Not allocation. Allocation is the act of assigning a resource to a recipient; the site is the standing position into and out of which occupants are allocated. Allocation is the operational placement; the site is the structural slot it places into.
  • Not a role. A role is a sociological specialization of the site pattern — an occupiable position with normative expectations layered on. The bare site has a hosting rule but no duties; a role adds the behavioral expectations the plain position lacks.
  • Not discretion. Discretion is latitude in how an agent decides; a site is a persistent addressable position. The embedding proximity is incidental — there is no structural overlap between decision-latitude and occupiable-slot.
  • Not idempotence. Idempotence is an operation-property (repetition yields the same result); a site is a structural position. The two share no role-set; the proximity is an artifact of co-occurring in technical substrates.
  • Common misclassification. Reifying an ambient context, setting, or region into a site. The catch is the three-question test: a region with no specified hosting rule and no identity when empty is ambient background, not a site — dressing it as one manufactures a hosting rule and an occupant where there is only diffuse surroundings.

Broad Use

The pattern recurs wherever a system is organized around persistent, addressable positions whose occupants are interchangeable. In ecology, a niche is a site defined by what an organism would do there — its resource use, its position in the web — independent of whether any species currently occupies it, which is why niche vacancy and niche invasion are intelligible. In software architecture, ports, file descriptors, memory addresses, plugin slots, and mount points are occupiable positions a program addresses without knowing the current occupant. In organizational structure, offices carry duties, powers, and accountabilities that persist across holders, so that transitions are succession events between the same office and a new occupant. In the built environment, parking spaces, beds, plots, seats, and gates are engineered as grids of slots, and logistics works on the slot rather than whoever is in it. In civic geography, postal addresses, zoning lots, precincts, and districts are sites whose occupants turn over independently of the slot. In hardware, sockets and bays guarantee, through fixed geometry, that a compatible component can be swapped without redesigning the surrounding system. Across all of these the slot is addressed and the occupant is incidental.

Clarity

The pattern is sharp because all three commitments are operational and observable. Is there an identity that survives the slot being empty? — yes for a site, no for an occupant. Is the hosting rule a property of the slot rather than of any current occupant? — yes for a site. Can the occupant change while the slot's address stays the same? — yes for a site. If any one of these fails, what is in view is a material object, a transient assignment, or a one-off arrangement, not a site. This three-question test is what prevents over-extending the pattern to every edge or region: a region with no specified hosting rule, or one whose identity dissolves when vacated, is not a site. Naming the pattern thus converts a vague sense that "this is a place where things go" into a precise structural specification — a persistent, addressable position with an explicit hosting rule — and makes the characteristic confusions (treating a container that moves with its contents as a site, or treating an ambient context as a site) diagnosable as failures of one of the three commitments.

Manages Complexity

Sites let a designer separate two questions that would otherwise have to be answered together: what positions does the system have? and who is in them right now? The first is a structural question, decided by the system's architect or evolved into its shape; the second is an operational question, decided by schedulers, biology, hiring, networking, or market dynamics. Without the separation, every change of occupant would require re-deciding the structure; with it, structure can be designed, audited, and reasoned about independently of any particular occupant. This separation is what makes interchangeability, succession planning, capacity planning, and anonymous addressing possible — a dispatcher schedules units into slots without knowing their occupants, a kernel routes to a port without knowing the bound program, an ecosystem absorbs the loss of one species into a niche another may then fill. By promoting the position to a first-class entity with its own identity, address, and rules, the pattern absorbs the complexity that would otherwise arise from coupling structure to occupancy, and lets the system reason about its capacity and its vacancies as standing facts rather than re-deriving them from whoever happens to be present.

Abstract Reasoning

Sites are members of a position-occupant family of patterns that separates where something is from what is there. The family includes the role (a position defined by expected behaviors in a social structure), the slot or field (a position in a data structure), the socket (a position in a hardware or network interface), the seat (a position in a deliberative body), and the niche (a position in an ecological web). The shared structural move is to promote the position to a first-class entity with its own identity, address, and rules, separate from any occupant. Reasoning with sites licenses diagnostic questions that property-on-object reasoning cannot frame: which slots are currently empty, what is the system's capacity, can occupants be swapped without breaking external references, and what becomes of the slot when its occupant departs. These questions transfer cleanly across substrates because the slot structure is the same shape wherever it appears, and they support inference about interchangeability and capacity that is invisible if one reasons only about the occupants. A reasoner who sees the family can also place a given case within it — recognizing, say, a social role as a sociological specialization of site, with normative expectations layered on the bare occupiable-position structure.

Knowledge Transfer

A reader who recognizes the pattern in one substrate gains transferable diagnostics for others, because the same checklist works wherever the position-with-persistent-identity-and-hosting-rule shape appears. From an organizational chart: does this duty travel with the office or with the person? From a network diagram: does this address belong to a port or to the service currently bound to it? From an ecological account: is this niche defined by what fills it or by what would fill it? From a facility: what is the slot's capacity rule, and how does the system handle oversubscription? The same questions produce structurally comparable answers in each case, and the interventions they license — succession planning, capacity expansion, admission control, interchangeable-component design — port across substrates with only the slot's content changing. The deepest carry is the separation of structure from occupancy itself: a practitioner who has learned, in one domain, to address the slot rather than the occupant — to schedule, account, and audit against the bed, the port, the office, the niche — carries that discipline directly into every other, because the payoff (occupants become replaceable without disturbing external references) and the cost (the interface must be committed before the occupants are known) are the same regardless of whether the occupant is a patient, a process, a post-holder, or a species. Treating a single ecological niche, a single network port, or a single office as the only name for the pattern loses exactly this cross-substrate transfer; recognizing all of them as instances of the same site structure preserves it.

Examples

Formal/abstract

A network port is the site in its purest, fully formal substrate — non-spatial, yet exhibiting every commitment exactly. The addressable position is a port number on a host: a first-class, addressable slot in the host's transport-layer structure, identified independently of any program. Independent existence holds — port 443 is a defined position whether or not any service is bound to it; the slot persists when empty, and a connection attempt to an unbound port yields a definite "nothing here," which is a property of the empty slot, not of an occupant. The hosting condition is the binding rule: the position admits one bound listener (under a given protocol and binding mode), a structural feature of the port, not of any program. The interchangeable occupant is the service: one server process can be stopped and another bound to the same port without changing the port. Persistent identity across occupants is the load-bearing payoff — the port number outlives any particular service, so clients address :443 and reach whatever is currently bound, exactly as a memory address outlives any value stored there. The where/what separation invariant is what makes this work: "what ports does this host expose?" (structural) is decided independently of "what is bound to each right now?" (operational). The three-question test discriminates cleanly: the port survives emptiness (yes), the binding rule belongs to the slot (yes), and the occupant can change while the address stays fixed (yes) — so it is a site, not an occupant. The cost is forward design (the port assignment is committed before the services are known); the payoff is interchangeability (a service can be upgraded or replaced behind a stable address).

Mapped back: The network port instantiates every role — addressable position, independent existence when unbound, a binding hosting rule, an interchangeable bound service, persistent identity across rebindings — and the where/what separation is exactly what lets clients address a stable port while the service behind it is swapped.

Applied/industry

Two cases run the identical position-occupant structure on substrates a port shares nothing with. In organizational design, an office is a site: the addressable position is the office (a chief-executive role, a board seat), a first-class entity with its own identity, duties, and powers. Independent existence holds — the office persists when vacant, which is precisely why an interregnum is intelligible and why "the office is unfilled" is a coherent state. The hosting condition is the eligibility rule (credential, election, appointment) that admits an occupant; the interchangeable occupant is the office-holder; and persistent identity across occupants is what makes succession a transition between the same office and a new holder rather than the creation of a new role. The diagnostic question the prime supplies — does this duty travel with the office or with the person? — is the operational test that keeps duties attached to the slot. In facility and logistics management, a hospital bed (or a parking space, a shipping slot) is a site: the position is the bed, addressed by a fixed identifier; independent existence holds (the bed exists empty); the hosting condition is its capacity and care-level rule; the occupant is the patient; and persistent identity lets the system schedule, account, and audit against the bed rather than whoever occupies it. The interventions the prime licenses are the same in both: succession planning and capacity planning are the office case and the bed case of one move — reasoning about vacancies and turnover as standing facts about the slots, decided independently of current occupants. A manager who has learned to address the slot rather than the occupant — to plan against the office, the bed, the port — carries that discipline directly across, because the payoff (occupants replaceable without disturbing external references) and the cost (the interface committed before occupants are known) are identical regardless of whether the occupant is a post-holder, a patient, or a process.

Mapped back: The office and the hospital bed span organizational and facility substrates; in each, a persistent addressable position with a hosting rule survives occupant turnover, and succession planning and capacity planning are the same where/what-separation intervention the prime makes portable.

Structural Tensions

T1 — Site versus Occupant (coupling). The defining test is whether identity survives emptiness — a site persists vacant, an occupant does not. The two are routinely conflated, especially when one occupant has held a slot so long it seems to be the slot. The failure mode is treating a long-tenured occupant as the site (so duties leave with the person) or a movable container as a site (so the address travels with the contents). Diagnostic: ask whether the identity and address survive the current occupant's departure; if removing the occupant dissolves the position, it was never a site, and reasoning about vacancy, succession, or interchange does not apply.

T2 — Forward Interface Commitment versus Unknown Occupants (temporal). The payoff of interchangeability requires committing the hosting rule before all occupants are known — but a rule fixed too early may not fit occupants that arrive later, while a rule left too loose admits incompatible occupants. The interface is a bet placed under uncertainty. The failure mode is a slot whose committed shape excludes the occupant you later need, forcing a redesign of everything addressing the slot. Diagnostic: ask how stable the population of future occupants is; where it is unpredictable, an over-specified hosting condition is a liability, and the forward-design cost the prime names may exceed the interchangeability payoff.

T3 — Capacity versus Occupancy (scalar). The where/what separation lets "what positions exist?" be answered independently of "who is in them?" — but the two must be reconciled, and a system that reasons only about slots can plan capacity that occupants never fill, or oversubscribe slots beyond real capacity. The structural and operational views can drift apart. The failure mode is capacity planning against nominal slots that ignores whether occupants can actually be placed (a ward of beds with no staff, ports with no services). Diagnostic: periodically reconcile the slot inventory against actual occupancy; a standing count of positions is only useful if occupants can be matched to them, and slot-count divorced from fill-rate misleads.

T4 — Hosting Rule on the Slot versus on the Occupant (scopal). The prime insists the hosting condition is a structural feature of the site, not of any occupant — but in practice admission rules migrate to the occupant (a credential the holder carries) or get negotiated per-occupant, eroding the clean slot-owned interface. The failure mode is a site whose hosting rule has quietly become occupant-specific, so interchangeability fails because each occupant brings its own fit. Diagnostic: ask whether a new, compliant occupant can be dropped in using only the slot's published rule; if placement requires per-occupant negotiation, the hosting condition has leaked onto occupants and the slot is no longer a true interchangeable site.

T5 — Persistent Address versus Stale Binding (temporal). Persistent identity across occupants is the payoff, but it creates a hazard: external references address the slot expecting a current occupant, and a slot whose occupant has departed still resolves — to nothing, or to a successor the referrer did not intend. The stable address outlives the binding that made it meaningful. The failure mode is addressing a port, seat, or office and reaching an empty slot or an unexpected new occupant, with the caller assuming continuity. Diagnostic: ask what a reference to the slot gets when the occupant has changed or left; a stable address guarantees the position, not the occupant, and code or process that conflates the two will silently mis-reach.

T6 — Real Site versus Ambient Context (measurement). The three-question test guards against over-extension, but the boundary is genuinely contestable: is a "context," a "setting," or a "region" a site with a hosting rule, or just an ambient background with no slot structure? Over-applying the pattern reifies every vague place into an addressable position. The failure mode is modeling an ambient context as a site, manufacturing a hosting rule and an occupant where there is only diffuse surroundings. Diagnostic: demand a specified hosting condition and a persistent address before granting site-hood; a region with no rule about what it admits and no identity when empty is ambient context, and dressing it as a site adds structure that is not there.

Structural–Framed Character

The site sits at the pure-structural pole of the structural–framed spectrum, an aggregate of 0.0 with every diagnostic structural. It is a bare relational pattern — a position that persists when empty, carries a hosting rule about what it admits, and keeps its identity across the turnover of occupants — and it applies fully to non-human substrates.

The diagnostics line up. The pattern carries no home vocabulary that must travel with it: the same location-shape describes an ecological niche, a parking space, a network port, a memory address, a mount point, and a seat in a deliberative body, each told in its own field's words, so vocab_travels is 0. It carries no inherent approval or disapproval — a slot is neither good nor bad until you specify what fills it — so evaluative_weight is 0. Its origin is formal and relational, with no appeal to any institution; a niche is a site by nature, not by decree, so institutional_origin is 0. It runs in physical and biological substrates indifferently — a port hosts a service, a niche hosts an organism, with no human practice required — so human_practice_bound is 0. And invoking it RECOGNIZES a hosting structure already present (the slot, its rule, its persistent address) rather than importing any interpretive frame, so import_vs_recognize is 0. The interchangeability payoff — occupants swapped without disturbing whatever addresses the slot from outside — is a structural fact about the substrate, not an imported reading; the pure-structural label is exactly right.

Substrate Independence

Site is about as substrate-independent as a prime can be — composite 5 / 5 on the substrate-independence scale. Its signature is a bare relational pattern — a persistent addressable position that survives emptiness, carries a hosting rule about what it admits, and keeps its identity across occupant turnover — stated in purely relational vocabulary with no commitment to any medium, so the where/what separation is recognized rather than translated wherever it appears, which earns the maximal structural-abstraction mark. The domain breadth is maximal and the same location-shape recurs in ecology (a niche defined by what would fill it), software architecture (ports, file descriptors, memory addresses, plugin slots, mount points), organizational structure (offices outliving their holders), the built environment (parking spaces, beds, plots, gates), civic geography (postal addresses, zoning lots, precincts), and hardware (sockets and bays guaranteeing swappable components). Transfer evidence is strong though slightly below maximal at 4: the network port, the organizational office, and the hospital bed demonstrably share the three commitments and the same succession-and-capacity-planning interventions, the where/what separation carrying intact across them. Because the pattern carries no evaluative or institutional load — a niche hosts an organism and a port hosts a service with no human practice required — the remaining components read 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 — 4 / 5

Relationships to Other Primes

One-hop neighborhood: parents above, mutual partners to the right, children below.Sitesubsumption: RoleRole

Foundational — no parent edges in the catalog.

Children (1) — more specific cases that build on this

  • Role is a kind of, typical Site

    The file states a role is 'a sociological specialization of the site pattern — an occupiable position with normative expectations layered on'. The bare site has a hosting rule but no duties; a role adds the behavioral expectations. Site is the more-general parent. Additive: role keeps its social_cultural lineage; add potential_occupancy_region as an additional parent.

Neighborhood in Abstraction Space

Site sits in a sparse region of abstraction space (61st percentile for distinctiveness): few abstractions share its structure, so a faithful description tends to retrieve it precisely rather than landing on a neighbor.

Family — Identity, Reference & Placeholders (10 primes)

Nearest neighbors

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

Not to Be Confused With

The embedding-nearest neighbor, dimension (similarity 0.81), is a confusion of a coordinate system with a single occupiable position. A dimension is an axis along which positions are measured — it supplies the space within which locations can be specified, but it is not itself a location, has no hosting rule, and admits no occupant. A site is one addressable slot, with three commitments a dimension entirely lacks: it persists when empty, it carries a rule about what it admits, and its occupant can change while its address stays fixed. The relationship is that sites are located within a dimensional space (a parking grid uses spatial dimensions, a port number is a position in an address space), but the dimension is the measuring framework and the site is a structured point in it. Conflating them leads a modeler to treat a mere coordinate as if it had hosting structure (expecting a bare position to admit and exclude occupants), or to treat a genuine site as if it were just a coordinate (losing the hosting rule and persistent identity that make interchangeability and succession reasoning possible).

The most substantive confusion is with containment. Both involve something being "inside" something else, and a container can look like a slot that holds an occupant. The decisive differences are persistence-when-empty and address-independence. Strict containment is a relation between a container and its contents that often moves with the contents and may have no identity apart from them — empty the container and, in many cases, the relation lapses. A site is defined precisely by surviving emptiness: a parking space with no car, a port with no service, an office with no holder all remain fully themselves, addressable and rule-bearing, with the occupant incidental. Tension T1 makes this the prime's defining test — identity survives the occupant's departure for a site, not for a mere container or occupant. The practical hazard of conflating them is treating a movable container as a site (so the address wrongly travels with the contents) or treating a site as mere containment (so reasoning about vacancy, succession, and interchangeability — all of which require the slot to outlive its occupant — never gets framed).

A third confusion is with allocation, and it is a confusion of the standing structure with the operational act. Allocation is the assignment of a resource or share to a recipient — the placement event. A site is the persistent position into and out of which such allocations happen. The prime's whole contribution is the where/what separation: "what positions exist?" (the site inventory, structural) is decided independently of "who is allocated to each right now?" (the operational placement). Allocation answers the second question; the site furnishes the first. Confusing them collapses the separation that makes capacity planning possible — one ends up reasoning only about current assignments and loses the standing fact of the slots themselves, so vacancies, oversubscription, and interchangeability (which are facts about sites, not about any allocation) become invisible. The dispatcher who can only think in allocations cannot ask how many beds, ports, or offices exist independent of who currently fills them.

These distinctions matter because each protects a different commitment. Holding the site apart from dimension keeps it a structured, rule-bearing, occupiable position rather than a bare coordinate. Holding it apart from containment preserves the survives-emptiness and address-independence tests that license vacancy and succession reasoning. And holding it apart from allocation preserves the where/what separation, so the standing inventory of positions stays distinct from the operational record of who currently occupies them — which is exactly what makes capacity planning, interchangeable-component design, and anonymous addressing possible.

Solution Archetypes

No catalogued solution archetypes reference this prime yet.