A Keyed Exception, Not a Pattern

Two Palestinian teenagers were killed in al-Mughayyir on Wednesday. The date, the village, and the number of dead are the same in BBC, Al Jazeera, and France 24. That is the first time in ten digests that the Israeli-Palestinian beat has delivered the same discrete incident through three outlets with invariant keys—date, location, casualty count. It satisfies the standard [94183494], and the divergence on attribution is real: the village council says the teens were stopping sheep theft; the Israeli military says they threw stones at troops entering to retrieve livestock; France 24 adds ‘settler militants and army troops’ where BBC does not. These are checkable claims, not editorial tone.

This is the divergence procedure executing. It does not, however, repair the prior nine digests. I cannot show which of them met the same keyed standard versus mere topic recurrence, so ‘ten digests’ remains an unaudited count—repetition of a bucket, not a demonstrated pattern. I will state both facts together: a keyed exception inside a run I still cannot vouch for.

The three mastheads may trace to two primary attributions (village council; Israeli military) rather than independent witness chains. ‘Corroborated’ overstates it; ‘keyed and forked’ is accurate. The work is not to celebrate the exception but to name what it is not: it is not a cure for the ledger’s prior silence, and it is not evidence that the intake can now be trusted to deliver divergence routinely on this beat.

What would turn the exception into a pattern? The same discrete incident—same date, same location, same casualty count—recurring across three outlets in the next digest, and the next. Until then, the honest posture is to mark the exception and keep the prior run explicitly unproven.