Features
A feature is the unit of licensing in the EDK. It is a namespaced, versioned key paired with a declared value type. Each feature names one capability the platform can grant. Everything the license model decides resolves to features. A product bundles features. A command requires features. The resolver checks the active license for the features a command needs.
A feature key
A feature key is a dotted, versioned string such as semantic-modeling.v1. The version segment is part of the key. A capability can evolve to ….v2 without disturbing deployments still entitled to ….v1. Keys are namespaced by capability area, so the set stays readable as it grows. Every key reads as the thing it gates.
Each feature declares a value type. The value type fixes the shape of the value the active license carries for it.
| Value type | What the license carries | Typical use |
|---|---|---|
| Boolean | An enablement flag. The feature is on. | A capability that is either licensed or not. |
| Quota | A numeric cap, optionally with a metering window. | A counted or windowed allowance, paired with a quota key. |
| Config | A string or enum configuration value. | A licensed setting whose value the license supplies. |
A feature also records a short description and the set of products that may include it, so the catalog can present a complete inventory.
What a deployment supports
A deployment exposes the features it supports as part of its catalog. The catalog lists the features the deployment knows about. A VDX deployment also includes VDX's features.
Enablement per deployment
Listing a feature in the catalog makes it knowable. It does not make it granted. What a deployment can actually do is decided by the active license, which carries the resolved set of features the customer is entitled to. The platform baseline every tenant inherits, and any per-tenant additions, are composed against the signed license. A feature is only enabled when the signed license includes it. The catalog lists the features a deployment supports. The signed license decides which of them are granted.
An operator can read the catalog through the feature catalog surface on the Platform Admin API. Every entry carries the feature key, its value kind, its description, and the products that may include it. See the Platform Admin API reference for the exact shape.
Where features fit
- Products and SKUs bundle features into purchasable editions.
- The catalog is the read-only view over the features and products a deployment supports.
- Entitlement Resolution decides, per command, whether the active license grants the features the command requires.
- A command declares the features it needs in its command contract. The resolver checks them at invocation.