The criticality gear's prediction on fresh data
This is the load-bearing test: the whole criticality account turns on the claim that the effective number of independent blocks collapses across an onset. It took six runs to find the right quantity to score, and that arc is the lesson.
Dynamic Neff collapse — community-specificity
MEASUREDThe theory's real claim is specificity: before an endogenous cascade, the existing community's block partition collapses harder than a random reshuffle of the same people. That was the primary endpoint, scored by a binomial rule on a fresh roster of 12 r/wallstreetbets cascades disjoint from every prior run (COVID crash, Archegos, Coinbase, the NVDA earnings prints, Credit-Suisse, the 2024 election, and more). It fired at 9 / 12 cascades, binomial p = 1.7×10⁻⁷.
Two properties of this substrate bound how far that number travels, and they are stated because they mark the claim's edge. The per-cascade shuffle nulls on r/wallstreetbets are small — median 90th percentile 0.014 against collapses of 0.24 — so on this forum the specificity bar sits low in absolute terms, and the endpoint carries most information on the cascades whose null is on the same scale as the collapse being scored. There the endpoint behaves exactly as designed: one fires at the 91st percentile, one is correctly silent. The same fact explains the cross-substrate contrast below, since Wikipedia's median event null is 0.491, about 36× larger.
validation/neff_v4/). Left: each cascade's canonical-Neff collapse against its own block-label-shuffle 90th percentile (dots); green bars fire, red do not. The dots also show the substrate's null geometry — ten of the twelve sit below 0.018 while the bars they gate run to 0.35, so on this forum the specificity bar is low in absolute terms. Right: the observed collapse sits at the top of its own 300-shuffle distribution for most cascades. The roster carries no endogenous/exogenous field, so the three non-firing cascades cannot be read as the mechanical or exogenous events.§ Scope. The endpoint is the one near-decomposability names and it ran on fresh data; the magnitude threshold an earlier run failed was not relaxed (that verdict stands, see below). The September-2024 stimulus case is the sharpest illustration of why specificity and magnitude are different quantities here — raw collapse only 0.065, yet above all 300 shuffles, against a null 90th percentile of 0.0028. The per-cascade null arithmetic is reproduced in validation/neff_v4/p0_audit.json; the six-run arc is in validation/NEFF_COLLAPSE_SYNTHESIS.md.
The twist: why magnitude was the wrong yardstick
The raw-magnitude reading — non-discriminating
REPORTED, NOT GATINGTwo earlier runs tested whether the collapse magnitude exceeds a threshold derived from genuinely-quiet windows. They failed, and the failure is informative: it is why we switched to specificity.
validation/neff_v3/). The decisive discovery was in the null itself: short high-volume onset windows compress Neff generically, so quiet windows already drop a median ~0.10. Magnitude therefore cannot tell an endogenous cascade from a busy-but-quiet week on a continuously high-volume forum. The specificity gate (does the real partition beat a shuffle?) discriminates where magnitude cannot.§ The reconciliation. The dynamic collapse is a real structural signal that lives in the block partition (the shuffle test sees it four times) but is not a magnitude excursion beyond a quiet baseline — which the near-decomposability premise never required. Both halves are reported. The full six-pass arc and the synthesis are in validation/NEFF_COLLAPSE_SYNTHESIS.md.
