1 · Gather match data
A request starts by collecting available statistics, team context, weather and squad information. Competition coverage affects how much evidence is available. Seeing a collection stage does not confirm that a final lineup exists: the assessment uses information actually received.
2 · Read news and availability
Original news, press conferences and absence reports add context to the numbers. Sources are associated with the relevant team, competition and player, and their publication dates matter. An RSS headline helps discover an article; it does not replace checking the original source.
3 · Analyse, then review
Nexus Engine works on match context, tactical factors and the evidence needed for the analysis. Oracle Core reviews the scenario and probabilities before a conclusion is issued. These are real processing stages and may return to evidence gathering; the screen does not advance on a timer that invents progress.
4 · Save a report or explain the wait
When a valid report arrives, the interface reveals the forecast and makes it available in Vault. If a provider is delayed or evidence is insufficient, the app shows the request state instead of inventing a score. A next-attempt time is a scheduled check, not a promised delivery time or accuracy rating.
Forecast questions
Do more sources always make a forecast better?
No. Relevance, freshness and independence matter more than the count alone. Reposting the same story does not create multiple independent pieces of evidence.
Why can analysis pause?
It may be waiting for evidence, a provider response or the next retry. The app shows the current state and you can revisit the request in Vault.
Must I keep the analysis screen open?
You can leave the screen and return to your request in the app. Delivery depends on completed processing and sufficient evidence.
Probabilities based on available evidence, not guaranteed results.