Platform coverage
Platform coverage requires a native artifact and verification evidence for every target. A successful build on one machine, launch under emulation, or website download button does not prove delivery for another platform.
Current target matrix
| Target | Delivery and primary checks |
|---|---|
| macOS arm64 | DMG, signature, installation, first launch, and update |
| macOS x64 | Separate x64 DMG, signature, and Intel-machine verification |
| Windows x64 | Installer, install and uninstall, first launch, and service behavior |
| Linux x86_64 GNU | Native x86_64-unknown-linux-gnu artifact and startup check |
| Linux arm64 GNU | Native aarch64-unknown-linux-gnu artifact and startup check |
Verify on every platform
- Filename, platform, architecture, channel, and version fields agree.
- Final downloaded bytes pass size, SHA-256, and signature checks.
- The installed or unpacked application starts with the expected data and identity homes.
- Updates do not mix another architecture or stale channel manifest.
- Failure can be uninstalled, rolled back, or restored to the last verified version.
Evidence record
Record operating-system version, real hardware or runtime, download URL, artifact digest, startup result, and known limitations. Results under Rosetta, a compatibility layer, or a container must be labeled and do not replace the corresponding native target.
Missing targets
If a platform has no artifact or has not been verified, mark it unavailable or failed in the manifest and release notes instead of copying another platform's success. Block complete channel promotion when a required target is missing.
Related pages
EvoX Docs · Administration · Release management