SnS uses a small set of domain concepts to connect real-world places, spatial context, operational work, and reusable digital assets. These terms are used across admin screens, editor state, spatial workflows, database models, and future automation.

The core model starts with places and the things attached to them: communities, structures, spaces, assets, requests, projects, work orders, layers, and twins. The goal is to keep navigation and data relationships understandable as the platform grows.

• Communities
• Places
• Structures
• Spaces
• Assets

A community provides broad context. A place is the central record. Structures and spaces describe physical organization inside a place. Assets, layers, and twins describe files, visual overlays, models, and spatial representations connected to that context.

Operational work starts from a place-aware need: a request becomes a project, and a project can later coordinate work orders, deliverables, assets, and versions.