Eve library

Phase 164 local completion evidence

Tracker

Revision 1

On this page

Historical task source. The Eve task board holds current task state.

Phase 164 is locally complete. The two formerly open validation items now have executable, fail-loud coverage in @neith/liveops-conformance; the earlier assumption that both required wholly external infrastructure was incorrect because all three named game packages are present in this repository and a million-client concurrency model can be exercised safely with bounded workers.

Requirement-to-evidence matrix#

Task Authoritative local evidence Pass condition
164.13.8 load_test::run(ONE_MILLION_CLIENTS) materialises 1,000,000 live connection states before a barrier releases bounded worker shards. Every client performs a deterministic remote-config evaluation and emits a validated analytics heartbeat through the sibling crates' public APIs. Peak connections are exactly 1,000,000; all 2,000,000 requests complete; request failures are zero. The ordinary crate test runs the full one-million-client population rather than a reduced CI sample.
164.13.10 dogfood::run() binds Phase 27 to libs/yemaya/project-obsidian/src/game-design.ts, Phase 76 to libs/maya/forge-core/src/lib.rs, and Phase 77 to libs/maya/games/src/mmo/index.ts. Each game profile executes attribution, compliance, remote config, experiment assignment, analytics, ads, IAP, economy, cloud save, CRM, customer support, and portal reporting through the twelve sibling crates' public APIs. Both the real package/project marker and integration anchor must exist for every game; every profile must complete all twelve ordered subsystem steps; the conformance report must contain six passing binding/journey checks.

The load harness deliberately models connection concurrency independently from OS thread count. One thread per client would test thread-scheduler exhaustion, not the liveops SDKs. All connection states coexist, their request window is barrier-synchronised, and CPU work is sharded across at most sixteen workers. A deployed multi-region network soak remains an environment release exercise, not an open locally actionable Phase 164 implementation task.

Verification commands#

Run from the repository root:

bash
cargo fmt --manifest-path libs/neith/liveops-conformance/Cargo.toml -- --check
cargo clippy --manifest-path libs/neith/liveops-conformance/Cargo.toml --all-targets -- -D warnings
cargo test --manifest-path libs/neith/liveops-conformance/Cargo.toml
cargo build --release --manifest-path libs/neith/liveops-conformance/Cargo.toml

The crate's full_suite_passes test also executes all ten Phase 164.13 conformance reports together, including the full million-client and three-game dogfood gates.