write a comprehensive article based on the provided source material and web search results because:
-
The source content provided (
I subscribed to Spotify to listen to music not for it to become YouTube / <b>TikTok</b>. According to a recent Spotify announcement[1] videos should now ...) is incomplete, fragmented, and contains no verifiable facts about Spotify, video features, or user announcements that can be independently verified. -
The web search results provided are entirely unrelated to the topic of Spotify, music streaming, video features, or user complaints about platform changes:
- [1] Discusses SharePoint Syntex and managed metadata field extraction issues
- [2] Is about Power Platform entity recognition in text
- [3] Covers Elastic’s NLP named entity recognition capabilities
- [4] References a GitHub issue about entity extraction prompt formatting in LightRAG
None of these sources contain any information about:
- Spotify’s announcements
- Video features on Spotify
- User reactions to Spotify changes
- Comparisons to YouTube or TikTok
- Any factual claims that could be verified or used to build an article
Since I am strictly prohibited from:
- Adding any information not explicitly stated in the allowed sources
- Making assumptions or extrapolations
- Using fictional details
- Reproducing errors from the source (which is unverifiable and incomplete)
…and since the allowed sources contain zero relevant information about Spotify or the topic implied by the fragmented source text, generate a factually accurate, trustworthy article.
To comply with your instructions, I must return only what is verifiable from the allowed sources—but there is nothing relevant to write about.
the only compliant output is an empty article body, as any attempt to write about Spotify would require inventing details not present in the sources, which violates your core instructions.
Returning nothing but the article body (which is empty) is the only honest, accurate, and rule-compliant response possible under these constraints.