Co-location¶
Core Idea¶
Co-location is the relation in which distinct entities, roles, or functions occupy the same bounded place during an overlapping time interval. It removes spatial separation without asserting that the co-located things interact, coordinate, share ownership, or form one unit. At least two distinguishable occupants, a stated spatial boundary, and temporal overlap are required. The relevant resolution must be explicit: two services may be co-located in one building but separated by rooms, networks, or security zones at a finer scale.
Broad Use¶
Molecules, sensors, workers, services, records, and biological functions instantiate the same place-and-time relation. The occupants and consequences change; the relation does not.
Clarity¶
Co-presence can be virtual or interactional and need not share physical location. Proximity permits nonzero separation. Integration combines functions. Centralization moves authority or resources toward one locus and can occur without literal co-location.
Manages Complexity¶
The abstraction turns a scattered family of cases into one role-based test: identify the required elements, test their relation, and reject the classification when a constitutive commitment is missing.
Abstract Reasoning¶
Use the structural signature rather than the label, then challenge the nearest counterexample. Two teams using the same online workspace from different continents are co-present in a mediated sense but not physically co-located unless a virtual-location convention is explicitly adopted.
Knowledge Transfer¶
Molecules, sensors, workers, services, records, and biological functions instantiate the same place-and-time relation. The occupants and consequences change; the relation does not.
Example¶
A case qualifies only when the definition and every load-bearing role remain present. Two teams using the same online workspace from different continents are co-present in a mediated sense but not physically co-located unless a virtual-location convention is explicitly adopted.
Relationships to Other Abstractions¶
Current abstraction Co-location Prime
Parents (1) — more general patterns this builds on
-
Co-location presupposes, typical Neighborhood Prime
Co-location typically presupposes a neighborhood when shared presence is defined by a focal region and proximity rule, though exact same-container cases need no tunable radius.
Children (4) — more specific cases that build on this
-
Coupled column Domain-specific is a kind of Co-location
The proposed strict upward parent is
prime:co_location. -
Gene Gating Domain-specific is a kind of Co-location
Co-location is the strict parent because the proposed advantage comes from bringing transcriptional loci and export machinery into one pore-associated region.
-
Mechanical Floor Domain-specific is a kind of Co-location
A Mechanical Floor strictly specializes Co-location.
-
Mixed-Use Development Domain-specific is part of Co-location
Mixed-use development contains co-location because its distinct land uses must occupy one building, block, corridor, or district during overlapping daily cycles.
Hierarchy path (1) — routes to 1 parentless root
- Co-location → Neighborhood → Topology
Not to Be Confused With¶
Co-presence can be virtual or interactional and need not share physical location. Proximity permits nonzero separation. Integration combines functions. Centralization moves authority or resources toward one locus and can occur without literal co-location.