01 / NEWS WITH CONTEXTDo not confuse duplicate text with one event
Repeated delivery of one item is not the same as several publishers reporting on one event. Keep original records intact and attach grouping relationships when clustering helps the reader. Test recurring event names and follow-up reports. Similar wording can be a clue, but it should not erase independent sources or differing perspectives.
02 / NEWS WITH CONTEXTPreserve source and correction relationships
Preserve publisher identity, canonical links, and the relationship between a revised story and its earlier version when available. Mark your own observations as observations rather than publisher-declared corrections. A summary based on an old representation should be reviewed when a substantive source change affects its meaning or supporting evidence.
03 / NEWS WITH CONTEXTSeparate publication status from ranking
Carry explicit source publication status through the workflow where the source format provides it. A relevance score should not override an editorial hold. Keep unknown status unknown when no signal exists. Define which decisions the queue automates and which require a reviewer before content appears in a public or consequential view.
Follow one story through its revisions
Build a local sequence with an initial report, a correction, an independent account, and a commentary piece. Check that your queue preserves each source and explains the relationships without flattening them into one authoritative summary. Add a hold or withdrawal signal when the source format supports it. Use the exercise to define the decisions that require editorial review.