Start Here
ORIENTATION · EVIDENCE MODEL · PUBLIC BOUNDARY
Read the method before the case study.
This site is an evidence-led map of PSP recompilation and binary-translation research. Start here to understand what each kind of claim can—and cannot—establish.
Choose a route
🧪 Replicate hardware
Run a bounded public experiment or find the next high-value replication target.
🛠️ Learn the pipeline
Follow a teaching path from guest contracts and safe parsing to implementation anchors.
🤝 Contribute
Send a source correction, replication result, experiment proposal, or public-safe implementation change.
Recommended reading order
- Evidence Standard — how observations, implementations, and hypotheses are labelled.
- Static Recompilation Architecture — the public pipeline from executable input to a native runtime.
- PSP Executable Model — PRX/ELF, imports, relocations, NIDs, and function ownership.
- Hardware Oracle Methodology — what a qualified PSP measurement must preserve.
- Nakagawa Recomp Case Study — one public implementation, with project-specific scope kept explicit.
Evidence labels at a glance
Measured
- HARDWARE MEASURED
A qualified PSP observation with a reproducible probe record. - DIFFERENTIAL
Agreement or divergence between named models or implementations.
Implemented
- IMPLEMENTATION FACT
Behavior visible in a named public source revision. - PRIVATE ACCEPTANCE
Restricted local evidence that is summarized, not reproduced here.
Reasoned
- DERIVED
A reasoned result that depends on stated premises. - INFERENCE / HYPOTHESIS / OPEN
Useful reasoning that is not yet a measured fact.
Public boundary
Public pages may link to source repositories and published specifications. They do not publish commercial ISOs, decrypted PRXs, generated retail code, keys, private traces, private filesystem paths, save data, or derived bytes from restricted inputs.
Scope note: this index is a living research map. Each page carries its own status and review date.