How Can We Help?
How to Read a PSP Recompilation Claim
Claim status: PUBLIC METHOD · Evidence class: DERIVED · Last reviewed: 2026-08-11
A useful report makes the claim smaller than the headline. Ask what path ran, what input and environment were used, what was observed, and what remains untested.
Four questions
- What is the scope? Name the title, subsystem, source revision, model, firmware, or synthetic fixture.
- What is the evidence class? Distinguish implementation fact, hardware measurement, differential agreement, derivation, private acceptance, inference, hypothesis, and open work.
- What is the provenance? Link the public source or experiment record at the smallest useful granularity.
- What must not be inferred? A passing host route does not prove PSP hardware equivalence, and a missing capture is not a semantic pass.
Compact claim record
| Field | Example |
|---|---|
| Status | PUBLIC METHOD |
| Evidence | DERIVED from named implementation and experiment premises |
| Open follow-up | Qualified hardware probe or independent synthetic reproduction |
Public-safety note: the example uses no commercial game input, private capture, key, save, path, or derived retail bytes.
Use the site Evidence Standard and Start Here pages for the full method.