This board shows the durable foundation, the work still under validation, the limitations we will not hide and the features deliberately outside the current active catalogue.
Built foundations
5
23-action active automation catalogue with explicit action contracts
Observe → Act → Verify → Report outcome model
Bounded retries, reconciliation and per-farm isolation
Customer Command Centre, Environment Health and support bundle
Auditable GnBots configuration preview, backup, dry run and import
Validating now
4
Per-workflow operator acceptance after the latest reset
Customer-like Windows installation and sustained multi-farm performance
Versioned beta telemetry with representative farms and inclusion rules
Current-game variants for actions that require naturally available rewards, wounds, queues or targets
Known limitations
5
No anti-ban or zero-failure promise
Unsigned beta distribution remains a Windows trust limitation
Game updates can invalidate previously recognised screens
A configured workflow can still be unavailable on a particular farm
Public reliability numbers are gated because current internal evidence is not representative beta telemetry
Deferred or planned
5
Recall Troops is not in the current active catalogue
Divination Shack is not in the current active catalogue
Beast Pen is not in the current active catalogue
Public customer telemetry and status feeds wait for consented beta data
Final download, pricing and activation details remain unpublished
Why no per-workflow percentages here? The current evidence is development/operator validation over a short period and too few distinct farms. It does not pass the Reliability Lab publication gate. Publishing it as beta reliability would be misleading.
FOLLOW THE ENGINEERING
Every checkpoint keeps its caveat.
Read the dated build log or inspect the public measurement method before trusting a headline statistic.