Contribute and Correct

Status: PUBLIC CONTRIBUTION GUIDE · Evidence class: DERIVED POLICY · Last reviewed: 2026-08-11

Choose the smallest route that matches your evidence. Public discussion is welcome, but every claim stays scoped, sourced, and safe to reproduce.

Documentation correction

Identify the page, section, and exact sentence. Explain the proposed wording, cite the smallest public source, and say what remains uncertain. Use GitHub Discussions for a text-first correction; do not attach private captures.

Prior-art correction

Name the source family, revision/date, and the claim it supports or limits. Distinguish primary or near-primary documentation from emulator behavior and historical notes. The Prior Art and Sources index explains the expected provenance record.

Hardware replication

Start with Hardware Replication and Replication Wanted. Use the experiment runbook, report model and firmware/CFW, and share only public-safe scalar results through Submitting Results Safely. Never send a serial number, MAC address, account identity, save, key, retail input, or private capture.

Experiment proposal

Use the Planned Experiments registry to avoid duplicating a question. State the competing explanations, owned fixture, observables, safety boundary, and acceptance/rejection rules. A proposal is PLANNED until a valid run exists.

PSP homebrew or source-owned fixture

Contribute a tiny, redistributable program with clear source/license, build revision, expected hash, and a narrow purpose. Keep it deterministic and non-destructive. Do not include commercial assets, decrypted modules, private routes, or derived bytes from restricted content.

Nakagawa implementation contribution

Implementation changes belong in the public Nakagawa repository as a focused issue or pull request with a failing-before/passing-after synthetic regression. Separate production-dispatch evidence from helper, model, or source-shape tests. The current public main is the implementation reference; historical notes are not current authority without re-checking.

What every route should include

  • scope and evidence class;
  • exact public source, fixture, or experiment identifier;
  • what the evidence does not establish;
  • publication-safety and provenance notes;
  • the next smallest reviewable action.

Do not submit

Do not submit commercial ISOs/CSOs/PBPs, decrypted retail modules, generated retail-title C, proprietary textures/audio/video/fonts, private traces or framebuffer captures, keys, memory-card images, saves, absolute paths, or unique device identifiers. AI-assisted drafting does not create a contributor sign-off or DCO identity; human contributors must make required attestations themselves.

Disagreements are preserved as linked Contradictions rather than deleted. For a general orientation, visit Hardware Replication or the static-recompiler course.