GENERATED VIEW · PRIVATE ARCHIVE · DO NOT SERVE
RobCo Industries · Archive Museum

folder_and_repo_naming.md



MEMORY

memory/project-C--Dev--RobCo--RobCo-UOS/folder_and_repo_naming.md

sha256 87f8737a2772cf68 · 2600 bytes · original held in the private archive

--- name: folder-and-repo-naming description: "The app repo is NEVER renamed (PWA install origin); _RobCo-Archive (private, permanently) vs _RobCo-Exhibit (public) must never converge — safety-critical" metadata: node_type: memory type: project originSessionId: 6768475a-1793-4f0b-8611-49831756197e modified: 2026-07-20T20:20:48.380Z --- Folders were renamed 2026-07-20 and the sweep landed: `C:\Dev\!GEM\` → `C:\Dev\!RobCo\`, `Website version\` → `!RobCo-UOS\`, `_robco-local-backup\` → `_RobCo-Archive\`. Two naming rules outlive that operation and must never be "tidied" by a later consistency sweep. **1 — The app repo `zerckzzyHD/Robco-UOS` is NEVER renamed. Closed 2026-07-20, do not re-propose.** Its GitHub Pages URL is the origin 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 reinstalling. 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: *"the site can have a lowercase C whatever."* ⚠ A sweep WILL notice the mismatch between the folder `!RobCo-UOS` and the repo `Robco-UOS` (including the lowercase "c") and want to fix it. **That mismatch is deliberate. Leave it.** **2 — `_RobCo-Archive` and `_RobCo-Exhibit` must NEVER converge.** The owner first proposed naming the private backup `_RobCo-Exhibit`; Dispatch pushed back and he agreed to `_RobCo-Archive`. - **`_RobCo-Archive` — PRIVATE, PERMANENTLY.** Repo `zerckzzyHD/_RobCo-Archive` (note the LEADING UNDERSCORE, matching the folder). 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. See [[backup-archive-repo]]. - **`_RobCo-Exhibit` — PUBLIC.** A *fresh* repo with clean history containing ONLY generated museum output. Served via **Cloudflare Pages, its own origin** — 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 names matter:** 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.
STAMP · generated for RELEASE v2.8.5 commit 06e5180 (06e51801b38a) · archive input-tree hash c07fbfbdd2e1ddeb · 754 files · no wall-clock timestamp (regenerates identically when nothing changed).