Add enterprise docs structure and include pending core maintenance updates.

docs/features/geospatial-search.md

@@ -0,0 +1,60 @@
+# Geospatial Search
+
+## Purpose And Business Outcome
+
+Support location-aware queries such as nearest-neighbor and bounding-box lookups for geospatial workloads.
+
+## Scope And Non-Goals
+
+Scope:
+- Spatial index configuration
+- Proximity and bounding-box query operations
+
+Non-goals:
+- Full GIS projection transformations
+- External map tile services
+
+## User And System Workflows
+
+1. Consumer configures spatial index for coordinate fields.
+2. Coordinates are serialized and stored with entity payloads.
+3. Query path evaluates `Near` or `Within` predicates.
+4. Engine returns matching entities.
+
+## Interfaces And APIs
+
+- Spatial index APIs in model configuration
+- Query helpers under `GeoSpatialExtensions`
+- Index implementation in `RTreeIndex`
+
+## Permissions And Data Handling
+
+- Geolocation data may be regulated or privacy-sensitive.
+- Apply least-privilege access and retention limits.
+
+## Dependencies And Failure Modes
+
+Dependencies:
+- Correct coordinate format and units
+- Spatial index consistency
+
+Failure modes:
+- Invalid coordinate values
+- Unexpected results from bounding definitions or radius units
+
+## Monitoring, Alerts, And Troubleshooting
+
+- Validate geospatial paths through dedicated stress and correctness tests.
+- Use [`../runbook.md`](../runbook.md) for escalation.
+- Follow [`../security.md`](../security.md) for geolocation data protection controls.
+- Use [`../troubleshooting.md`](../troubleshooting.md#query-and-index-issues) for issue resolution.
+
+## Rollout And Change Considerations
+
+- Document coordinate and unit assumptions in release notes when behavior changes.
+- Validate backward compatibility for persisted spatial index pages.
+
+## Validation Guidance
+
+- Run `GeospatialTests` and `GeospatialStressTests` before release.
+- Include representative proximity/bounding queries in smoke checks.