Every number can be traced to a source, a date, and a method.

One direction only. Facts never skip a stage.

Field set

Every operator profile leads with the same four counts, in two lines. They measure different things and are never parts of one sum — this is exactly what the profile renders:

X, Y, N, M, K are each operator's own counts. The last segment shows only when K > 0.

Core fields — of 7

the seven fields worth knowing before the rest of a profile means much (listed below). A gap here is not the same as a gap anywhere else, so they are counted on their own.

Tracked fields — of 32

coverage: how many of the fixed 32-field list we hold on file, each with a source and a check date. It counts fields, not rows, and can never exceed 32.

N sourced facts

the lead number, and the order of the catalog — the total volume of sourced rows on file. A field can hold more than one row, so this is not the same as coverage.

on tracked fields · beyond the tracked set

the same sourced rows split in two: those that land on a tracked field, and those the list has no slot for.* Both carry sources and dates; they are rows, not fields, so they never fold into coverage.

The 32-field list is fixed in advance and published below, so coverage means the same thing for every operator — the denominator is settled before the counting starts, never stretched to fit what a given site happens to publish.

A field we have not established is shown empty. We never fill one to make a profile look complete — an empty row is information too.

The set is versioned. When a field is added, every operator's coverage moves with it, and the change is recorded in the methodology changelog.

Five weighted components, published in full

No component can be bought. Sentiment is never a weight.

Machine-classified by a voting panel, measured against a hand-graded sample

To show the mix of what communities say — without inventing a sentiment number — a panel of three independent foreign-vendor models labels each mention into a reputation bucket, with an independent arbiter resolving disagreements and the accusatory calls. The label is data, not a score: it never enters any Score at any weight, and its accuracy is measured against a hand-graded sample the panel never sees, and the measurement is published with the version that produced it.

1. 01 Three foreign-vendor voters (OpenAI, Google, DeepSeek) + an independent Anthropic arbiter on any disagreement or accusatory call — no single model decides, and the arbiter is never shown which brand collected the row.
2. 02 Precedence: spam > sponsored > negative > positive > neutral (promo and spam are never genuine signal).
3. 03 Versioned (classifier_v1) and re-runnable; every label records the rules that fired.
4. 04 Quora is in the expansion queue — nothing from it is counted yet. Telegram joins once its public-channel list is active.

Bucket mix is context, published as counts. It does not enter any Score.

40 prompts × 4 engines, read by hand

Players' Choice: popularity, counted honestly

Players' Choice is a popularity signal and nothing more — it never enters a safety rating. Each signed-in player casts one vote per week, “for” an operator; the week runs Monday to Monday, UTC. An operator's number is the count of accepted votes over a rolling 90 days. A vote is final once cast and cannot be changed before Monday.

Anti-abuse runs the moment a vote lands. A burst of votes from one network within minutes is recorded as rejected, with its reason, and does not enter the count.

We keep only what anti-abuse needs — the age of the account and a hashed network prefix. The raw IP address is never stored. A player's votes are deleted together with their account.

Observed on-chain outflows

For operators whose payout wallets we can attribute, we watch the rhythm of outgoing payments on-chain. An outflow is a transaction where an attributed wallet is the sender. We publish counts over rolling windows (24h · 7d · 30d), the median interval between outflows over 7 days, and the time of the last observed outflow — never balances, never amounts, never deposits.

Every attributed wallet carries a method, a source and a check date. A wallet with no recoverable source is unverified and never enters the public flow.

• Known hot wallets only — operators rotate wallets, so coverage is non-exhaustive.
• Absence of observed activity ≠ absence of payouts.
• Observed from public chain data, deduplicated by transaction hash.

Withdrawal flow is observed activity — it does not enter any Score at any weight. It is context for future Tested payout measurements.