01
Implemented and server-tested
Release controls
Feature registry, dependency guards, circuit breakers, deterministic audits, and focused automated coverage form the current safety floor.
No blurred release claims
The QA roadmap.
Automated correctness is the foundation, not the finish line. Each stage names the evidence still needed before access expands.
Release sequence
Evidence before audience.
The canonical handbook currently defines 192 manual and client cases. Each observation is classified as Pass, Verified defect, Automation blocker, or Not tested, then separately evidence-reviewed.
02
Active evidence gap
Client walkthroughs
Observe Hall placement, menus, travel, encounter flow, Trust behavior, recovery, and visual presentation in the real FFXI client.
03
Live sampling pending
Balance and economy
Run multiple attempts across roles and gear bands, then review clear times, hit rates, pacing, rewards, prices, and realized returns.
04
Harness ready; physical runs pending
Reliability lab
Capture current-host baselines, database and queue faults, restart recovery, multi-client ramps, and one-hour memory and entity soaks.
05
Gated
Private remote Alpha
Invite a small no-cost tester group only after the client, recovery, privacy, backup, and operational evidence is reviewed.
06
Roadmap
Closed Beta and public launch
Expand in measured stages, keep held features inaccessible, publish known limits, and promote only the claims supported by evidence.
What blocks promotion
Green automation cannot see the client.
Live hit rates, pacing, positioning, menus, Trust decisions, rendering, recovery feel, and long-session behavior require direct observation. A tool failure is recorded as an automation blocker, never as a game defect.