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

chore(memory): Basic Memory trial begins — sync normalization baseline (283 files)

Browse Source 
Basic Memory v0.21.6 first sync over the live memory dir (steward-authorized
live-dir trial, Option A 2026-06-06): adds permalink: to frontmatter, refolds
long YAML description lines, strips final newlines. Bodies untouched —
verified via full diff classification. From this commit forward, any diff in
claude/memory shows only what Basic Memory or the session writes.

Trial design: MemPalace untouched as incumbent; git status check on this dir
at every wrap; end-of-day evaluation (recall quality, sync robustness,
rebuild-from-files, malformed-file behavior).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
David F Glidden
2026-06-06 09:52:17 +02:00
co-authored by Claude Opus 4.8
parent 161fad7ae2
commit 3f9a89b00c
283 changed files with 2055 additions and 620 deletions
Download Patch File Download Diff File Expand all files Collapse all files
claude/memory/feedback-articulate-toolchain-fit-before-executing.md
+6 -2
View File
@@ -1,9 +1,13 @@
---
name: Articulate toolchain fit before executing conversion or processing work
description: Before running any conversion/processing tool, surface why this tool is the right one for this input, what its limits are, and where in the broader toolchain it sits. Universal-tool framing is wrong; tools-by-input-type is right.
description: Before running any conversion/processing tool, surface why this tool
is the right one for this input, what its limits are, and where in the broader toolchain
it sits. Universal-tool framing is wrong; tools-by-input-type is right.
type: feedback
originSessionId: a5411fd1-4a96-43e7-aa1a-1a50d8951a8f
permalink: claude-memory/feedback-articulate-toolchain-fit-before-executing
---
When proposing or executing **conversion / processing operations** (EPUB → MD, PDF → MD, OCR, transcription, etc.), do not present a single tool as "the" tool. **Articulate the toolchain fit first.**
**Why:** Steward's articulation (2026-05-13): *"I thought that pandoc was the tool for conversion and document creation. I'd like to know more about where the current toolset is truly ideal for my needs. Now you have enough experience with me to know how I work, and, remember that we haven't even begun with the historical treatises… they could prove more difficult to process."*
@@ -29,4 +33,4 @@ For the steward's likely future corpus (historical treatises, scanned classics,
- **Calibre's ebook-convert** — handles weird EPUB edge cases that pandoc can't.
- **Direct text extraction (pdftotext)** — fast but loses all structure; useful as a fallback or for quick inspection.
The historical treatises will likely need OCR + docling + manual review per text — not a single automated pass. Treat as research-grade conversion: surface that reality before suggesting a one-line command.
The historical treatises will likely need OCR + docling + manual review per text — not a single automated pass. Treat as research-grade conversion: surface that reality before suggesting a one-line command.