Doesn’t Really Sound Like You.

Under his own name, a folk singer found a single his attorney says he never made. His platform built protection for exactly this. Per its own help page, that protection is opt-in and still a limited beta.

Around noon, August 22, 2026. Sam Ness is sitting in a café. He is preparing an Instagram post to thank fans for Of Heart and Home, released July 23, 2026 after two years’ work. He opens Spotify for Artists to get a stream count. What loads is not his album’s stats. It is “the number of streams for a new single.” Madison Magazine reported the episode on September 14, 2026. “I didn’t realize I had one,” Ness said. A bandmate wrote: “Hey’s what’s up with this new single? Doesn’t really sound like you.”

The record answered for him

The single was called “Chasing Open Sky.” The article says it also appeared on Apple Music, Amazon Music, Deezer, YouTube Music, SoundCloud “and other music services.” Ness searched the title on Google. “It came up with all the credits as me,” he said. “I was the songwriter. I was the producer.” He recalled Google’s AI overview calling it “a Sam Ness song about his travels and his adventures as a songwriter.” Ness has 19 Madison Area Music Awards, per Madison Magazine. The credits carried his name.

Ness’s attorney, Matthew B. Harrison, told the magazine: “Sam did not make, authorize, submit, approve or release it.” He says “the available evidence establishes” the recording “was unauthorized and falsely attributed,” but he is “not prepared to say that it is in fact AI because I don’t know.” The article also reports he called the track “likely” an AI impersonation. The magazine reported Harrison contacted the platforms and they had not been responsive. Harrison is careful. So is this record.

The check that exists

Spotify built something for this: Artist Profile Protection. Spotify’s help page, fetched September 19, 2026, says the protection “notifies you when music is delivered to your artist profile and lets you remove yourself from incorrect releases.” The next sentence: “It’s currently in limited beta.” Spotify calls it “available to a limited group of artists” and says it will “expand access over time.” DistroKid’s help article names the condition: profile protection is “entirely optional” and “only affects newly delivered releases.”

Profile protection has two settings. In the standard one, silence has a default: “If you don’t take action on a release, it goes live as scheduled with you listed as an artist.” The advanced setting inverts it. It requires approval before a release lists you as an artist, and Spotify says it is “designed for profiles that receive frequent incorrect or impersonating releases.” DistroKid’s help-center paragraph on approvals gives only the approval-gated rule: “Releases that are not acted on by the release date will not be listed on the profile.” In the advanced setting, silence keeps your name off. In the standard setting, silence leaves it on.

None of this says Ness lacked the protection, or that it would have stopped this release. The check runs only when an artist turns it on, and Spotify adds another limit: “During the beta, releases from some providers may not be eligible for removal or approval.”

The assumption underneath

On September 15, 2026, UMG Recordings, Inc. and affiliated labels sued DistroKid in federal court in Delaware. Everything in the complaint is allegation, untested in court. Ness is not a party, and nothing here connects the suit to his song. Paragraph 61 alleges that DistroKid did not remove a disputed track carrying a legitimate UMG artist’s ISRC, the standard code identifying a specific recording. The complaint adds that the legitimate track’s revenue on one service is “currently frozen.” Paragraph 109 alleges a reason the digital services distribute DistroKid’s tracks: they “(incorrectly) believe that DistroKid vets its account holders to ensure that real human musicians are creating the music.” That paragraph is a claim about a belief: what the digital services assume DistroKid checks, not what they check themselves. A belief about a check is not a record of one.

The same key, on a different shelf

Tamra Westberry writes as Tara West, and The Atlantic reports she has published dozens of books under that name. Earlier this summer, a fellow author endorsed a new book listed under her pen name: Project Erebus, per The Atlantic’s September 18, 2026 article. “She had never heard of a book called Project Erebus. And she certainly wasn’t its author.” She found it on her Amazon author profile, with character names she had used before and a cover “echoing that of her recent work.” She emailed Amazon to delink the books. Amazon removed them from the platform “within a week or so—but not before some of her fans purchased them, read them, and left reviews.” She told the reporter it is “deeply unsettling” that “some no-talent grifter can bottom-feed off my fan base with AI slop.” Those are her words. This edition characterizes no one’s intent.

The Atlantic reports the pattern across the category, not Westberry’s case: Amazon “often sends out emails notifying author-page followers about new listings,” which lets such titles “leech a writer’s fan base.” Amazon’s publishing help says “several Amazon features (e.g., Author Pages, Series Pages, format linking) rely on a consistent author name.” Amazon told The Atlantic it takes measures to prevent, detect and remove violating content, without saying how; its spokesperson said the company works “directly with authors to address any issues or errors affecting their accounts.” Nothing in that help page ties the name to its owner at upload. The Atlantic also reports Amazon caps self-publishing at ten books a week per format and “sometimes requests identity verification for accounts.” Asked by The Atlantic why it doesn’t verify profile identities across the board, Amazon “did not provide a response.” Two catalogs, two industries, one key: the name on the work, in each company’s own documents.

What removal does not reach

On September 19, 2026, this record captured the Tara West page at FantasticFiction, a third-party bibliography site. The page carried Project EREBUS: Volume 1 twice. Once among her new and upcoming books, dated June 2026. Once as a series of its own. This record makes no claim about how the listing got there or who placed it, and FantasticFiction is not accused of anything. The Atlantic gives the title as Project Erebus. If the two listings are one work, the capture shows what one retailer’s correction does not reach. Edition 051 found it in archived copies; here, a live bibliography.

The Agentics read

Agentics reads this pattern through Digital Derangement Syndrome™ (DDS™): AI-mediated systems failing to recognize legitimate authority. One clinical characteristic fits this record.

A second characteristic fits in part: Signal Fragmentation, authority signals that are disconnected or inconsistent. If those listings are the same work, Westberry’s record no longer agreed with itself: absent at the retailer, present in a bibliography. For Ness, removal is unconfirmed, so the fit stops there. Edition 075 called its case a hostile mirror: a fabricated approval built to borrow the credibility of real names, aimed at a payment decision. This is not that. Here the object damaged is each person’s own record of what they made. The Answer Engine Authority™ (AEA™) prescription starts upstream: tie the work to its owner before a catalog takes the name’s word for it.

Where the argument stops

Ness’s account rests on one outlet, Madison Magazine. Westberry’s rests on The Atlantic. The Google overview is Ness’s recollection. Whether the Ness track is AI-generated is not established. Whether the song has come down from Spotify is unconfirmed. Madison Magazine’s account does not say whether Ness had access to Artist Profile Protection. This record did not independently establish that the two listings are the same work. This record read one help page and found nothing tying a name to its owner at upload; that is a reading, not a claim by Amazon.

Every platform rule quoted here was read on September 19, 2026, and may have moved since. This edition carries no statement from Ness, Westberry, Spotify, DistroKid or Amazon beyond what each told those outlets or published itself. The mapping to Digital Derangement Syndrome™ is this record’s editorial reading; the quotations are not.