# Preserved Claude Code transcripts **What this is.** A verified copy of every `*.jsonl` session transcript that existed in `~/.claude/projects/-Users-davidglidden/` on 2026-08-19, taken out of that directory because the harness prunes it on a 30-day retention policy. **Why it exists — PENDING-147 leg (i), steward-authorized 2026-08-19.** Two governance instruments were counting files in that pruned directory as if the count were cumulative: - `REVIEWED-95` (2026-08-07) pre-registered a 20-session falsifier for the verification-ladder retrieval trial, graded automatically when the count reaches 84. - `REVIEWED-123` cond. 2 (2026-08-17) obliges an N-now report at every wake. The count is a **30-day rolling window**, not a cumulative count: it read 60 on 08-17, 61 on 08-18 and **47 on 08-19**. So the trigger is very likely unsatisfiable at the observed ~1 session/day, and the trial's own evidence was being deleted on a rolling basis — only 13 post-intervention transcripts survived, the earliest cohort due for deletion on 2026-09-06. **This archive stops that clock for everything that existed on 2026-08-19.** **What was verified.** 47/47 files copied; **46 confirmed sha256-identical to source**. The 47th is the live session's own transcript, still being appended at copy time — recorded in `MANIFEST.json` as a snapshot rather than silently counted as verified. **Read `MANIFEST.json` for provenance, not the filesystem.** Each entry carries `sha256`, `bytes` and the source `mtime` **as recorded data**. This is deliberate: mtime is mutable, and on 2026-08-17 a bulk frontmatter repair moved 20 records' mtimes and broke the wake by promoting an April session to `Last wrap`. A hash in a manifest survives what a timestamp does not. ## ⚠ What this archive does NOT do **It covers only files that existed on 2026-08-19.** It is a snapshot, not a mechanism. Sessions run after that date still land in the pruned directory and will still be deleted at 30 days unless the copy is repeated. The recurring case is named in PENDING-147 and is **not** discharged by this archive. **It is one copy on one disk.** The deletion clock is stopped; disk-loss is a different risk and is not addressed here.