select-scalardb-edition

The selection process enforces edition constraints by evaluating your deployment mode, API type, required features, and storage backends against OSS and Enterprise limitations. This prevents misconfiguration and ensures licensing alignment for your project.

When ScalarDB requirements are ambiguous, the selection process defaults to Enterprise Standard. This ensures a baseline of enterprise-grade features while still generating a structured configuration file for your project.

You configure ScalarDB storage backends and API types by defining them during the interactive edition selection workflow. The agent outputs this structured configuration, including edition, deployment_mode, api_type, features, and storage_backends, to a downstream file.

After selecting a ScalarDB edition, the workflow generates a structured configuration file named scalardb-edition-config.md in the work directory. This file contains the edition decision, deployment mode, API type, features, and storage backends for downstream skills to consume.

Using ScalarDB OSS edition for enterprise-level storage backends depends on the specific edition constraints enforced during the selection process. The agent evaluates your required storage choices and environment constraints to verify OSS compatibility or recommend an Enterprise edition.