The weekly installment is current again. This entry collects four anchors already published on the site — one platform-deprecation explainer, one voice-network retirement explainer, one EU-regulation buyer guide, and one consolidated compliance-audit deep link. Each resolves to a post you can open today; nothing here is promised future work. The date in the slug names the morning this installment went live; the quarter's monthly and quarterly recaps continue on their own slots.
What shipped this week
- OpenAI's deprecation cycle, decoded — the 2026 deprecation schedule retires whole API surfaces, not just models: the Assistants API shut down in August with the Responses API as the migration target, the Evals platform and the hosted Agent Builder surface retire in November, and the legacy GPT-3.5 and GPT-4 snapshots disappear in October. The thing that is not deprecated is Chat Completions, so the runbook splits into two moves: a scheduled surface swap where your integration names a retiring surface, and a model-family bump where it only names Chat Completions.
- VoLTE, VoNR, and the IMS retirement wave, explained — voice retirement is two waves running side by side. The fixed-line track is the PSTN switch-off; the mobile track is operators shutting 2G/3G radios and moving every call onto VoLTE or VoNR while trimming the IMS core that carried both. The tenant-owned response is the same on either track: move fixed-line voice onto SIP or programmable voice before the medium underneath it is cut, and line up your caller-identity record — STIR/SHAKEN posture, BYO carrier, ported numbers — before the migration window closes.
- eIDAS 2.0 and messaging verification — buyer guide — the EU's eIDAS 2.0 expands the trust-services catalogue with digital identity wallets and verification schemes, which raises one narrow question for a CPaaS buyer: does any of it change how a one-time passcode gets verified over SMS? Platform-level OTP delivery and verification stay a tenant-owned control layer exactly as before; what changes is the vocabulary regulated markets use to name who proved whom. The guide draws the line between identity-proofing, which eIDAS governs, and KYC document collection, which it does not.
- The compliance-audit deep link for AI voice — the four voice-compliance classes a legal team clusters its questions around — EU AI Act Article 50 disclosure, the FCC Robocall Mitigation Database filing lifecycle, STIR/SHAKEN attestation with call-recording consent, and E911 emergency-address registration — are consolidated on one page, each resolved to the shipped tenant-owned control and its docs walkthrough. A legal review can now run start to finish from a single link instead of four separate hunts.
Operator takeaways
Three actions are worth the minutes they take this week.
- Split your OpenAI migration runbook by surface, not by date. Inventory which OpenAI surfaces your integrations name. Anything on Assistants, Evals, or Agent Builder needs a scheduled swap; anything on Chat Completions only needs a model-family bump. Treating them as one migration makes the retirement list look larger than it is.
- Sort your voice estate by retirement track. Fixed-line numbers follow the PSTN switch-off calendar; mobile-carried calling follows the VoLTE/VoNR window. Check which track each of your numbers is on before you schedule the move, and get your caller-identity record in order ahead of either window.
- Hand your legal team one link. Forward the compliance-audit deep link to whoever owns your AI-voice legal review; the four classes resolve to the controls you set per tenant and the evidence trail you own, so the review no longer starts from a scavenger hunt.
Where this shows up
All four anchors are live now:
- OpenAI's deprecation cycle, decoded — the platform-sunset runbook split.
- VoLTE, VoNR, and the IMS retirement wave — the mobile-side counterpart to the PSTN switch-off.
- eIDAS 2.0 and messaging verification — the regulation mapped to the Verify loop.
- The compliance-audit deep link — four voice-compliance classes on one page.
The canonical release history stays at orbit.devotel.io/en/changelog; the quarterly review slot carries the archive of past installments.