David/dotfiles
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

session 2026-07-14: PENDING-58 rewritten (corollary struck); session file + MEMORY demote; feedback-close-low-hanging-fruit; KG +3; skill-harvest flag

Browse Source
This commit is contained in:
David F Glidden
2026-07-14 10:15:12 +02:00
parent b00294a1fb
commit 0a25b183ba
8 changed files with 195 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files
claude/memory/skill-harvest-register.md
+8
View File
@@ -471,3 +471,11 @@ The single place proposed skills live so they don't evaporate between sessions.
| **method-class-vs-calibration** | verification-ladder entry (primary) OR Symmetria §3 flag | **When a metric/gate fails to separate two cases, ask whether it is mis-CALIBRATED or structurally BLIND to the distinction — no amount of retuning a set metric reaches an order-only difference, because the blindness is in the method CLASS, not its threshold.** Antidote: reach for a different method *category* and order tiers strongest-most-specific-signal FIRST (exact ordered-string before fuzzy set metrics). Earned today: Jaccard=1.0 AND raw-overlap both TIED on Suetonius 'Grammarians' vs 'Rhetoricians' (identical token sets — both words in "Grammarians and Rhetoricians"); only the ordered STRING separates them, and it had to lead. The steward elevated it: "the problem was in the *category* of method, not its calibration… no amount of retuning a set metric would ever have separated them." Generalizes past this matcher — any check that ties/fails where a distinction is real. | `reference-verification-ladder.md` (a diagnostic instrument), with a possible Symmetria §3 shadow ("retune-a-structurally-blind-metric" = reaching for the calibration knob when the method class can't make the distinction) | **PROPOSED** |
*(One candidate, load-bearing and steward-named. Primary home is the verification-ladder — it's a positive diagnostic technique, not only a contamination shape. The §3-flag form is offered in case the steward reads it as the drift-shadow [reaching for the convenient tuning knob] rather than the instrument. His ruling on which home, or both.)*
### Harvest 2026-07-14 (PENDING-58 refuted / constitutional survey / the banked-record drift)
| Element | Kind | One-line | Where it lands | Status |
|---|---|---|---|---|
| **Symmetria §3 flag: answer-from-training-before-checking-the-banked-record** | Symmetria §3 flag | Answering an architecture/tooling/citation question — or proposing a tool/approach — **from training memory before grepping the banked docs + the tooling/landscape register** is contamination shape: the corpus often already holds the considered answer, with the exact option already *rejected*. Caught hard 2026-07-14 — re-derived TEI/DTS from training AND re-proposed external/Perseus alignment + the dormant MyCapytain runtime, BOTH rejected 2026-07-04; the 2026-07-03 anchor audit already had the finding. RECURRED within 48h of `didn't-consult-banked-notes` being flagged 07-12; the *steward* caught it, not me. Antidote: for any architecture/tooling/citation question, **grep the banked record (docs/ + the scan register + prior FOR-JURIST briefs) BEFORE answering from training.** Kin to [[feedback-resurface-banked-notes-before-rederiving]] + the solving-at-the-wrong-level drift, generalized from builds to Q&A. | Symmetria §3 | **PROPOSED** |
*(One flag, strongly earned — recurred within 48h of being named. A §3 flag would make me reach for the grep before the first from-memory answer.)*