This is the backfill installment of a third cadence slot. The announcement-cadence hub defined a weekly This week in Orbit entry and a monthly Orbit release notes recap; the quarterly review — one post per quarter wrapping the quarter's shipped work in a single page — began with Q2 2026, and this post completes the series backward to Q1. Like every installment, everything below is live today and each item traces back to a dated entry on the canonical changelog. Q1 2026 covers January, February, and March.
Q1 was the foundation quarter: the public changelog opens on March 8 with the platform foundation entry, and the prior weeks were studio time. The narrative below covers the March avalanche by week, then the numbered anchor list ties each cluster to the dated entries behind it.
Early March: the platform stands up
The first week of March carried the heaviest single wave the changelog has recorded — fifteen dated entries between the 8th and the 13th. March 8 opened with the platform foundation itself: auth and messaging foundation, developer docs and SDKs, and the dashboard's action dialogs. The next day completed the API surface — API key scopes, delivery webhooks, and the first MCP server — while custom fields, sender IDs, and call recordings filled in the messaging core.
March 12–13 turned that base into a system: the channels pricing engine, the flow execution engine, the RAG pipeline and agent tools, and the GDPR feature set all landed inside two days, with production-readiness hardening closing the week. A telecom platform's load-bearing pieces — routing, pricing, flows, agent runtime — shipped as one authored shape rather than as stubs to be finished later.
Late March: the channel sweep
The rest of March widened the channel surface at a similar pace. Telnyx integration and 10DLC registration walked in on the 18th, WhatsApp embedded signup on the 19th, and a twelve-phase production-hardening pass on the 20th. The voice infrastructure and IVR pass landed March 23; the Clerk migration closed the auth story on the 25th.
The 28th was the heaviest single day of the quarter — RCS via Dotgo with the full brand workflow, scheduled-send for campaigns, a webhook debugger, Telegram Verify, and a channel audit all shipped in one pass. The final days rounded the surface out: Instagram, Messenger, and LINE (March 30), silent authentication via SIM-swap and APNs (also March 30), the Devotel SBC voice gateway, HLR lookup, Meta Marketing API, and Viber dual-tier (all March 31).
Shipped in Q1 2026 — the numbered anchor list
The numbered anchor list below maps each Q1 cluster to its dated changelog entries; the canonical history stays at the changelog either way.
- Platform foundation — the platform foundation, auth and messaging, and dashboard action dialogs (March 8 foundation wave).
- Messaging API completeness — API completeness with real-time events, API key scopes with delivery webhooks and MCP, and custom fields with sender IDs and call recordings (March 9 API surface).
- Flows, pricing, and agent tools — the channels pricing engine, flow execution engine, RAG pipeline, and enterprise/GDPR features (March 12 core systems).
- Compliance surface — 10DLC integration via Telnyx (March 18 10DLC and Telnyx); WhatsApp embedded signup (March 19); the GDPR feature set from March 12.
- Voice infrastructure — the voice and IVR pass (March 23 voice infrastructure and IVR) and the Devotel SBC voice gateway (March 31).
- Numbers intelligence — HLR lookup (March 31); silent authentication via SIM-swap and APNs (March 30).
- Messaging channels — RCS via Dotgo with the full brand workflow, Telegram Verify, and the channel audit (all March 28); Instagram, Messenger, LINE, and Viber dual-tier (March 30–31).
- Agent runtime and video — agent runtime with the voice gateway, push notifications, and video (March 28).
- Campaign tooling — scheduled-send and the webhook debugger (March 28 schedule and debug); the campaigns pricing and policy work in the March 12 wave.
- Hardening — the twelve-phase production-hardening pass (March 20); production-readiness and quality-360 (March 13).
What we learned
The honest read on Q1: a foundation quarter does not read like one until someone groups it. The March wave was a single authored shape — API, flows, pricing, agents, and every major channel in one month — but as a scroll of dated entries it was unreadable as a whole. The cadence slots exist precisely so a quarter is legible; this backfill applies the same lens Q2 introduced to the quarter that came before it, so the series now covers the platform's full public history.
Quarterly convention
One post per quarter, named Orbit quarterly review — <quarter> <year>, tagged quarterly-review so the class is machine-identifiable alongside the weekly and monthly slots. Each review covers shipped work only, grouped by channel, with platform-and-hardening sections for what does not fit a channel. The cadence hub post lists all three slots; the canonical history stays at the changelog either way.
The following installments are already live: Q2 2026, Q3 2026, and Q4 2026.
Frequently asked questions
Why is this published after Q2, Q3, and Q4? The quarterly slot was introduced with the Q2 review; this post backfills the quarter before it so the series is complete. The work it describes shipped in January–March 2026 and has been on the canonical changelog since the days it landed.
Is everything here actually live? Yes — the review covers shipped work only. Each numbered item points at its dated changelog entry; no capability gets a retrospective mention it has not earned in the public changelog.
Where do monthly release notes fit? Monthly release notes are a separate cadence slot running alongside this quarterly review; the two do not subordinate to each other. The announcement-cadence hub lists all three slots (weekly, monthly, quarterly).
How does this relate to the announcements page? The announcements registry at /announcements deep-links into the quarterly reviews as their narrative spine — the registry is the hub surface and these posts are the narrative it resolves against.