Build a co-location map
content(gis): GIS/location-intelligence cluster consolidation (final of 5 flagged clusters) — merged the one genuine duplicate (pointsav-gis-engine.md into location-intelligence-substrate.md; its own body said its core logic lives in app-orchestration-gis). More significant: found and fixed a corpus-wide wikilink collision — 7 articles cited [[co-location-methodology]] as the retail-cluster tier-scoring methodology, but that slug resolves to a real, unrelated article about data-center FACILITY co-location siting. No article for the real retail methodology existed under any slug, and the one place a scoring mechanism WAS described in detail (app-orchestration-gis.md) described a Haversine formula the real SCORING-METHODOLOGY.md V3 confirms was replaced by a 4-tier gate system — with 2 more articles describing the mechanism differently again, none matching each other or reality. Created substrate/retail-co-location-tier-methodology.md as the single source of truth (facts from the verified real methodology doc) and repointed all 7 citing articles (14 files EN+ES) to it. Fixed architecture/_index.md's MOC description, which had also mischaracterized the real co-location-methodology.md article. All content-matrix clusters now resolved.
@@ -123,7 +123,7 @@ application's visual language. ## See also - [[pointsav-gis-engine]] — GIS engine architecture and available API surfaces - co-location methodology — how cluster tiers are scored - [[location-intelligence-substrate]] — GIS engine architecture and available API surfaces - [[retail-co-location-tier-methodology]] — how cluster tiers are scored - O-D catchment methodology — how trade areas are defined - [[federate-archives-via-content-mounts]] — mount location-intelligence data into a second instance