Editors in SnS follow the DataMine editor pattern: a composed surface with head, list, detail, and foot regions backed by scoped state. This gives CRUD and review workflows a predictable structure.

• Head contains search, filters, view switches, and primary commands.
• List presents selectable records or search results.
• Detail shows the current record, form, map, or review surface.
• Foot provides secondary navigation, record bars, or status controls.

Editor components should stay thin. Selection, loading, filtering, dirty state, and current record resolution belong in scoped feature state. Services own persistence, normalization, validation, and database access.

This separation keeps editor markup readable and allows feature state to coordinate overlays, navigation, and refresh behavior without scattering that logic through child components.