Overview
Match lifecycle
StatForge tracks each match from initial signal through review to a verified outcome, published once downstream systems can rely on it.
Every official result moves through a clear lifecycle so your platform, admins, and integrations can rely on the same status model.
Lifecycle
Detected → Reported → Under review → Verified → Published
Alternate outcomes: Disputed · Rejected
What this means
- Detected
- Gameplay signals or source data indicate that a match may have occurred.
- Reported
- A structured report, event submission, or additional source input is attached.
- Under review
- The match is being evaluated against available signals and evidence.
- Verified
- The outcome has passed review and is accepted as official.
- Published
- The verified result is available to public and integration surfaces.
Alternate outcomes:
- Disputed
- The outcome remains contested and is not treated as final.
- Rejected
- The candidate does not meet the standard for publication as an official result.
Why this matters
This lifecycle gives every system using StatForge a shared definition of what is official.
- Fans see published results.
- Operators work in the portal.
- Integrations consume the same final states through the API.
For customers
Your workspace may include additional operational rules, workflows, or review procedures based on your plan and agreement.
Public pages explain the model. Customer-specific implementation details live in the signed-in portal and onboarding materials.