--- name: planning-additive-only description: sync.ps1 keeps planning/ additive-only (ARCHIVE-class is never deleted); a CLAUDE.md note recording this is still owed metadata: node_type: memory type: project originSessionId: c6b932fe-0f9f-4dfc-bfb2-5383747c2c84 modified: 2026-07-20T18:12:15.032Z --- `sync.ps1` treats `planning/` (ARCHIVE-class, per the main project's 3-class model) as **additive-only**: it copies without purging, so an audit/mockup/plan/slate the owner deletes from his working `planning/` folder is **retained forever** in the backup. `library/` and `memory/` stay mirrored. Each run writes `ARCHIVE_RETAINED.md` and prints how many archive artifacts were retained that are no longer present locally. This is documented in the backup repo's `sync.ps1` header and `README.md`. **Why:** the owner wants to clear `planning/` once a doc has served its purpose, without losing the record. **Recovery finding (2026-07-18):** the owner asked whether previously-deleted audits and mockups were recoverable. They are **NOT**. This backup's full git history contains exactly one deletion ever (a top-level `LOSS-AUDIT.md`), and the git history, working tree and snapshot ZIP all hold an identical `planning/` set. The deleted docs were removed locally before ever being synced here, so they exist nowhere in scope. The additive rule exists to stop that from recurring. **Still owed:** a note in `C:\Dev\!GEM\Website version\CLAUDE.md` recording that `planning/` is additive-only in the backup while `library/` is mirrored. It was not written on 2026-07-18 because that repo was mid-edit by another session; the owner said he would queue it. **Verify against CLAUDE.md before closing this** — as of 2026-07-20 it was confirmed still absent. Add it when that repo is idle. See [[backup-memory-topology]].