Management hedged the May 2025 drop as possibly a "knee-jerk reaction" tied to a single large non-renewed contract and the new US administration's DOGE cost-cutting, not a durable trend — but the Oct 2025 call shows it held. A genuine Q&A-hedge pattern per doctrine (the gap between "one-off" framing and a persisting number), though Eutelsat-side, not an SES contract.
Coincided with 4 additional board-director resignations on the same day as Berneke's exit, also unaddressed. Textbook Q&A-gap signal (per doctrine, what management won't explain is itself informative) even though dated.
Flagging as a citation-consistency note for retro/dossier-deep-dive — unclear if this is a transcription artifact or an actual company-side rename; worth a quick primary-source check (Viasat/Space42 press materials) before the dossier's next update.
Not independently corroborated this cycle — a single-source mention inside an earnings call, not a primary filing. Worth a follow-up search next cycle to identify the carriers and confirm the claim.
("we're not getting full value for those [businesses]... that's what's causing us to think about other alternatives") — predates and directly seeds the Strategic Review Committee/spin-off language that persists through the Aug 2025, Nov 2025, and May 2026 calls. Same call features a notable evasive non-answer when JPMorgan pressed Viasat on United Airlines' choice of Starlink for in-flight connectivity over Viasat, including a refusal to confirm or quantify any resulting backlog impact. Chronology-only value — dates the beginning of two still-live threads (Starlink competitive displacement of incumbent GEO/MEO providers; Viasat spin-off speculation).
the file named "..._IP_2026-03-31_English.pdf" actually contains a "Third Quarter 2025-26 Revenues, May 12, 2026" presentation — its title-page date doesn't match its filename. Flagging for inbox-naming hygiene; content itself was cross-checked and used correctly (folded into D6/context above), just noting the discrepancy for whoever named the file. [no clean thread match — process/hygiene note only] ---