Spatial systems in SnS connect place records to maps, geometry, provider interop, and future digital twin experiences. The spatial layer is intentionally separated so provider details do not leak into app state or database workflows.

• Maps
• Providers
• Geo DTOs
• Digital Twins

Sns.Spatial should stay provider-neutral where possible. Provider-specific DTOs, JavaScript modules, and interop wrappers belong under provider folders, while SnS workflows compose those capabilities from Sns.Framework.