How is per-deployment configuration stored (PlatformSettings key/value)?

Configuration that varies per deployment lives in a single PlatformSettings key/value store, accessed through a settings service. Rather than scattering config across compiled constants or many tables, settings like the vendor mode (single vs multi), the active product types, setup-wizard progress, AI recommendation toggles and intervals, and similar choices are stored as named keys with…

Configuration that varies per deployment lives in a single PlatformSettings key/value store, accessed through a settings service. Rather than scattering config across compiled constants or many tables, settings like the vendor mode (single vs multi), the active product types, setup-wizard progress, AI recommendation toggles and intervals, and similar choices are stored as named keys with string values. This is what makes the platform "configurable, not hard-coded": flipping a deployment from single- to multi-vendor, changing a refresh interval, or recording which steps of setup are complete is a settings write, not a code change. The setup wizard writes here, and the equivalent settings are also reachable directly from the admin so power users can adjust configuration outside the wizard.