Repository navigation
v2.7.4
New in v2.7.4
The short version: one new advisory signal joins the herd family. Where herd-phase (v2.7.3) asks whether a fleet's members share one timer offset, herd-tightness asks whether a whole group's timing points sit suspiciously on top of each other - the shape a single scheduler leaves on an entire cohort at once. Nothing on the default path changes.
- One scheduler, one tight knot of points. Feed the new
createHerdTightnessSignalthe same repeated timestamps you already feed herd-phase (session starts, room joins), plus a reference stream from your established legitimate users. Each account becomes one point on a phase map; a fleet driven by one scheduler lands all its points in one tight knot, while real people - including a whole office behind one IP on office hours - spread out. In the pre-registered lab, a single frozen bar separated the two on two fresh held-out populations it had never seen: the shared-scheduler herd read 0.26-0.28 against the bar 0.81, legitimate users 1.09-1.36, the office-hours group 1.39-1.72, smallest margin 35.9%. The shipped module was then re-measured on the lab's own populations and reproduced every value to the last printed digit. - What it refuses to do. The statistic describes a whole group, never a person: no output names an account. A fleet whose bots each keep their own timer reads spread out and is not flagged - that shape belongs to herd-phase's cohort statistic, not this one; the two signals are companions, not substitutes. And without a reference stream the module issues no verdict at all: it reports the raw number with status "uncalibrated" rather than guessing. Advisory only, like everything in this tier - evidence for an accumulator or a human, never a block.
- The first design failed, on the record. The candidate's first registered form filtered "outlier" points before measuring - and the filter deleted the entire bot cloud on the calibration draw, because a tight herd sitting far from the legitimate centre looks like outliers. That run was void; the filter was removed, not loosened; the re-registered form is the one that passed. The full story, with numbers, is in the deep dive.
Full technical write-up: v2.7.4 deep dive. What the previous release changed: v2.7.3 deep dive.