# Manufactured rage-bait take Part of [The AI Tells Index](https://feedsquad.com/ai-tells). A tell signals low effort. It does not identify an author. Skilled writers produce every shape listed here, some of them daily, and automated detectors misread those writers for it at rates measured above 60 percent on non-native English prose. Nothing in this index proves that a machine wrote anything. Read an entry as one piece of evidence to weigh against the false-positive notes printed beside it. ## Facts - Id: manufactured-ragebait - Category: Platform-specific (platform) - Subcategory: engagement-bait - Also known as: deliberately wrong hot take, post engineered to be corrected - Status: Contested. Credible people dispute that this signals anything at all. - Severity: medium - Evidence grade: primary-doc (platform policy, vendor documentation, or a model card) - Languages: en - Added: 2026-08-15 - Updated: 2026-08-15 - Page: https://feedsquad.com/ai-tells/manufactured-ragebait ## Description A claim published because it will be corrected, where the corrections are the product. X enforces the coordinated version of this under engagement spam, which it frames as inauthentic use of engagement features to artificially affect traffic. A single post cannot be judged this way and this entry says so in its own rubric. ## Why it reads as machine-written Being wrong in public is a reliable way to generate replies, and generation makes a confident wrong claim cheap to produce on demand. The pattern only becomes visible across an account's output, where the absence of corrections separates a person with bad opinions from an account built to harvest replies. ## Detection Type: judge (a rubric for a lightweight model judge) Rubric for a lightweight model judge: ```text Return no-tell for any single post, because intent cannot be read off one text and this rubric will not pretend otherwise. Score an account instead. Over its last 30 posts, count the ones asserting something checkably wrong in a field the account claims to work in, then count how many of those the account later corrected. Also count how often the account amplifies the corrections it receives instead of editing the claim. Return tell only when wrong assertions are frequent, corrections are absent, and amplification of the replies is the visible pattern, listing the posts counted. ``` ## Examples Constructed specimens. Written for this index. Never quoted from anyone's posts. ### Specimen 1 Before, exhibiting the tell: > Nobody in marketing has ever needed a spreadsheet. Every metric that matters fits in your head. If you disagree, you are the problem. After, repaired: > We stopped keeping a weekly metrics spreadsheet in April and put one number on a whiteboard instead: qualified demos booked. Two people warned me this would break forecasting. It did, mildly, and we added a second number in June. Note: The repair keeps the contrarian position and attaches the cost of holding it. ## False positives Who legitimately writes this way. Sincerely held bad opinions are not bait, and the internet is full of people who are confidently wrong for free. Satire reads identically to the thing it satirises when quoted out of context. Provocation is also a legitimate teaching device: naming the wrong version first is how a lot of people explain the right one. The reviewer check is the correction record, because a person who is wrong in good faith eventually says so and an account farming replies never does. ## Model attribution No family attribution. X withholds the prompts behind its slop labels, and no vendor documents a tendency toward provocation. ## Platform notes - x: The April 2025 authenticity policy names content spam, covering bulk, duplicative, irrelevant or unsolicited posting, and engagement spam, covering inauthentic use of engagement features to artificially affect traffic. Both are framed as behaviour and volume. The policy does not name any writing formula, and the widely repeated claim that X's monetisation standards ban engagement bait and recycled content is not in that page. ## Sources 1. X authenticity policy, content and engagement spam https://help.x.com/en/rules-and-policies/authenticity (tier: primary-doc; accessed 2026-08-14) ## Status history Ids are permanent. A retired tell keeps its id and its page. - 2026-08-15, Contested: X's policy reaches the coordinated case and says nothing about a lone provocative post, and intent is not observable from one text. Contested is the only honest status for a tell whose definition depends on a motive nobody can see. ## License CC BY 4.0. https://creativecommons.org/licenses/by/4.0/ Attribution: The AI Tells Index, feedsquad.com/ai-tells Reuse the data, including commercially. Keep the attribution line. --- Dataset version 1.0.0. Schema version 1. Part of [FeedSquad](https://feedsquad.com). Built by [Herman Foundry](https://hermanfoundry.com) from Levi, Finnish Lapland.