Revocations & superseded builds

A public record of artifacts we have revoked or replaced, with the honest recorded reason, the date, and the newer build where one exists.

We want to be honest about one limit of BitTorrent: swarms are decentralized. When we revoke an artifact we stop listing it and stop serving its .torrent / magnet and manifest from our infrastructure, but we cannot remove data that is already held by third-party peers we do not control.

Revoked

Artifacts we pulled because they were broken, wrong, or otherwise should not be distributed.

Unlisted artifact

Revoked Jul 9, 2026

Reason: Pre-launch cleanup (WP-9.8, Pat-approved 2026-07-09): legacy Phase-3/6 test torrent, manifest signature invalid, never gate-passed catalog surface

Unlisted artifact

Revoked Jul 9, 2026

Reason: Pre-launch cleanup (WP-9.8, Pat-approved 2026-07-09): legacy Phase-3/6 test torrent, manifest signature invalid, never gate-passed catalog surface

Unlisted artifact

Revoked Jul 9, 2026

Reason: Pre-launch cleanup (WP-9.8, Pat-approved 2026-07-09): legacy Phase-3/6 test torrent, manifest signature invalid, never gate-passed catalog surface

Unlisted artifact

Revoked Jul 9, 2026

Reason: Pre-launch cleanup (WP-9.8, Pat-approved 2026-07-09): legacy Phase-3/6 test torrent, manifest signature invalid, never gate-passed catalog surface

Superseded

Older builds that a newer revision has replaced. These keep seeding and stay reachable while people pull off them — they are simply no longer the current build.

No artifacts have been superseded.

This page states provable, recorded facts about our own distribution decisions. It is not a claim about the safety or legality of any third party's copy.