Methodology
How the Agent Traffic Index is computed
We wrote these rules before we had any data, so they cannot bend to it.
The index aggregates requests observed by gateways our customers installed. The subject of every number is a site, an agent, or a request. No number here has a person as its subject, and none ever will.
Nothing on this page is an ARS score, so nothing here carries a grade or a measured/heuristic split. These are counts and shares from our own event log.
Floors
What has to be true before a cell is published
k = 25 independent stores per cell
Every published cell must be computed over at least 25 distinct stores. The floor lives in the SQL as a HAVING clause, not in the reporting layer, so a cell that does not clear it cannot be selected in the first place.
It is not a tunable and it is not a starting point. There is no configuration value, no environment variable, and no admin toggle that lowers it.
No store may be more than 20% of a cell
The floor alone is not enough for volume metrics. If one store is 95% of the traffic, 25 stores is effectively one store. So every cell also carries a per-store contribution cap of 20%, computed from per-store rows rather than a summary column.
A cell that fails the cap is withheld. We do not rescale or trim it to make it publishable.
Independence is defined, not assumed
A store counts toward k when it is not first-party, has not opted out, and cleared 100 events in the 30-day window. Without the minimum-events predicate, k would count stores that sent us a single request.
trymumm.com posts events into the same log through the public ingest path. Our own stores do not count as independent, so first-party stores are excluded from the numerator, the denominator, and k.
Opting out is total
A per-store opt-out removes the store from the numerator, the denominator, and the k count. No store is ever named here, so opting out removes the store's data from the computation entirely.
The opt-out must be in the merchant terms before the first publication, not after it.
Publication
How and how often
Monthly, and cadence is a privacy parameter
Two consecutive snapshots differ by whatever changed between them. The shorter the period, the easier it is to trace that difference to one store joining or leaving. A weekly series leaks more than a monthly one over the same population, at the same k.
So the cadence is set on privacy grounds, not engagement. We will not shorten it to make the charts more interesting, and any change to it requires a privacy review.
Shares and percentiles. No absolute total.
Published cuts carry shares of a mix and distribution percentiles. There is no absolute network total, and no cut publishes a total next to all of its parts, because that would let anyone recover a single part by subtraction and defeat the floor.
Pre-declared cuts only
The cuts are fixed and published in advance. There is no query builder, no interactive slicer, and no filter parameter on the page. A per-query floor protects nothing if a caller can run unlimited queries against the same population.
Snapshot tables, never live queries
Numbers are published from a snapshot written by an explicit job. Each publish gets one audit row recording what was computed, over what window, under which floors. A page that queried the live log would show a different population on every request, none of it reviewed.
Not built yet
What still has to land before the first publication
Nothing is published until all of these exist.
The snapshot table and the audit rowPlanned
Neither exists yet. Until they do there is no code path on /agent-traffic that can render a share. The page holds a counter and nothing else.
The ARCHITECTURE.md subsection for this crossingPlanned
The canonical docs describe MUMM reading Rebilder data. This index is merchant data flowing to the public, which is a different crossing with different rules, and it needs its own subsection before the first publication rather than after it.
Merchant terms covering the opt-outPlanned
The per-store opt-out has to be in the terms a merchant agreed to before any of their traffic contributes to a published number.