Provider-agnostic settings service for all OpComm applications
Receives and indexes configuration registrations from all OpComm services, APIs, and mobile clients to build a unified settings catalog.
Phase 1 — ActiveServe settings from any backend — Azure App Config, local file, SQL, or custom providers — through a single consistent API surface.
Phase 2 — PlannedHonors the full slot-file hierarchy — base, common, slot, and development overlays — matching the established OpComm layered config pattern.
Core Architecture