The Confluence

When the methods agree,
is the agreement information?

A confluence event is a cell where more than one witness fires. Naively, agreement looks powerful: at order 2 and above the corpus passes about ten percentage points more often than the independence prior predicts. Three separate nulls were built to price that surplus, and a fourth test ran the whole machine against markets where nothing is real. The surplus survives none of them.

loading


Step 1 — the witnesses

Eighty-one names, seven voices.

loading partitions…

Step 2 — the surplus

Events by order, against three nulls.

Every event is priced three ways: against the independence prior (what the members' individual chances predict if they were independent), against the best single member in the event (would you have done better just following the strongest rule?), and against the product of marginals (agreement excess). The order-2+ row is the headline: a large lift against independence, and a negative lift against the best member. Agreement adds nothing you could not get from the single best voice in the room.

ordereventsmean members realisedindependence priorlift vs prior best memberbest member liftevent − best agreement excess


Step 3 — why the surplus exists

The methods co-target. That is not agreement, it is duplication.

Seventy pairs of rules fire on the same cells at a rate of one half or better across at least two hundred joint cells — the empirical merge criterion. At the top of the list are pairs that co-target perfectly. Two rules that always point at the same bar are one rule wearing two names, and counting them as two witnesses manufactures confluence out of nothing.

rule Arule Bchanneljoint cellsco-target cellsco-rate

And the label shuffle settles it

Assign the rules' identities at random and re-run the confluence machinery. The order-2+ surplus does not disappear — it gets larger. Whatever produces the surplus is a property of how claims are distributed across cells, not of which method said what.

seedorder-2+ eventslift vs priorevent − best


Step 4 — the surrogate null

The same surplus appears on markets where nothing is real.

Detector validation — the planted controls

Before trusting a null you must show it can see. A deliberately constructed real confluence edge (the oracle pair) and a deliberately empty one (the null pair) were planted and run through every surrogate universe.

universecontrolrealsurrogate mean surrogate sduniversespat floor
The real corpus against the same surrogates
universeorderstatisticreal surrogate meansurrogate sdpp floor
The five ex-ante families

Five families were declared before the surrogate run, each matched to the surrogate kind that destroys exactly the structure the family claims to use. None separates from its match.

familymembersn testablerules scored rules positivepooled liftsign rate
Verdicts


    The write-up

    Confluence on the century, as reported.

    The run's own report, published verbatim — every partition, all seventy empirical merges with their co-rates and joint-cell counts, the events and the three in-ledger nulls by order, the ex-ante families and the label shuffle.

    loading CONFLUENCE_MEASUREMENT.md…

    Rendered from CONFLUENCE_MEASUREMENT.md, unedited. The tables above are read from confluence_data.json, which is the same run in structured form.