Monday’s war coverage offers a clean specimen of official language surviving its own contradictions. CBS News reports that Israel’s military said it “was committed to the ceasefire but would continue to ‘remove threats’ from Hezbollah” [1]. Read it twice. A ceasefire that includes strikes is not a ceasefire; it is the word ceasefire surviving its own definition. Orwell called this doublethink: holding two contradictory commitments at once and accepting both. Here it arrives pre-packaged as a defense statement, and the outlet passes it through unmarked.
The verb does the work
“Remove threats” is pest-control grammar, one entry in a small euphemism laundering set this coverage runs on. Threats are removed like mold or old furniture; the object of the verb is a category, not a person, so nobody dies in that sentence. The twelve people the Lebanese health ministry counted do not appear in it [1]. Notice where they do appear: in a subordinate clause. The article’s opening sentence hangs the deaths off the army’s self-description, “after the Lebanese health ministry reported 12 people killed in overnight strikes” [1]. The body count is grammatically secondary to the messaging.
The military’s second formulation is even better, because it compresses the contradiction into one clause: it “will continue to operate to remove threats while remaining committed to the ceasefire agreement” [1]. Operating and ceasing, simultaneously, as fidelity.
Infrastructure, and the school books
The same article says the military struck Hezbollah “infrastructure sites” across southern Lebanon [1]. Paragraphs later, the same article reports that in Kfar Rumman “school books and remnants of furniture were among the rubble,” that the building was destroyed with eleven people killed, and that a resident, Fouad Chakaron, described the inhabitants as “peaceful people with no connection to anyone” [1]. ABC, citing Lebanon’s state news agency, counts “at least 11 people” dead there, “among them two children,” and notes that “Israel has not commented on the strikes in Kfar Rumman” [2]. (The two outlets’ overnight totals, eleven and twelve, coexist without reconciliation; CBS’s health ministry figure includes a rescuer killed in a second attack [1].)
A caveat, stated plainly: CBS never says the “infrastructure sites” claim refers to Kfar Rumman specifically. Maybe it does; maybe it covers other strikes. The reader cannot tell, and that vagueness is itself the finding. The euphemism and the school books sit in the same article, and neither is asked about the other. The one sentence that would join them, the military says infrastructure and the rubble contained school books, is not opinion; it is sequence. Its absence is the tell.
The passive voice has a nationality
The most complete Newspeak artifact in either piece is this: “The claim that several uninvolved individuals were harmed as a result of the strikes is being reviewed” [1]. Take it apart. Civilians become “uninvolved individuals,” as though the salient moral fact about dead noncombatants were their non-membership in a category the state defines. Killed becomes “harmed,” a verb for bruises. The sentence’s only action is the agentless passive “is being reviewed”: no reviewer, no deadline, no consequence. The claim reviews itself, indefinitely.
Compare the sentence CBS built from the health ministry: “12 people killed in overnight strikes” [1]. One sentence has an actor and a number; the other has neither. Both run at equal authority.
The asymmetry is consistent. Two Israeli soldiers “were lightly injured” in what the military called “the close-quarters encounter,” and the adverb of degree survives editing [1]. The twelve Lebanese dead get no adverbs. The man who “opened fire on its troops from inside a building” is killed inside a subordinate clause of the sentence about those light injuries [1]. To be fair, CBS does know how to mark contested language: it scare-quotes “several terrorists” and attributes the word [1]. But nearby, the killing of the Hezbollah member is flat assertion [1]. The distancing device appears and disappears within a single paragraph, and it is deployed selectively: Tehran’s ships travel “in what it calls unauthorized routes” [1], a “what it calls” construction that never attaches to “infrastructure sites.”
At sea, a mechanic’s verb
The same register difference runs through the tanker war. When Iran hit a Saudi-flagged vessel, CBS wrote actively: Iran “attacked the vessel,” and the article names the dead by nationality (two Filipino sailors) and counts the rescued (sixteen of a twenty-five-member crew) [1]. When the United States acted, Central Command’s verb was mechanical: it had “permanently disabled” three Iranian oil tankers [1]. “Disabled” is what you do to a machine. A tanker is a floating workplace; the Saudi one carried twenty-five people [1]. Whether anyone was aboard the three Iranian tankers is not reported in either account [1][2], and the question is not asked. I flag this as an omission, not a finding: I do not know whether those crews were harmed. But notice which deaths arrive with a nationality and a rescue count, and which strikes arrive with a verb from a repair manual.
The CENTCOM statement, quoted in full by CBS, makes the accounting explicit: “If you shoot at two of our ships, we will impose an even higher economic cost — taking out three of yours” [1]. Sinking ships as a line item. The register runs through the American vocabulary generally: “major combat operations,” a “crushing economic operation” [2]. War renamed operations; destruction renamed cost. The one plain verb in the statement, a promise to “destroy Iran’s limited and exposed oil fleet” [1], is honest precisely because it is a taunt. Candor is reserved for threats; euphemism for consequences.
Tehran speaks the same dialect, to be sure: a “restricted prohibited zone” [2] that doubles its own adjective, an “exclusion zone” [1], military bases reduced to ones “that are no longer viable” [2]. One more unexamined item: the word “blockade” appears in both articles, but only inside quoted Iranian officials’ remarks about a “U.S. naval blockade” or the U.S. Navy’s “blockade line” [1][2]. Neither outlet says in its own voice whether a blockade exists, what it consists of, or since when. The word is printed, attributed, and dropped.
The retaliation chain with no origin
Every action in this coverage is a response. The U.S. strikes came “in retaliation for previous attacks” [1]; Tehran “responded by announcing it had targeted more ships” [1]; the Iranian parliament speaker declares that “the era of proportionate responses has come to an end” [1]. The ledger resets each cycle. The origin does exist in the record, but only in the market paragraphs: “Prices shot up after the U.S. and Israel attacked Iran in February” [1]. February’s war-starting is a price event; Saturday’s strike is a retaliation. The same selective passivity appears in the nuclear section, where Iran must account for safeguarded material “following attacks on its facilities,” attacks Grossi said “should never take place” [1]. Attacked by whom? The sentence does not say, though the same article names who attacked Iran in February [1]. The passive voice activates for one side and idles for the other.
The pump
Then there is the frame the whole package ships in. CBS’s headline: “Oil prices up as Iran says it will expand control over Strait of Hormuz” [1]. Twelve people killed in overnight strikes open the article and cannot reach the headline; the gas price closes the article and is the headline. This is the Huxley half of the mechanism. The Orwellian move hides violence inside the vocabulary; the Huxleyan move makes sure the version of the war that reaches you is the one you can feel at a gas station: $4.14 a gallon, “nearly a dollar higher than last year,” a Labor Day record, “heading into the holiday” [1]. Kfar Rumman’s dead, two Filipino sailors, a killed rescuer [1]: subplot to the price of a road trip. The headline’s causality is also a choice. Iran’s announcement moves the market, while the American disabling of three tankers days earlier is mid-article context [1].
ABC’s format completes the picture: a live-updates page [2] where the war arrives as a feed, each item credited and then displaced by the next, nothing reconciled with anything. A live blog cannot repeat itself unexamined; it never repeats itself at all.
What a reader would need instead
None of this requires editorializing. It requires follow-up, which is the opposite of stenography. Neither article names any monitoring body for the Israel-Hezbollah truce; the word “ceasefire” floats free of any institution that could say whether strikes under it are violations [1][2]. The UN Interim Force in Lebanon exists for exactly that question and goes unmentioned. Casualty claims have accounting bodies: the Lebanese health ministry is already cited [1], and organizations like the UN’s humanitarian coordination office and the casualty-tracking group Airwars exist to do the verification that “is being reviewed” defers. The International Maritime Organization appears in this coverage only as the registry for an Iran-Oman traffic route [1]; neither outlet consults any maritime authority on what “permanently disabled” means for the ships and crews involved. The IAEA is present and quotable [1]; what the article never adds, in its own voice, is who attacked the facilities whose safeguards lapsed, though it says elsewhere who attacked Iran in February [1].
Orwell’s duck quacks articulately, with no thought arriving at the beak. The test of Monday’s coverage is that the quack and the counterevidence coexist without friction: “committed to the ceasefire” beside twelve dead, “infrastructure sites” beside school books, “uninvolved individuals were harmed” beside a rescuer killed in a second attack [1]. The reader is asked to hold it all, unconnected. The repair is a sentence, not a sermon: the military says infrastructure, and the rubble contained school books. Write the sentence and see if it survives.