Declared and Latent Capability

Two different mechanisms by which software capability accumulates on the available side of the adoption gap.

Declared capability. The vendor announces a new feature. It is documented, it appears in a release note, and the customer decides whether to switch it on. This is the path every enterprise change gate was built for, and it still works exactly as designed.

Latent capability. The vendor improves the model underneath a feature the customer already runs. The ceiling on what that feature can do moves. Nothing appears in a feature list, no administrative action is required, and the customer's gate never sees it, because the gate was built to admit or refuse discrete things and this is not one.

The distinction that matters

Not every model improvement is latent capability. Performance improvements make the same feature cheaper or faster, and vendors have shipped those forever. Nobody ever needed a gate for a faster response.

Latent capability is specifically an increase in what the feature can do. That is the part with governance consequences, and it is the part that arrives with no decision attached.

How to use it

When counting the distance between what you own and what you run, count both.

Declared capability can be counted from release notes. Somebody can work through the list and name what is switched off.

Latent capability cannot be counted the same way. It requires asking the vendor what the models underneath your implemented features have done since the implementation, and it requires a scheduled re-look, because nothing in the maintenance calendar will prompt one.