Review Desk — Event Dedup

Connect to load the docket.

runner… natural

Granularity γ 0.09

Axis

Tick the clusters that belong to your narrative, then read the barometer.

Scenario

What a tracker follows: countries and tags from the lists, and a plain description in short sentences, one aspect each. No keywords. Every event and post in the window is ranked by similarity to the description and by its country and tag keys; Haiku reads down that ranking and keeps what it calls core, with a one-line reason, and stops after 100 items in a row with nothing core. The same selection the trackers use (leiden_runner/relevance.py). The axis plays no part in it.

from to

Explore clusters optional

The list on the left is what the corpus clusters into on its own — no input from you. A gate narrows the candidate set and re-clusters just that slice. Ticking clusters builds a pool by hand; its social posts are the ones that link to its events.

✓ Agree is the default: you agree with what the agent proposes. Click ✗ Disagree only where the agent is wrong, and type why in the box that opens: it saves by itself as you type (the note is what the agent learns from). Each line shows what Apply accepted will do with your choice, using the same paths as the Review tab.

Open this tab to load the agent's proposals.

Registry hide speculative

Reload to load pending changes.

Review Desk / event dedup

Contrast axis

Query history