David F GliddenandClaude Opus 5
0fbd4f625a
Steward-authorized. 47 files copied to ~/.claude-transcript-archive/raw/, 46/47 verified sha256-identical to source by readback; the 47th is this session's live transcript, recorded as a snapshot rather than counted as verified. Manifest records sha256/bytes/mtime as data because mtime is mutable. Manifest and README are tracked here; the 114 MB of raw transcripts are not (42 MB gzipped, ~1.5x the existing .git, permanent in history). Explicitly NOT discharged: the recurring case (post-2026-08-19 sessions still prune at 30 days) which needs a ruling with leg (ii); single-disk risk; and 21 of the baseline's 64 transcripts, already deleted before this ran, leaving the 14% baseline only partly auditable. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
38 lines
2.2 KiB
Markdown
38 lines
2.2 KiB
Markdown
# 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.
|