Telnyx planned/backlog

Telnyx is planned/backlog and not currently available in this release. There is no installation command, credential flow, or availability claim for it.

What a future adapter would add

A future communications adapter would own its transport boundary and provider observation categories. For example, a notification system might distinguish “message accepted for delivery” from “customer account changed.” If the action changes authoritative state, an independent verifier and a safe claim policy would still be required. Those are design questions, not current behavior.

The provider-neutral lifecycle remains the supported way to study proposal, trusted context, grounding, authorization, provider attempt, independent verification, effect truth, and safe result. Telnyx is not a current enrollment option, package-access path, live transport, or credential surface. Any future work requires separate implementation, conformance, privacy, operational, and release review.