Backlog triage Part B: 125 finished rows + 20 id-less rows moved to CLOSED-ITEMS (full text at 9e2786c); open rows normalised to one 6-column shape; narratives archived verbatim; closed_register_gate RULE 3 refuses a finished row in OPEN-ITEMS (decoys, seen red); rules rehomed to CONTEXT + 07 §11; loose notes triaged; R-814..R-819 filed; register 444 -> 325

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS

documentation/architecture/07-backup-architecture.md

@@ -1381,6 +1381,20 @@ to now *implement* D5 remains an open scheduling decision, not a blocked one.
 
 ---
 
+**Decided, and deliberately not built — carried here 2026-10-03 when their register rows moved to
+`backlog/CLOSED-ITEMS.md`** (the reasoning is in `CONTEXT.md`, "Rules carried out of rows closed 2026-10-03"):
+
+- **[DESIGN] No automatic abandon on a date (R-245, decided 2026-08-07).** A customer who never decides is not
+  auto-abandoned after 30 days. An automatic ending, if ever built, triggers on the HARM (quota — old history
+  blocking new backups), with a dated warning, never on a date alone. Reopens on quota.
+- **[DESIGN] `markOrphaned` keeps no guard against an active abandon countdown (R-303, decided 2026-08-13).** The
+  co-render is made harmless, not impossible; suppressing the orphan card during a countdown would hide a real
+  second fault. Reopens on a real-world sighting.
+- **[DESIGN] No in-product route from the recovery screen to a set-aside store (R-312, decided 2026-08-13).**
+  Retention is an operator-only capability, and nothing anywhere may promise the customer can perform it
+  themselves. Re-evaluate on a real customer request. Its fixture, `demo-felhom`'s unrecoverable set-aside store
+  (R-313), is kept until R-312 ships or is abandoned.
+
 ## 12. Evidence index
 
 | Claim | Grade | Source |