DEVELOPMENT EVIDENCE
Real actions. Inspectable records.
Controlled action runs, reviewed screenshots and recognition tests show what has been checked. Follow the observed state, the chosen action and the captured result.
VRA EVIDENCE
Know what happened.
Know what needs you.
When a farm needs attention, you should not have to guess why. VRA connects the attempted action to its observed result, available captures and the reason it stopped—so you can decide what to do next.
FROM ACTION TO OUTCOME
See the checks behind the work.
VRA connects the workflow to the result it expects: an active healing queue, a claimed reward or a gathering squad setting off.
Read the testing method →THE EVIDENCE RECORD
Six questions.
One inspectable answer.
Follow the work from its starting state to its recorded outcome, with the context you need to review it.
Expected
The terminal state the workflow was attempting to establish.
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 that lets you inspect the game state behind the result.
FOLLOW THE OUTCOMES
From starting state
to a verified result.
Follow a completed healing workflow through the observed state, normal timed healing, tribe assistance and return to the city. The replay includes an original evidence crop.
DEVELOPMENT EVIDENCE REPLAYVerified healing · recorded development evidence
Initial observed state
The Infirmary showed wounded troops and an eligible timed Heal control after ready city output was collected.
1 / 6
Completed21 September 2026
Read the complete text record
- Initial observed state
- The Infirmary showed wounded troops and an eligible timed Heal control after ready city output was collected.
- Teacher / workflow decision
- Use the deterministic healing workflow. Preserve existing work and exclude instant healing or premium spending.
- Action attempted
- Start normal timed healing, then request available tribe assistance.
- Expected result
- A new active healing queue, followed by an assistance acknowledgement and return to the city.
- Observed result
- Saved frames show the timed queue and the explicit assistance confirmation. The final frame is the city.
- Retry or stop decision
- No repeat Heal was needed after the active queue was verified.
Step through the recorded observations and original screenshot crop. This text replay follows a real development action; the Product Tour also includes a recorded training run.
OUTCOME LANGUAGE
Every action gets
the result it earned.
See when work completed, when an existing queue should be preserved and when a farm needs your review.
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.
Needs attention
The recorded state is ready for your review before work continues.
CONTROLLED RECOVERY
Keep the next move in your hands.
VRA checks the existing state before repeating a spend, claim or dispatch. When the result needs review, it keeps the relevant evidence together so you can make the next decision.
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.
THE DECISION BEHIND A RESULT
An interaction is an attempt.
The next state decides the outcome.
This is the verification model—not a simulated live run. Spending permissions, supported controls and recovery limits remain the boundary throughout.
- 01
Observe game state
Identify the current screen, eligibility and any work already running.
- 02
Choose a permitted action
Apply the farm’s settings and resource/spending limits.
- 03
Execute the interaction
Perform the eligible interaction; do not call the click a success.
- 04
Observe the resulting state
Compare the new state with the workflow’s declared result.
Is the outcome clear?
Record the verified result
Record completed work or a valid no-action state, with the observation that supports it. A timer starting can be the immediate result; its later completion is different.
Capture evidence and stop for attention
Retain the relevant capture and reason. Do not replay a possible spend, claim or dispatch just to obtain a more flattering status.
Review the evidence → make an authorised correction or seek support → validate the next run. Product/model improvements require their own review; a failed old record is not rewritten as successful.
REAL HISTORICAL EXCEPTION · 21 September 2026
Animal visible.
Collection not established.
- Observed
- The camera reached a moving animal during a city errand. The retained post-input capture still showed the animal, but did not establish collection.
- Expected
- An identifiable collection state following the attempted interaction.
- Recorded decision
- The recorded step failed reconciliation. The retry decision was stop for inspection, with automatic replay disallowed.
This is one historical development failure, not a current failure rate. Later changes do not turn that recorded run into a success. The crop alone is not the full log.
Read the current City Event Reports boundaries →
SEE THE OBSERVATION AND RESULT
Watch the work, not just the promise.
Inspect the real paired training recording and the evidence behind a verified result. One demonstration is not a fleet-wide reliability benchmark.