fix: reject geocode results outside node jurisdiction

Nominatim's viewbox is advisory (bounded=0), so ambiguous place names like "Pinebrook" can resolve to locations 30-40km away in the wrong town. Added a post-geocode distance gate: results farther than geocode_max_km (default 25km) from the node are discarded with a warning log rather than written to the incident. Also logs distance on successful geocodes for easier audit. New config setting: geocode_max_km (float, default 25.0)
2026-05-25 13:09:10 -04:00
parent 4b7d9dd49a
commit 0db09d6bf7
2 changed files with 25 additions and 3 deletions
@@ -29,6 +29,7 @@ class Settings(BaseSettings):
    embedding_no_location_threshold: float = 0.97 # slow-path: match without location (very high bar)
    embedding_cross_tg_threshold: float = 0.85    # cross-TG path: same dept + 2+ shared units
    location_proximity_km: float = 0.5        # radius for location-proximity matching
+    geocode_max_km: float = 25.0              # reject geocode results farther than this from the node
    incident_auto_resolve_minutes: int = 90   # auto-resolve after N minutes with no new calls
    recorrelation_scan_minutes: int = 60      # re-examine orphaned calls ended within this window
    tg_fast_path_idle_minutes: int = 90       # fast path: max minutes since incident last updated