Replace adapters, preserve the contracts

Use the examples to understand the sequence and safeguards, then implement your real authority.

Independent integration surfaces

The provider Runtime accepts billing, numbering, endpoint resolver, independent inbound and outbound edges, optional DNS and registry adapters. Edge verification must independently inspect persisted or remote resources. A successful configuration call alone is not verification.

Respect ownership

Simulated edges record owners, specifications and fingerprints. Matching resources remain unchanged; unmanaged or drifted resources conflict. removeOwned must revalidate ownership before deletion. Commercial number allocations are not silently released when entitlement changes.

Use honest result states

The reference distinguishes simulated, configured, verified-config and call-tested results. Its operations retain simulated status and call_tested: false. Real connectors need documented authenticated APIs, least-privilege credentials, bounded transport and independently verified outcomes. No production SBC connector is fabricated by the example.