Release evidence

Release evidence

Elah treats a release claim as incomplete until a test can fail when the claim is false.

Required repository gates

The protected main branch requires checks for:

• Rust formatting, linting, and tests;
• Java formatting, compilation, and tests;
• Node linting and tests;
• Protocol Buffer linting, building, and compatibility;
• generated output reproducibility;
• isolated upstream research boundaries;
• public provenance policy;
• Apache notices and REUSE coverage;
• dependency review;
• software bill of materials generation;
• CodeQL for Rust, Java or Kotlin, and JavaScript or TypeScript;
• Protocol Laboratory;
• Observer Laboratory.

Observer Laboratory

The 0.0.3 hosted fixture contains 17 occupied chunks across four region files and two dimensions.

The gate requires:

• independent Prismarine fixture creation and rereading;
• agreement between fixture truth and standard report;
• agreement between fixture truth and deep report;
• agreement between standard and deep structural totals;
• identical complete SHA-256 inventories before and after both scans;
• changed-world exit code 5;
• zero success-report bytes after a detected change.

Protocol Laboratory

The 0.0.2 gate force-kills and reconnects the dummy worker 25 times, then proves the retired first session cannot send another accepted heartbeat.

What evidence does not prove

Current gates do not prove Minecraft gameplay, plugin compatibility, multi-machine ownership, seamless player handoff, persistent storage, automatic failover, or performance at player scale.

Those claims require later milestone-specific laboratories.