From 1be50e056fc9cbb9651b19fbaf2d8c0b7c21515a Mon Sep 17 00:00:00 2001
From: Abdessamad Derraz <3028866+Abdess@users.noreply.github.com>
Date: Sun, 4 Oct 2026 17:49:16 +0200
Subject: [PATCH] docs: state what separates two platform packs

---
 wiki/architecture.md | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/wiki/architecture.md b/wiki/architecture.md
index 41c8a7b5..0f1abbed 100644
--- a/wiki/architecture.md
+++ b/wiki/architecture.md
@@ -147,9 +147,11 @@ entries that are out of scope here.
 ## Pack grouping
 
 Platforms that produce identical packs are grouped automatically.
-RetroArch and Lakka share the same files and `base_destination` (`system/`),
-so they produce one combined pack (`RetroArch_Lakka_BIOS_Pack.zip`).
-RetroPie uses `BIOS/` as base path, so it gets a separate pack.
+Two platforms share a pack when they declare the same files and run the same
+emulators. RetroArch and Lakka do, so they produce one combined pack
+(`RetroArch_Lakka_BIOS_Pack.zip`). RetroPie inherits RetroArch's systems but
+ships its own package list, standalone emulators included, so it gets a
+separate pack and a separate install manifest.
 With `--target`, the fingerprint includes target cores so platforms
 with different hardware filters get separate packs. Emulator and system packs
 also retain system identity, `variant_group` and requested region; same-named