# TL;DR box reflex 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: summary-box-reflex - Category: Formatting (formatting) - Subcategory: summary-block - Also known as: TL;DR block, summary box on a short piece, what you'll learn preamble - Status: Active. Currently signals low-effort writing. - Severity: low - Evidence grade: community-observed (named by practitioners, no formal measurement exists) - Languages: en - Added: 2026-08-15 - Updated: 2026-08-15 - Page: https://feedsquad.com/ai-tells/summary-box-reflex ## Description A summary block sitting on top of a piece too short to need one. The block restates the body in nearly the same words, so a reader who stops there has read the whole thing twice. ## Why it reads as machine-written Chat interfaces reward a visible answer at the top, and the habit follows the text out of the window. vale-ai-tells carries heading rules for the announcement family, including headings that promise what a reader will learn before the piece has said anything. The judgement is about proportion. On a 2,000-word piece a summary is a service. On a 200-word post it is the post. ## Detection Type: judge (a rubric for a lightweight model judge) Rubric for a lightweight model judge: ```text Count the words in the body, excluding the summary block. If the body runs to 400 words or more, return no hit. Below that, list every fact stated in the summary block, then check each one against the body. Escape hatches that mean no hit: the block carries a figure, a date, a name or a caveat the body never repeats; the surface is documentation whose summary is a navigation aid; the publishing template requires a summary field. If every fact in the block already appears in the body and the block adds nothing, return a hit and quote the block. Otherwise return no hit. ``` ## Examples Constructed specimens. Written for this index. Never quoted from anyone's posts. ### Specimen 1 Before, exhibiting the tell: > TL;DR: We moved our newsletter to a new provider and it went fine. > > We moved our newsletter to a new provider last month. It went fine. Deliverability held and the API took an afternoon to wire up. After, repaired: > We moved our newsletter to a new provider last month. The migration took an afternoon, and the only thing that broke was the unsubscribe link in our oldest template, which had been hard-coded in 2023. Open rates did not move either way across the first three sends. Note: Figures in this repair are invented for the specimen. ## False positives Who legitimately writes this way. Long-form journalism and technical documentation put a summary at the top for readers who will not reach the end, and that is a service to them rather than a habit. Academic abstracts, executive summaries and legal head-notes are required by the form and cannot be dropped. Many content management templates render a summary automatically out of the field the writer filled in for search results, so it never passed through a writing decision. Judge proportion and novelty together: a block carrying a figure or a caveat the body never repeats is doing work, and one paraphrasing a 200-word post is filling a slot. ## Model attribution Undocumented. No vendor names a summary-block instruction in anything this project read, and no study measures the habit. The evidence here is one machine-checkable rule set plus our own review queue, which is why the grade sits where it does. ## Platform notes - linkedin: The first two lines are the only part shown before the more link, so a summary block spends the whole preview restating what follows it. ## Sources 1. vale-ai-tells, 111 machine-checkable rules https://github.com/tbhb/vale-ai-tells (tier: community; accessed 2026-08-14) 2. FeedSquad review queue, summary blocks on short agent drafts (FeedSquad observation) Corpus: Agent-drafted LinkedIn and blog posts held for human approval in the FeedSquad review queue, weeks 30 to 33 of 2026. No sample count is claimed; the observation is qualitative and is the reason this entry carries the lowest evidence grade with an external source attached. Observed 2026-08-15 ## Status history Ids are permanent. A retired tell keeps its id and its page. - 2026-08-15, Active: Active with a low grade and low severity, which is the honest pairing. One machine-checkable rule set carries heading rules for the announcement family, and the rest of the support is our own review queue, named as a source rather than dressed up as measurement. The rubric is gated on body length so that long-form summaries never register. ## 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.