01
Integration in progress
Release controls
Reconcile exact component identities and validate security, release, migration and recovery controls for the combined candidate.
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.
kxi-owner-alpha-20260913-04 · 2026-09-13 · local-development · DRAFT
Readiness: NOT READY. Full agreed scope: INCOMPLETE.
Website access hardening is deployed. The Player launcher passed Windows and Linux validation and a local startup check. Game-server deployment, complete support testing and gameplay acceptance remain open.
Website: 30 local build/render checks, 9 hardening checks, 30 hosted negative checks, and owner/logout observations. Launcher: Windows and Linux CI, 58 texture cases, 17 package file hashes, managed-asset signature verification, malware scan and actual local UI startup. Discord: 86 Worker, 2 migration, 1 operator and 5 tooling cases on the reviewed source; a separate native D1 restore rehearsal passed. Game-server certification and full live support/client acceptance remain pending.
02
Client acceptance pending
Client walkthroughs
Observe setup, login, world entry, Hall menus, travel, encounters, Trust behavior and recovery in the actual FFXI client.
03
Gameplay sampling pending
Balance and economy
Review roles, gear bands, pacing, rewards, crafting costs and long-term progression using recorded gameplay evidence.
04
Host and recovery acceptance pending
Reliability lab
Validate backup restoration, persistence, interruption recovery, multiple clients and monitored stability on the intended candidate.
05
Owner approval required
Private remote Alpha
Invite testers only after the required client, recovery, privacy and operational gates pass and the owner approves access.
06
Future access gate
Closed Beta and public launch
Expand access only after the agreed release requirements pass and the owner approves the release. Held features retain their prerequisites.
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.