Complaints & challenges
How to challenge a value, a rule, or a constituent. No account required.
Anyone may challenge a benchmark value, a rule, a constituent, or a classification. No account, subscription, or relationship with W.E.T. is required.
How to raise one
Email indices@worldeventtrading.com with:
- the benchmark and the settlement date(s) concerned;
- what you believe is wrong;
- anything supporting it (a venue price, a resolution source, a computation).
What we commit to
| Stage | Timeline |
|---|---|
| Acknowledgement | 2 business days |
| Substantive response | 10 business days |
| If it needs investigation | Interim response at 10 days with an expected date |
What happens to it
- Every challenge is logged, including the ones we reject, with the reason.
- A challenge that identifies a genuine error triggers data-errors.md and, where it meets the bar, restatement.md.
- A challenge to a rule rather than a value is treated as consultation input under methodology-change.md.
- Outcomes affecting a published value are published, whether or not the challenger asks.
What makes a challenge easy to make
Every settlement row records the engine, rubric, classifier and methodology versions that produced it, plus each constituent, its severity class, the rule that classified it, the venues consolidated, and whether it was single-venue or provisional. You do not need our cooperation to check our work — that is the point of publishing it that way.
The rest of the set
Methodology change & consultation
What counts as a material change, the 14-day consultation window, and why changes are prospective.
Data licence & rights
What the free tier grants, what attribution it requires, and what commercial use needs.
The loop architecture
The nine scheduled agents that cultivate indices, which one may publish, and the six mechanisms that assure accuracy.
The confirm gate
What human confirmation covers — merges only — and how to read the provisional and single-venue counts.
Restatement policy
The three narrow conditions under which a published value may be corrected — and the many under which it may not.
Cessation & fallback
What happens when a benchmark cannot be computed, and why the history stays published forever.
Conflicts & the conflict wall
The wall between index operations and the trading circuit, plus standing disclosures.
Data-error playbook
Detection, triage, quarantine — and the commitment to disclose errors nobody noticed.
Settlement-reference licensing
What licensing a benchmark to settle against requires — and why publication alone does not grant it. Reading a value is free; referencing it in something that settles is not the same act.
Determination, disruption & cessation
Written for contracts rather than charts: who determines a final value, the disruption fallback ladder, and why a refusal is not a cessation.
The independent committee seat
The seven-part independence test, published before a candidate exists; the power to block rather than comment; and what the administrator may do while the seat is vacant.
Incident process
Who is paged, what they do, and what gets published when the machinery fails — as distinct from a wrong value, which is the data-error playbook.
Finding — the WETX coverage breach, August 2026
Why WETX refused for five consecutive days, the change that caused it, and what is still not established. Published because an availability figure without the incidents behind it is a number nobody can check.