# Rules versus responses — The Steam Dossier

Canonical: https://phishdestroy.io/steam_dossier/steam_enforcement_evidence
Language: en
Attribution: PhishDestroy Team
Reading edition: 18 October 2026.

Evidence supplement / source-linked records 

## Steam Enforcement Evidence — Support Records & Developer Network

The rule. *The response.*

 

WHAT THIS SECTION PROVES  

This evidence room places Valve's Subscriber Agreement beside public accounts of support and enforcement outcomes, plus retained network data covering 252 repositories and 3,320 GitHub profiles. It lets readers compare stated rules with what the cited sources report. These are not authenticated internal enforcement logs, and the collection does not establish uninterrupted bot activity, Valve's knowledge of individual operators or the absence of an appeal in every case.

 

**18 October 2026 · scope clarification.**  Public user accounts and repository records are distinguished here from internal enforcement evidence. The earlier overview stated broader conclusions than this collection could establish on its own.

  [← Back to Executive briefing](https://phishdestroy.io/steam_dossier/index.html#briefing-heading)

 

Read the written restriction. Open the recorded response. Compare what the source shows with what remains unanswered.

[Support & appeals ↓](https://phishdestroy.io/steam_dossier/steam_enforcement_evidence)  [Public infrastructure ↓](https://phishdestroy.io/steam_dossier/steam_enforcement_evidence)

 

**252**  repository records

**3,320**  public profiles

**4,214**  distinct profile–repository pairs

**98,902**  profile pairs with shared repos

 

01 / Support, sanctions & restoration 

## Read the complaint. Keep the source attached.

[Support replies & source register (9,051 rows) ↗](https://phishdestroy.io/steam_dossier/support_canned_refusals)  [Download selected records ↓](https://phishdestroy.io/steam_dossier/steam_tos_assets/selected-support-records.json)

 

[HFB / THE OUTSOURCING CASE **The acknowledged compromise. The reported dismissals.** Follow the reproduced support response and the source of the claim about contractor staff. **Open the case and its sources →**](https://phishdestroy.io/steam_dossier/investigation_part2#outsourcing-case)

 

Below: five preserved **public Reddit posts**  from the supplied support collection. Each record documents a reported interaction with Valve's support system — preserved with its original source link, capture position and complete text. These are victim accounts. The authenticated support logs that would confirm or contradict them are held by Valve and have not been disclosed.

 

02 / Steam development network 

## Public infrastructure. Recorded at scale.

 [Download all 252 records ↓](https://phishdestroy.io/steam_dossier/steam_tos_assets/network-repositories.csv)

The supplied `output_steam_network` snapshot records repositories, public contributor/fork relationships and profile overlaps. These are published records — what was built, who contributed, what was forked. The paper trail of public capabilities is what Valve must account for.

252 records

| Repository / description | Contributors | Forkers | Recorded profiles |
| --- | --- | --- | --- |

Page 1

Snapshot: 17 September 2026, 11:19:11 as written in the source; timezone unspecified. Relationship collection is capped in the export (many categories stop at 40). Contributors and forkers sum to 4,554 role entries across 4,214 distinct profile–repository pairs; a profile can have both roles. Zero means no records captured in that category. Repository names may include aliases or case variants; totals retain the source’s counting conventions.

 

Source provenance 

## Built from retained source files.

Support testimony

2323/reddit_scams_ultra/steam_support_tickets_MEGA.json · rows 45, 58, 107, 110, 294

Network snapshot

[network-repositories.csv](https://phishdestroy.io/steam_dossier/steam_tos_assets/network-repositories.csv)  ·  [raw_data.json](https://phishdestroy.io/steam_dossier/output_steam_network/raw_data.json)  · overlaps.csv · summary.txt (historical source paths retained in manifest)

The manifest records source paths, byte sizes, SHA-256 hashes and selected record positions. Raw captures remain separate from the investigation’s interpretation.

 [Download source manifest ↓](https://phishdestroy.io/steam_dossier/steam_tos_assets/enforcement-source-manifest.json)