Capability vs availability
A designed capability may require specific deployment, entitlement or integration before it is available.
TRUST
Separate capability, configured availability, vendor-declared information, verified integration evidence and future/planned items.
A designed capability may require specific deployment, entitlement or integration before it is available.
Organizational, product, device, regulatory, vendor and integration claims are kept distinct.
External systems, device firmware, identity provider and customer policy can materially affect behavior.
Material service-boundary changes are reflected in controlled documentation/release information.
Marketing language must not turn an integration-dependent or vendor-declared item into a verified Mobile-ID claim.
Questions about availability or claim status should identify the exact service, device, version/configuration and deployment context.