Site Map or Plan¶
Spatial model — instantiates Persistent Site Framing
Draws sites as bounded, nested regions so their extent and adjacency are legible at a glance.
A Site Map or Plan is the archetype's spatial representation: it renders sites as regions with edges and shows how they nest, abut, and contain one another. Where a registry says a site exists and a label says where its handle is, the map answers the questions only a picture answers — how big is it, where does it stop, and what is next to it. Its defining move is drawing the boundary: it fixes the extent of each site so that "the loading bay" has an edge that does not creep, and it arranges those bounded regions into a legible whole so adjacency and containment can be read directly rather than reconstructed from a list of coordinates.
Example¶
A regional distribution warehouse keeps losing time to arguments about where one storage bay ends and the next begins — pallets straddle the painted line, a forklift lane gets colonized, and two shift leads book "bay 12" meaning slightly different footprints. The team produces a Site Map: a scaled floor plan with every bay drawn as a closed polygon keyed to its registry token, aisles and fire lanes shown as their own bounded regions, and a nesting structure that groups bays into zones and zones into the building. The plan makes the extents unarguable — bay 12 is that rectangle, ending at that line — and shows at a glance that bay 12 borders the charging station, which is why anything flammable is barred from it.
The map changes no occupancy and schedules no move; it just makes the geography legible, so when planners reason about capacity or fire code they are reading edges and neighbors off a picture instead of litigating them in a meeting.
How it works¶
The plan is a scaled, coordinate-anchored drawing in which each site is a closed region tied to its registry token, plus a containment structure over those regions. Two things distinguish it from a mere sketch. First, boundaries are authoritative: the edge on the plan is the site's extent, so disputes resolve to the drawing rather than to memory. Second, the hierarchy is explicit: sites nest (unit-in-cabinet-in-row-in-hall, bay-in-zone-in-building) and border one another, and those relations are part of the model, not incidental to how things were drawn. The map is kept in register with the registry — every drawn region corresponds to an entry — but it deliberately holds no occupancy, capacity rules, or live status; it is geometry and topology only.
Tuning parameters¶
- Scale and precision — survey-grade dimensions versus a schematic. Precise plans support engineering and legal use but are costly to keep current; schematics are cheap and communicative but can't settle a boundary to the centimeter.
- Boundary rigidity — hard fixed edges versus soft, adjustable regions. Rigid edges end disputes but resist legitimate reconfiguration; soft edges flex but invite drift.
- Hierarchy depth — how many levels of nesting the plan encodes. Deep nesting captures fine containment but clutters; shallow nesting is readable but hides structure.
- Adjacency richness — whether the plan merely shows neighbors or annotates the relationship (shared wall, blocking, access route). Richer adjacency aids reasoning but complicates upkeep.
When it helps, and when it misleads¶
The map's strength is legibility[n1]: humans reason about extent and neighborhood far better from a picture than from a coordinate table, so a plan prevents the boundary disputes and capacity miscounts that come from everyone carrying a slightly different mental map. It is the reference geography every spatial decision hangs on.
Its characteristic failure is boundary drift without lineage: the physical world changes — a wall moves, a bay is split — and the plan is quietly redrawn with no record that the extent changed, so old references silently mean something new. A related misuse is trusting a stale plan as ground truth long after reality diverged, which is worse than having no plan because it is confidently wrong. The guarding discipline is to version the plan, treat a boundary change as a lineage event worth recording, and periodically confirm the drawing against reality rather than assuming it still holds.
How it implements the components¶
The map fills the archetype's spatial-representation components:
site_boundary_or_extent— it draws each site as a closed region with an authoritative edge, fixing how far the site reaches.site_hierarchy_map— it encodes how sites nest and border one another, making containment and adjacency directly readable.
It renders geometry only: it does not compute how heavily sites are used — site_utilization_signal is the Vacancy Status Dashboard's, its nearest twin (the dashboard rolls live usage up the same hierarchy this plan draws statically) — and it does not name or authorize sites; site_identity_frame is the Site Registry's.
Related¶
- Instantiates: Persistent Site Framing — the plan is the archetype's spatial model, giving extent and adjacency a legible form.
- Consumes: Site Registry — supplies the identities the drawn regions correspond to.
- Sibling mechanisms: Site Registry · Physical or Virtual Labeling System · Capacity-Fit Matrix · Assignment and Release Workflow · Occupancy Ledger · Site Lineage Tombstone · Vacancy Status Dashboard · Site Audit Walkthrough
Editorial Notes¶
Form Classification¶
Form family: Representation, Specification & Plan
Rationale: Site Map or Plan operates as a static representation, map, specification, schema, or prospective plan that externalizes information because it draws sites as bounded, nested regions so their extent and adjacency are legible at a glance.
Independent corroboration: The frozen evidence defines Site Map or Plan as 'Draws sites as bounded, nested regions so their extent and adjacency are legible at a glance', so its operative form is Representation, Specification & Plan.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Architecture & Urban Planning
Origin pattern: Single lineage
Present-day reach: Multi-domain
Rationale: Representing bounded, nested regions and adjacency in plan view is foundational architectural and planning drawing.
Related originating lineages:
- Art & Aesthetics — Graphic composition makes extent and relation legible.
- Earth Sciences — Cartography supplies spatial conventions and scale.
- Engineering & Design — Site plans coordinate physical implementation and interfaces.
Review resolution: The blind reviewers agree that architecture_urban_planning is the primary origin and differ only on alternate origin disagreement. I preserve every independently explained alternate from both records rather than imposing a numeric cap. I retain single_lineage because the combined evidence shows one traceable formative lineage. The broader reach of multi_domain records portability separately from historical provenance; encyclopedia_synthesis=false preserves the affirmative synthesis judgment where either reviewer identified one.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] Legibility — the ease with which the parts of an environment can be recognized and organized into a coherent pattern — is Kevin Lynch's central idea in The Image of the City. A site plan is a deliberate legibility aid: it externalizes extent and adjacency so no one has to hold the geography in their head. ↩