TuneCore's AI verdict on 'Praying' was right. The process was still broken.

Three days ago, Ukrainian indie artist Yasia Saienko (@yasiavmyla) posted an Instagram screenshot of a TuneCore email refusing to distribute Track 2 of her theatre-production album Atlantis. TuneCore cited "indicators suggesting the use of generative AI tools that rely on datasets that are not properly licensed." No evidence. No human review. No appeal path. Her post crossed 1,200 likes in 72 hours because thousands of independent artists have felt that email arriving in their inbox with no recourse. We ran the same track through our detector. The verdict agreed with TuneCore. That doesn't end the conversation — it starts a different one.

What happened

On July 20, 2026, TuneCore emailed Yasia Saienko rejecting delivery of "Praying" — a track from Atlantis (Music for the Theatre Production), which she says has been publicly available on her Bandcamp for approximately 1.5 years. The rejection language is boilerplate: "content review team identified indicators suggesting the use of generative AI tools." No specific signal disclosed. No audio timestamp. No model version. No path to appeal with data.

Her reply, in the caption of the viral post:

At the same time, they don't provide any evidence and simply rely on their own "technology," which is, quite obviously, AI. Their support team doesn't support. It only slows things down and creates frustration. No human review is ever provided. And this is not an isolated case. […] really? do i need to prove my authenticity to machines?

Every element of her frustration is legitimate on its own: no evidence attached to the rejection, no human in the loop, no explainable signal, no clear appeal channel. The last line — "do I need to prove my authenticity to machines?" — is what the entire independent-artist tier is going to be asking DSPs and distributors over the next twelve months.

The independent second opinion

We ran the same track — "Praying" — through DistroShield's public lookup. Different model architecture from TuneCore's, different training corpus, no shared vendor. Here is what our detector emitted:

Two systems trained differently, using different feature sets, delivered the same verdict class. That is the definition of cross-validation, and it is what artists have not had access to until now. TuneCore's verdict was not disclosed with a probability, an attribution class, or a runner-up. Ours is disclosed with all three, plus a signed timestamp and a SHA-256 hash of the underlying analysis.

The "unknown_ai" attribution is the piece that matters here. It is our v10 primary model's way of saying "this fits the acoustic signature of AI-generated audio, but does not specifically match the fingerprints of Suno, Udio, or the licensed generators we have profiles for." That maps to TuneCore's phrasing almost exactly: "generative AI tools that rely on datasets that are not properly licensed." Two independent systems, no shared training data, converging on the same classification — including the same sub-classification.

This is not about who is right

It is possible both detectors are wrong. Cinematic and theatre-composition tracks — long sustained pads, minimal transients, extended releases, atmospheric mixing — sit in the acoustic region where AI-generation output and legitimate human production overlap most heavily. Every AI-music detector on the market today was trained on a corpus heavily weighted toward pop, urban, and vocal-forward genres. Ambient and cinematic material is genuinely out-of-distribution, and out-of-distribution is where classifiers fail in correlated ways — meaning two independent detectors can both misfire on the same track for the same underlying reason.

So this piece is not saying "Yasia used AI." We cannot prove that. TuneCore cannot prove that. What we can say is:

1. The acoustic signatures of this track will trigger every major AI detection system in the industry, not just TuneCore's. If the track ships to Spotify or Deezer through another distributor, it faces the same math with no more transparency than TuneCore offered.
2. If the track is 100% human, the artist deserves a way to establish that with data — not by begging a support ticket and hoping a human eventually reads it.
3. If the track is AI-generated or AI-assisted, the artist deserves to know which specific signatures triggered the flag so she can decide whether to disclose, modify, or dispute.

None of those three outcomes is available to her today through TuneCore's process. And none of them will be available at Spotify, Deezer, or Amazon either. That is the actual problem her post surfaced.

What every independent artist actually has right now

Map her situation onto the current industry stack:

The entire stack is one-sided verdicts with no independent artifact. Every conversation about "AI or not" happens as her word against a black box. When she signs up with a different distributor to bypass TuneCore, she is not solving the problem — she is walking into the next black box, and downstream she still hits Spotify's retroactive removal engine and Deezer's catalog cleanup, both of which run their own classifiers with their own zero-transparency policies.

What an independent second opinion actually gives an artist

For the specific case of "Praying," here is what a DistroShield report contains that a TuneCore rejection email does not:

1. A specific verdict class (human / hybrid / licensed_ai / unlicensed_ai / unknown_ai) rather than a boolean accept/reject. In this case: unknown_ai, 98% attribution confidence.
2. A probability, not a decision. 75% AI probability is meaningfully different from 99%. Both would be "rejected" by a boolean filter. The number is what lets an artist gauge whether the flag is borderline or overwhelming.
3. A runner-up class. Ours shows licensed_ai at 1% — meaning the classifier does not think this is a licensed generator's output, matching TuneCore's "unlicensed datasets" phrasing. When the runner-up is high (e.g. human at 40%), that is diagnostic of a hard case where reasonable minds — and reasonable classifiers — could disagree.
4. A signed certificate. Model version, timestamp, per-class probabilities, SHA-256 hash. This is the artifact that turns "I say it is human" into an evidentiary record a distributor, DSP, or rights team can verify independently.
5. A path forward. If the artist believes the verdict is wrong, the full report lists the acoustic signals that drove the classification. That surface makes it possible to have a technical conversation — with the distributor, with a producer, or with a lawyer — rather than a "trust me" one.

TuneCore emitted none of these. Neither does DistroKid. Neither does CD Baby. Neither does FUGA. Neither do the DSPs' internal classifiers. This gap is what Yasia's post surfaced with more visibility than any of the recent DSP announcements — because unlike the industry briefs, hers landed with a face and a name.

The larger shift her case sits inside

Zoom out from the individual case:

In two weeks: three DSP-tier enforcement disclosures, two distributor-tier active rejection systems, and one viral case putting a name on the artist end of that pipeline. The direction is set. The tools to enforce are already running at production scale. What has not caught up is the transparency layer — an independent, artist-controlled signal that participates on equal footing with the distributor's or DSP's private one.

Independent second-opinion detection is not a nice-to-have anymore. For any indie artist releasing after 2024, it is the only mechanism for recourse that does not require the distributor or DSP to volunteer information they have shown no willingness to volunteer. That applies whether the second opinion agrees with the distributor (as it did here) or contradicts it — the artifact is the same, and the artifact is what changes the conversation.

One note for Yasia, if this piece reaches her

If you believe the verdict is wrong, the full technical report on "Praying" — including the specific acoustic signals that drove the unknown_ai classification — is available at no cost. Email contact@distroshield.com with the track and we will send it. If the report identifies a specific signature that traces back to a mixing or mastering decision rather than the composition itself, that is actionable information — for you, for your producer, and for the distributor conversation. If it identifies signatures characteristic of generative AI output, that is also information you own and can decide what to do with. Either way, the signal is yours, not ours and not TuneCore's.

The larger point is not about one track. The point is that no artist should be in the position of arguing their humanity to a support ticket with no evidence in hand. The tool to change that exists and costs less than a coffee.