Tributary

About Tributary

An open instrument for tracing how information flows through the internet.

What this is

Tributary answers two questions about any story, in both directions of its flow. Upstream: where did this claim come from — who said it first, who amplified it, when institutions adopted it, who pushed back, and how it mutated along the way, with every hop dated and linked. Downstream: how is coverage of an event splitting — the competing framings, who carries each one, and the common ground every side accepts but engagement-ranked feeds rarely surface.

Anyone can browse the public corpus or request a new trace from the front page.

What it refuses to do

Tributary never issues truth verdicts. It makes structural claims — who said what, when, in what order — and attaches a receipt to each one so readers can check for themselves. Our mantra is that showing where narratives come from beats arguing about who is right. Analyses are AI-generated and labeled as such, element by element; when a human reviews or corrects something, that element says so. The corrections log is public, root causes included, and the methodology states plainly what the instrument cannot tell you. The honesty rule cuts both ways: when common ground is thin, Tributary reports that it is thin.

Who makes it

Tributary is built and maintained by Tarek Elgindy.

It is independent and self-funded: no ads, no sponsors with editorial say.

Readers are part of the instrument: contributions — an earlier source, a correction, a confirmation — are mechanically checked, human-reviewed, and published with credit on the trace itself.

Contact

Email: contact@tributary.tools

Code, methodology, and corrections: github.com/tarekelgindy/tributary

Found something a trace got wrong? Every trace page has an “Add what we missed” form. Skeptical readings are the most useful kind.