From 15b8af64fca404f57555309f6c4c300bf55a74bb Mon Sep 17 00:00:00 2001
From: Abdessamad Derraz <3028866+Abdess@users.noreply.github.com>
Date: Fri, 7 Aug 2026 19:04:33 +0200
Subject: [PATCH] docs: name dump preservation catalogs in faq

---
 scripts/generate_readme.py | 6 ++++++
 wiki/faq.md                | 3 ++-
 2 files changed, 8 insertions(+), 1 deletion(-)

diff --git a/scripts/generate_readme.py b/scripts/generate_readme.py
index 4aae33ef..c8f4294d 100644
--- a/scripts/generate_readme.py
+++ b/scripts/generate_readme.py
@@ -342,6 +342,12 @@ def generate_readme(db: dict, platforms_dir: str) -> str:
             " source code, file by file where a profile exists; when the two"
             " disagree, the code wins.",
             "",
+            "Hashes document what emulator code loads and accepts, not dump"
+            " provenance; that boundary, and how it relates to preservation"
+            " catalogs such as No-Intro, is drawn in the"
+            f" [FAQ]({SITE_URL}wiki/faq/"
+            "#are-these-files-verified-against-original-hardware-dumps).",
+            "",
             "1. **Read emulator source code** - trace every file the code loads, its expected hash and size",
             "2. **Cross-reference with platforms** - match against what each platform declares",
             "3. **Build packs** - include baseline files plus what each platform's cores need",
diff --git a/wiki/faq.md b/wiki/faq.md
index e55e072a..4d54a47b 100644
--- a/wiki/faq.md
+++ b/wiki/faq.md
@@ -49,7 +49,8 @@ variant satisfying the most checks, logging any conflict it cannot
 resolve.
 
 Whether a file byte-matches the original hardware ROM is a different
-question, answered by dump-preservation catalogs, not by emulator code.
+question, answered by dump-preservation catalogs such as No-Intro,
+Redump, and TOSEC, not by emulator code.
 The two views usually agree; when they differ, this project follows the
 code, because that is what decides whether your emulator boots.