In a recent note I published Our LLM Telemetry Stayed Green While the Work Moved to Codex. A draft reader-improvement plan offered it a new feed title:
The Telemetry Job Passed. It No Longer Saw Most of the Work.
It reads better than the original. I rejected it, because the word "most" makes a claim the article cannot back.
The plan proposed new titles and summaries for three already-published notes. Before using any of them, I compared every surface each note shows a reader: the HTML title, the h1, the Open Graph title, the meta description, the summary on the notes list card, the summary box at the top of the page, and the body. The question for each surface was the same. Does it promise anything the body does not deliver?
One note's surfaces already matched its body. The other two are the reason for this note.
The telemetry note is about a weekly report that kept passing its health checks after my unattended work moved to a tool its ingest never reads. The body is careful on one point in particular. It says the routing change moved a share of the work out of the table entirely, and that "the table had no column in which to say how large that share was."
"It no longer saw most of the work" fills in that column. It asserts a majority, a share over half of some total, and the article never measures that share. That is not a stylistic edit. It is a new quantitative claim on the surface of an article whose body explicitly declines to make it.
The plan was not careless about this. Its own notes said "most" should only be used after checking the period and the denominator in the original observations. The review did that check, and the denominator is not there.
It is tempting to rebuild one from numbers the article does print. The body has weekly counts of transcript files from each tool, and one column of those counts dwindles to almost nothing. But the article states that those are files, not sessions, and that the two columns are not comparable as workloads. A falling column shows that work left one place. It does not show what fraction of all work left. Using either column as a denominator would put a number on the title that the body specifically warns against.
The second rejection was subtler. For Sub-Agent Metrics Are Not Comparable to Main-Thread Metrics, the plan offered "Keep Main and Sub-Agent Metrics Separate."
That sounds like a faithful summary. It leaves out what comes after separation. The body shows that a pooled ranking of models can reverse once you account for the mix of roles each model ran in, and then says outright that stratifying is step one, not the answer: metrics can mean different things in each stratum, and the role gap is not a constant you can adjust away. A title telling readers to keep the metrics separate promises that separation solves a problem the body says it only begins to address.
That article has striking numbers in it, including a role gap of up to 135x and main-thread shares ranging from 1.5% to 71.4% across models. They would make a punchier title. None of them supports "keep them separate" as the answer, and none of them says anything about how much work moved anywhere.
The pipeline that turns drafts into published notes has a written content contract that both the writing step and the validation step follow. I added one rule to it.
Any quantifier on a title, description, Open Graph title or dev.to title (words like most, all and never, multipliers, and percentages) needs a sentence in the body that supports the same value over the same denominator. Promises of a fix, a time saving or a ratio need a body that contains the actual repair procedure or measurement. The validator has to quote the supporting body sentence, or write that the claim is unsupported.
This is a semantic review against the body, by whoever is writing or validating. It is not a machine check that parses numbers, and I'm not claiming it catches every overreach. It moves the question to the moment a surface is written, and it forces the answer into the form of a quoted sentence instead of a feeling.
One adjacent detail matters for the same reason. The description in a draft's front matter is copied to the list card as-is, with no truncation step. So a description has to be a complete sentence that keeps the same promise as the title, because that is exactly what a reader sees on the card.
No existing title, card or published post was changed. The rule applies to notes written from now on.
I have not measured whether stronger or weaker titles change click-through or readership, and nothing here claims they do. If I measure it later, it won't be by changing a title, a summary and a social card on the same day and crediting whatever moves to one of them. Several surfaces changing at once cannot isolate one element's effect. Any such measurement will use the cohort and probe rules I already have, not success thresholds invented for the occasion.
This note's own title says the candidate promised a share the data did not measure. The body sentence that carries it is the one quoted above from the telemetry note. Its table had no column for the size of the moved share, and the candidate title asserted that the share was a majority.
It asserts a share over half of some total. The telemetry note's body says its table had no column showing how large the moved share was, so a title saying the job no longer saw most of the work added a majority the body never measured.
Not in that note. Its body says the weekly counts are files, not sessions, and that the two tools' columns are not comparable as workloads. A dwindling column shows work left one place, not what fraction of all work left.
Any quantifier such as most, all, never, a multiplier or a percentage on a title, description, Open Graph title or dev.to title needs a body sentence supporting the same value and denominator. Fix, time-saving and ratio promises need the actual procedure or measurement, and the validator quotes the supporting sentence or marks the claim unsupported.
No. It is a semantic review against the body during writing and validation of new notes. It does not parse numbers, and no existing titles, cards or posts were changed.
That was not measured. Changing several surfaces on the same day could not attribute an effect to any one of them, and any later measurement would use existing cohort and probe rules.