Expected
The terminal state the workflow was attempting to establish.
VRA EVIDENCE
What happened.
Not just what was clicked.
VRA Evidence is the customer-facing record behind an execution result: the intended state, the observed state, the action, the classification, the retry decision and the reason automation stopped.
THE EVIDENCE RECORD
Six questions.
One inspectable answer.
The exact presentation can change before release. The principle does not: a success label alone is not sufficient evidence.
Observed
The customer-visible state VRA could actually classify.
Action and outcome
What was attempted and how the result was classified.
Time
When the step started, settled and reached its final outcome.
Retry history
Whether recovery happened, why repetition was allowed and where it stopped.
Capture
A relevant screenshot when visual inspection helps explain uncertainty or failure.
FOLLOW THE OUTCOMES
A routine can finish
without pretending everything succeeded.
This sanitised demonstration uses real VRA outcome types. It is not a live feed, sampled reliability data or a claim about current fleet performance.
REPRESENTATIVE RUN REPLAYSanitised demonstration · not reliability telemetry
- Starting FARM-07Assigned Daily Farm routine loaded
- Viking Rise recognisedCity state ready for configured work
- Mail Rewards3 available · claim verified
- ResearchQueue already occupied · no action needed
- Heal TroopsInfirmary empty · skipped correctly
- Gather ResourcesDeparture could not be verified · repeat blocked
- Routine complete3 resolved · 1 operator-attention outcome
0 / 7 events
OUTCOME LANGUAGE
Every action gets
the result it earned.
Completed, no action needed, unavailable and uncertain are operationally different. Evidence keeps those differences visible.
Completed
The intended state change was verified.
No action needed
The requested state was already satisfied.
Unavailable
A game condition or prerequisite blocked the action.
Skipped
Configuration intentionally excluded the operation.
Failed
Automation could not complete safely.
Needs attention
The outcome is uncertain; automatic repetition is blocked.
WHY DIDN’T IT RETRY?
Because uncertainty is not permission.
If a march might have departed, a reward might have been consumed or resources might have been spent, blind repetition can create a second unintended action. VRA blocks automatic repetition when the previous side effect cannot be reconciled safely.
SEE THE CUSTOMER SURFACE
Evidence belongs in the Command Centre.
Tour the real development interface and the operational views that connect farms, activity, outcomes and attention.