This guide describes the reporting contract, not a statement that current reporting is restored. Historical reporting still requires restoration and validation. No performance totals are published here.
A performance total only means something when it counts rows a user could actually follow. Edge93 keeps a raw audit ledger, but public reporting uses a separate deduped pick ledger.
The public result buckets
| Bucket | Meaning | Public performance |
|---|---|---|
| Shown prematch pick | A prematch pick visible to users | Included |
| Shown live signal | A live signal visible during the match | Included |
| Live read | Current analytics and market context | Excluded |
| Internal evaluation | A candidate used for research or QA | Excluded |
One pick, one result
Repeated source rows are collapsed by fixture, market, line, selection, scope, and result bucket. The earliest user-visible timestamp and first public price define the receipt, while duplicate counts remain available for audit.
Settlement after full time
The reporting contract requires a validated settlement and prevents an older pending label from reopening a finished match. A receipt should show WON, LOST or VOID only when the canonical evidence supports it. Restoration and validation of the reporting consumers remain pending; this describes the required behaviour, not current service health.
Public results should answer a simple question: if a user could see this row at the time, what happened to it? Context is not counted as a betting result; internal research remains separate from public reporting.