adk_provider_capabilities (erlang_adk v0.8.0)

View Source

Bounded, secret-free capability metadata shared by provider profiles.

Capability names and values remain ordinary Erlang terms because adapters use richer values than booleans (for example synchronous function calls or a list of input modalities). This module never creates atoms from input and rejects executable, opaque, secret-bearing, or excessively large terms.

Summary

Types

capabilities/0

Functions

constrain(Ceiling, Restrictions)

Narrow model/profile metadata to the behavior implemented by an adapter. The first map is an implementation ceiling: an override may turn supported behavior off, select a subset of a list/map, or retain an exact scalar value, but it can never introduce a key or value the adapter did not advertise. Unknown profile keys are deliberately omitted.

merge(Base, Override)

Merge a profile-wide capability floor with model-specific metadata. The model map is authoritative for duplicate keys.

normalize(Capabilities)
supports(Capabilities, Name)

A capability is supported when it is present and does not carry an explicit negative/empty marker. This accommodates richer provider values such as synchronous, [audio], or a configuration map.

Types

capabilities/0

-type capabilities() :: map().

Functions

constrain(Ceiling, Restrictions)

-spec constrain(term(), term()) -> {ok, capabilities()} | {error, invalid_provider_capabilities}.

Narrow model/profile metadata to the behavior implemented by an adapter. The first map is an implementation ceiling: an override may turn supported behavior off, select a subset of a list/map, or retain an exact scalar value, but it can never introduce a key or value the adapter did not advertise. Unknown profile keys are deliberately omitted.

merge(Base, Override)

-spec merge(term(), term()) -> {ok, capabilities()} | {error, invalid_provider_capabilities}.

Merge a profile-wide capability floor with model-specific metadata. The model map is authoritative for duplicate keys.

normalize(Capabilities)

-spec normalize(term()) -> {ok, capabilities()} | {error, invalid_provider_capabilities}.

supports(Capabilities, Name)

-spec supports(map(), atom() | binary()) -> boolean().

A capability is supported when it is present and does not carry an explicit negative/empty marker. This accommodates richer provider values such as synchronous, [audio], or a configuration map.