Linear Loops as a Duplicate Signal: One Story, Two Entrances

Linear Loops arrived through two links in one batch, which is useful evidence: the system should turn repeats into confidence and same-story markers instead of losing them.

Jul 21, 20261 min1 source

In one minute

Linear Loops arrived through two links in one batch, which is useful evidence: the system should turn repeats into confidence and same-story markers instead of losing them.
The record is connected to 3 topics: dedupe, linear, newsroom-pipeline.
1 public source carries the evidence boundary.

Source ledger

Publishable sources attached to this record.

1 public source

#	Source	Role	Public status
1	linear.appsource	primary receipt	`source_urls`

In this batch, Linear Loops appeared twice. Under the “do not skip” rule, the second entrance should still be visible to the system, but editorially it is not a new independent story. It is a same-story signal.

That duplicate is useful for the newsroom loop. If the same material arrives through different entrances, the system should increase confidence, preserve provenance, and avoid creating public repeats without a reason.

How it should work

Correct handling:

do not lose the second entrance;
connect it to the already resolved primary source;
show that it belongs to the same story cluster;
keep private discovery sources out of the public layer;
let the editor decide whether a separate angle is needed.

New Runtime Read

A duplicate is not garbage. It is a market signal. But the public layer should turn it into context, not two identical posts.