--- name: folder-and-repo-naming description: "⛔ The app repo is NEVER renamed (installed PWAs are bound to its Pages origin) — the folder/repo mismatch is deliberate. ⚠⚠ SAFETY-CRITICAL: _RobCo-Archive (private, permanently) and _RobCo-Exhibit (public) must never converge." metadata: node_type: project type: project --- Supersedes the completed `folder-rename-plan` memory. The 2026-07-20 renames LANDED and were swept: `C:\Dev\!GEM\` → `C:\Dev\!RobCo\`, `Website version\` → `!RobCo-UOS\`, `_robco-local-backup\` → `_RobCo-Archive\`; repo `robco-uos-local-archive` → `zerckzzyHD/_RobCo-Archive`. These two rules outlive that operation. ## ⛔ THE APP REPO IS NOT RENAMED — CLOSED 2026-07-20, DO NOT RE-PROPOSE Renaming `zerckzzyHD/Robco-UOS` would change the **GitHub Pages URL**, which is the address the owner's and his brother's **installed PWAs are bound to**. GitHub leaves an HTTP redirect, but a redirect does not help an installed app whose service-worker scope was registered against the old path: broken install scope, SW scope mismatch, both users needing to reinstall. Saves are keyed to the ORIGIN rather than the path so data should survive — but the brother is the one user who would notice if it didn't. All of that to correct one letter's capitalisation. Owner: *"scrap the 3rd one, we won't rename it at all. the site can have a lowercase C whatever."* ⚠ A future session doing a consistency sweep WILL notice the mismatch between `!RobCo-UOS` (folder) and `Robco-UOS` (repo), including the lowercase "c", and want to "fix" it. **That inconsistency is deliberate. Leave it.** ## ⚠⚠ ARCHIVE vs EXHIBIT — DO NOT LET THESE NAMES CONVERGE The owner initially proposed renaming the private backup `_RobCo-Exhibit`. Dispatch pushed back and he agreed to `_RobCo-Archive`. Keep it that way, and keep the reasoning attached: - **`_RobCo-Archive` — PRIVATE, PERMANENTLY.** Repo `zerckzzyHD/_RobCo-Archive` (note the LEADING UNDERSCORE, matching the folder — a sweep that assumed `RobCo-Archive` without it 404'd the remote; verify names with `gh repo list`, not from prose). Holds `library/`, `planning/`, the orchestrator memory, and the museum generator. **It can NEVER be made public**: its git history contains the owner's email, and deleting files does not remove them from history. - **`_RobCo-Exhibit` — PUBLIC.** A *fresh* repo, clean history, containing ONLY generated museum output. Served via **Cloudflare Pages — its own origin**, because GitHub Pages would share an origin with the live app and the archive's executable prototypes could then reach the app's `localStorage`. Did not exist as of 2026-07-20. **Why the naming matters:** if both are called "Exhibit", a session — or the owner at 1am — pushes the wrong one. That is the single irreversible mistake in this whole system. The names must say what the things ARE. ## STILL-PENDING decisions carried over from the rename plan (not done as of 2026-07-20) - **Prompt library moves** `planning/_standing/PROMPT_LIBRARY/` → `library/`. ⚠ Consequence: `planning/` is ADDITIVE-ONLY in the backup (nothing is ever removed); `library/` MIRRORS (deletions propagate). The move trades "can never be lost" for "deleting locally removes it from the backup working tree" — still in git history, but a weaker guarantee. - **Once the museum is complete**, the old audits and mockups get deleted from the app repo's local `planning/` and live only in the archive — exactly what the additive-only rule was built for. They're gitignored in the app repo anyway, so it's a local tidy; the archive keeps them permanently. Related: [[robco-uos-project]], [[parked-phone-archive-access]].