S17 · Balance, longitudinal validation and security

Current implementation: 599 tests, 110 browser checks, eight launcher checks and a quick actual-engine laboratory provide recorded component evidence.

Outstanding acceptance: Human longitudinal cohorts, all career/class viability and a full release abuse/security review remain open.

The four requirements below preserve the original release target. Their historic baseline is not used as a current completion score. This page does not mark the entire stream complete merely because related components are installed.

Reference

Requirement	Required deliverable	Acceptance standard
S17.01 · Test complete content and system interactions	Add property, replay, migration, adversarial and integration coverage for every released family and its cross-system consequences.	All content is reachable under allowed conditions; malformed effects and economic loops fail safely; test coverage has declared limits.
S17.02 · Evaluate class and career viability	Test offense, defense, support, hybrids, solo routes and all professions across progression and market conditions.	Evidence examines cost, attention, reliability and usefulness rather than only damage or a scripted fixed-price profit model.
S17.03 · Run persistent player and population cohorts	Observe real play through early, middle, late and post-clear content, alongside server bootstrap, scarcity, cartel and abandonment scenarios.	No developer grants, accelerated timers or solved-route scripts stand in for the normal journey; assumed hours are revised against actual experience.
S17.04 · Conduct release security and abuse review	Test duplicate rewards, authority confusion, alt incentives, scams, sabotage, private-story access, agent injection and economic exploit containment.	Confirmed critical failures are resolved; appeals and recovery are possible; one account per person is not claimed from weak identity signals.