Skip to content

Site

Core Idea

A site is a defined position whose identity is its capacity to host, not its material substance: it persists when empty, carries a rule about what it admits, and keeps its identity as occupants turn over.

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.

Broad Use

  • Ecology: a niche, defined by what an organism would do there, intelligible whether or not any species fills it.
  • Software architecture: ports, memory addresses, plugin slots, and mount points — occupiable positions addressed without knowing the current occupant.
  • Organizational structure: an office carries duties and powers that persist across holders, so succession is one office and a new occupant.
  • Built environment: parking spaces, beds, and gates engineered as grids of slots that logistics works on regardless of who occupies them.
  • Civic geography: postal addresses, zoning lots, and precincts whose occupants turn over independently of the slot.
  • Hardware: sockets and bays whose fixed geometry guarantees a compatible component can be swapped without redesign.

Clarity

Lets you ask three sharp questions — does identity survive emptiness, is the hosting rule the slot's own, can the occupant change while the address stays fixed — that separate a site from a mere object or transient assignment.

Manages Complexity

Separates what positions exist (structural) from who fills them now (operational), so structure can be designed and audited without re-deciding it on every change of occupant.

Abstract Reasoning

Belongs to a position-occupant family — role, slot, socket, seat, niche — whose shared move is promoting the position to a first-class entity with its own identity and rules.

Knowledge Transfer

  • Organizations to networks: "does this duty travel with the office or the person?" becomes "does this address belong to the port or the bound service?".
  • Facilities to ecology: capacity-and-vacancy reasoning about beds ports the same way to a niche defined by what would fill it.
  • Across substrates: the discipline of addressing the slot rather than the occupant carries intact whether the occupant is a patient, a process, or a species.

Example

A network port persists whether or not a service is bound to it; the port number outlives any process, so clients reach :443 and get whatever is currently bound — the slot addressed, the occupant incidental.

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.

Not to Be Confused With

  • Site is not Dimension because a site is a single addressable position with a hosting rule, whereas a dimension is the axis along which positions are measured; the site is located within a dimensional space, not identical to it.
  • Site is not Containment because a site survives emptiness and is addressed independently, whereas a container often moves with its contents and may dissolve when emptied.
  • Site is not Allocation because a site is the standing position into and out of which occupants are placed, whereas allocation is the operational act of placing them.