SpaceRot: broken Hugging Face Spaces, and Beam's verified repairs

Data and code behind Space Doctor (code on GitHub). Every number on that page is computed from the files here.

What's inside

File	What it is
census.json	The 10,000 most-liked Spaces on 2026-10-30: id, likes, SDK, hardware, runtime stage, Hugging Face's public error message, last modified
triage.json	Beam's root-cause families for every broken Space (two calls), each with its regex and the coverage we measured by running it. assignment maps each Space to a family
triage_r1.json	The first triage pass alone
summary.json	All headline numbers
cases/<owner>__<space>/repro.json	Our rebuild of the untouched Space: stage, exception, log tail, resolved pip freeze, and whether it matches HF's exception
cases/<owner>__<space>/case.json	Every Beam attempt: reasoning effort, the raw answer, its reasoning trace, diagnosis, tool turns (need_files, apply/lock errors), diff, lockfile, rebuild stage, probe calls and outputs, token usage
cases/<owner>__<space>/patch.diff	The verified patch, for revived Spaces
cases/<owner>__<space>/baseline.json	The no-LLM time-travel baseline on the same Space
code/reviews.json	The human review of every revival: approved, unverified (boots, output does not show the app working) or rejected (the patch gamed the verifier), each with its reason
code/prs.json	The pull requests opened on the original Spaces
code/	The full pipeline

The Spaces' own code is not redistributed; diffs reference it by path.

As a benchmark or RL environment

Each still-broken Space is a task with a verifiable reward:

• Input: the Space id (fetch the repo at the current revision), Hugging Face's error log, our rebuild log, and the resolved package versions.
• Action: a patch to the repo, or the verdict "unfixable".
• Reward: code/sandbox.py rebuilds the patched Space with the Spaces recipe and code/probe.py calls its main endpoint. Reward 1 only if it returns a non-empty result. Six patches in this run passed that check and were still rejected by a person (code/reviews.json): use them as negative examples of reward hacking. doctor.integrity rejects patches that delete code or swallow errors, so gutting the app is not a shortcut.
• Abstention: the "unfixable" cases (gated models, owner-only secrets, dead download links) are labelled with Beam's reasons, which we checked by hand. They make a calibration test: a policy should abstain on these, not hack them.

Caveat: Spaces change. A Space can be fixed by its owner, or rot further, after 2026-10-30. Re-run reproduce.py before using a case.

Reproducing

python code/harvest.py 10000 census.json           # census (Hub API)
python code/triage.py census.json triage.json      # 1 Beam call
python code/triage_refine.py census.json triage.json
python code/reproduce.py 220 6                      # needs Docker + buildx
python code/doctor.py                               # Beam repair loop, needs REFLECTION_API_KEY
python code/baseline.py                             # time-travel baseline
python code/report.py .

Model: reflection/Beam-1.0-501B-A23B via Reflection's API.