session 2026-07-28 mid-afternoon: PENDING-83/REVIEWED-83 (V-DPDF design gate passed) + PENDING-84/85/86 + maps home + memory-pointer portability

Harrison re-gate pilot broke the mechanism before converting a byte, and the
break was constitutional: tier_of() faithfully implements the ratified
evidence-tier table, which enumerates tiers by FORMAT, so 16 born-digital-PDF
canonicals with real ground truth receive a false ABSTAIN. Jurist design-gate
PASSED with two corrections (independence into the constitutional text, NOT by
analogy with V-TEXT which ruled the other way; the demonstration is of two
instruments and the second has no control). REVIEWED-83 placed by the steward.

Also: steward-facing maps given a durable home after one was lost and four more
found unbacked; memory pointers made home-anchored and self-diagnosing.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WuMjg3ipEVa3n8CoSzoyvc

claude/memory/skill-harvest-register.md

@@ -673,3 +673,14 @@ Regenerating the quality ledger showed 20 files moving `A-convention` → `+B-te
 
 **PROPOSED (2026-07-28, same wrap) — patch `symmetria` §4: name the SOURCE of the timestamp, not only its format.**
 §4 currently reads *"Use ISO timestamps. Be terse."* It specifies the **format** and leaves the **source** to invention — and invention is what it got. Across three sessions I wrote every ledger timestamp from narrative position without once running `date`: `14:10` landed 40 minutes in the future, and the previous session's `13:30`/`13:50` entries were written when that file's mtime says `11:35`. The harness supplies the *date* in a system reminder and never the *time*, so the skill's instruction is satisfiable only by fabrication — and ISO-8601-at-minute-precision is exactly the format that reads as measured. Proposed replacement: **"Timestamp each entry from `date '+%H:%M'` — read the clock, never infer it from where you are in the session. The harness supplies the date, not the time; an ISO timestamp is a measurement claim like any other."** Sibling for `wrap-up` §2, whose session-file naming convention (`morning`/`afternoon`/`evening`) has the same defect: this session was filed "evening" at **13:29**. Earned + steward-caught; the correction is in the ledger's head notice rather than silently applied to the values, which are unrecoverable.
+
+## Harvest 2026-07-28 (mid-afternoon — the V-DPDF ruling; 2 candidates, both evidence-backed)
+
+| Skill | Kind | One-line | Origin | Status |
+|---|---|---|---|---|
+| `/wake-up` | patch | **Read the day's own Symmetria ledger when one exists for today.** The wake reads `MEMORY.md` + the session file + the KG, but never today's ledger — so on a multi-session day every lesson banked earlier that day is invisible to the session that follows it. Cost, twice in ten minutes: I ran `find` on a symlinked directory without `-L` and nearly reported "no ledger today" against a file whose line 24 *records that exact trap*, written at 11:05; then I carried a re-derived link-canary diagnosis into the briefing as a fresh finding when its root cause was banked at 11:05 and an open horizon already proposed the fix. Proposed: if `session-ledger-<today>.md` exists, read its **Returns** and **Open horizons** at §2.a. Cheap (one read), and the 4th, 5th and 6th sessions of a day are exactly when it pays. | 2026-07-28 (2 instances, ~10 min apart, both self-caught only because the absence was implausible) | **PROPOSED** |
+| `/jurist-package` | patch | **Require a mechanical verbatim-containment proof over every quoted clause, reported in the package.** The skill already says *"Quote, never paraphrase"* and *"path-verify the reading list"* — but carries **no mechanical check**, and prose discipline did not hold: this session's package fabricated the end of a promotion-criterion quote (*"we already have"* for *"we already run **is** the promotion test. The bar for 93% (1,191/1,284) of the corpus"*) **inside the Grounding section**, in a package about verification. A containment check over all 45 quoted lines, run with a positive control, caught it before filing. This is also the jurist's own recommended option (b) under PENDING-86: since the jurist **cannot read the chamber constitution** (`governance_read` exposes six keys, not the spec), the executor's self-check is currently the *only* instrument touching the primary substrate for this class — which is precisely why it must be mechanical rather than promised. | 2026-07-28 (self-caught fabrication; converges with the jurist's PENDING-86 rec.) | **PROPOSED** |
+
+**Not proposed:** a `/pdf-origin-classify` skill — `classify_pdf_origin.py` is scratchpad evidence for an unratified proposal; skilling it now would codify a method the jurist has explicitly **not** yet accepted (Q3's Instrument-B control is outstanding). Revisit only if V-DPDF ratifies.
+
+**Repo `CLAUDE.md` freshness (§1.6) — surfaced, NOT applied.** REVIEWED-83 shifts `chamber-library`'s governance posture (a new declared evidence kind; independence as a constitutional requirement) and would add `V-DPDF` to its vocabulary. Per the FIX-vs-PROPOSAL split one level up, a **governance-posture** change is surfaced for steward review rather than auto-applied — and here it is also **premature**: the spec text is not drafted and ratification is gated on the Q3 demonstration. Apply at ratification, not now.