# Legacy Artifact Quarantine

The files listed in `legacy-artifact-registry.json` are immutable historical,
experimental, failed-run, or visual-review artifacts. They are retained so old
results can be audited and regressions can be reproduced. They are not current
verified proof and cannot support a current savings, quality, production,
security, or rank claim.

The registry binds every listed file to its SHA-256 byte hash. Its policy applies
to every entry:

- `current_verified_proof` is `false`;
- promotion is prohibited;
- raw bytes must not be rewritten;
- JSON field names do not establish attribution or verification;
- JSONL rows are raw run material, not a reviewed proof bundle; and
- screenshots are historical visual-review records, not machine-verifiable
  evidence of current behavior or claims.

The old partial live run mixed benchmark arms and did not include the
receipt-reconciled CostLayers attribution required by the current proof
contract. Its historical meter field is excluded. The failed full-run attempt
contains no accepted invoice-counter rows. The agent-loop files are
experimental raw runs. None can be promoted by renaming, copying,
screenshotting, or adding new marketing text around the old bytes.

Promotion requires a newly generated artifact under the current proof contract,
with quality evidence, receipt-reconciled attribution, a new hash-bound
descriptor, and explicit review. Verify the quarantine registry and all bound
hashes with:

```sh
node benchmarks/world-best/claim-consistency-smoke.js
```