session 2026-07-28: correct fabricated timestamps + rename evening->early-afternoon

Steward caught that the session was filed 'evening' at 13:29. Root cause is
larger than the label: every ISO timestamp in today's Symmetria ledger was
inferred from narrative position, never read from date(1). 14:10 was 40min in
the future; the prior session's 13:30/13:50 entries were written at mtime
11:35. Values annotated rather than silently corrected (unrecoverable); order
remains reliable. Skill defect harvested: symmetria §4 specifies the timestamp
FORMAT and not its SOURCE.

Also: chamber-grounding directive (constitution+charter+runbook) recorded as
standing feedback; honest census of where the Chamber vision actually lives
(seven sources, not one).

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

claude/memory/skill-harvest-register.md

@@ -670,3 +670,6 @@ The line already says *"Check for an existing tool — and our own register —
 
 **PROPOSED — add to `_curation/conversion-runbook.yaml` `verification:`: the ledger-delta confound.**
 Regenerating the quality ledger showed 20 files moving `A-convention` → `+B-textdamage` **that had not degraded**: `audit_corpus.py` was unchanged *and* the files were unchanged, but it **dynamically imports** its classifiers and `verify_conversion.py` changed 2026-07-21. In a declared-data architecture where tools are thin consumers, *"did the script change?"* is the wrong question. Proposed clause: **"A ledger regenerated across a change to its instrument produces a delta mixing corpus change with instrument change, and the output cannot distinguish them. Before treating a delta as corpus fact, re-run the old instrument on the new corpus, or stamp each row with the classifier version."** Load-bearing for the re-gate work ahead, where **ledger deltas are the intended progress metric**. Full record: `_curation/tool-evolution-log.md` 2026-07-28.
+
+**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.