Files
dotfiles/claude/memory/feedback-catalogues-stale-walk-trees.md
T
David F GliddenandClaude Opus 4.7 e9e772d69c memory: bundle accumulated 04-17/26 + lock ARC about-page architecture
Safety checkpoint before deep-audit Phase 0 of the ARC repo. Steward-authorized
commit-everything for rollback safety.

ARC architectural locks (2026-04-26 evening):
- Path 1 enfilade structure (separate Colophon and Lex items)
- 8-door enfilade locked: Colophon · Lex · Framework · Vignette · Attention ·
  Chamber · Tools · Now (+ Bio quiet link)
- Adsum and threshold-hic as two distinct texts on the reflowed About page
  (steward verbatim: "They are certainly not the same text")

ARC consolidation pass (canonical tracker project-arc-rework.md, +~700 lines):
fold 04-23 evening (Norris read), 04-24 (lex-method authored, posture cluster,
§XII Sidenotes, ARC CLAUDE.md cleanup), 04-25 (marks cluster, colophon-at-scale,
full Vico/Harrison lex-chain), 04-26 (chamber-library walk, cluster scaffolds,
canonical-tracker discipline surfaced).

Sibling-file integration: four 2026-04-26 frame files folded into the canonical
tracker (Integrations A/B/C/D) with INTEGRATED redirect notices retained as
audit trail.

New durable feedback memories:
- feedback-canonical-workstream-tracker-discipline (umbrella drift surfaced
  2026-04-26 by steward; proposes /wake-up + /wrap-up amendments)
- feedback-catalogues-stale-walk-trees (steward feedback on chamber-library
  catalogue currency)

Implementation plan drafted for the coming week: Phase 0 deep audit → Phase 5
cleanup, with steward additions on second pass (deep audit; Chamber v1 as own
browsable archive; clean rebuild of cluster sources rather than moving test
artifacts as canon).

Also bundled (untracked accumulation since 04-17):
- ~24 session memory + ledger files for 04-17 through 04-26 work
- ~10 feedback memories (BMF + ARC + working-method)
- 5 project memories (lex-as-method, strunk-white queue, plus today's four)
- 4 user memories (duality-rules, formation-practice, foundation-work, humic-layer)

Steward-side modifications also in this commit: ~/CLAUDE.md, bin/bmf-start.sh,
open-tasks.md, project-focus-april-may.md, session-2026-04-17 — all
pre-existing, not from today's session.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-26 14:52:14 +02:00

3.2 KiB
Raw Blame History

name, description, type, originSessionId
name description type originSessionId
Catalogues in chamber-library are stale — walk the trees, not the catalogues Steward correction 2026-04-26. Any catalogue or index file in chamber-library is presumed stale. For inventory, recall, or substrate-survey, walk the actual file tree. Do not rely on CHAMBER_CATALOGUE.md, README.md, or similar summary documents as authoritative. feedback 87dfe384-b862-4deb-9676-24e43046528f

Catalogues are stale — walk the trees

Steward verbatim 2026-04-26: "that catalogue is stale (any catalogues you may come across will be stale)"

The rule

Any catalogue, index, or summary file inside chamber-library/ (or by extension any of the steward's working repositories) is presumed stale unless its mtime / content has been verified against the actual tree it describes. This includes but is not limited to:

  • chamber-library/converted_texts/CHAMBER_CATALOGUE.md (last updated 2026-03-28; the tree has grown substantially since)
  • chamber-library/README.md (claims "305+ texts, 147+ philosophers" — likely undercount)
  • Any subfolder README.md files
  • Auto-generated indices in indices/ (currently empty but the principle holds)

For inventory, substrate-survey, or recall of "what is available," walk the actual directories with ls, find, or recursive read. The tree is the canonical record; the catalogue is a frozen snapshot.

Why

The chamber-library grows through deliberate steward-additions (Mauss 2026-04-07, Derrida 2026-04-05, observer-problem-sources 2026-04-09, Aldus Younger + Teall + Jaccottet:Handke:Lichtenberg/ 2026-04-21–25, etc.). Catalogue updates lag and may never catch up. Trusting the catalogue means missing the most recently filed substrate — exactly the material most likely to be load-bearing for current threads.

This is also a particular shape of the canonical-library-not-checked-first family: catalogue-as-shortcut over actual tree-walk. The catalogue is a kind of canonical-library check, but a degraded one.

How to apply

When the steward asks "what's available" or "have a look at chamber-library" or when surveying for cluster-substrate or humic-layer voices:

  • Walk the relevant subtree directly (ls, find -maxdepth N -type f, or Glob).
  • If a catalogue is open in context, treat it as a navigation hint at best — verify each pointer against the actual file before claiming presence.
  • For "what's new since" questions, prefer git log --stat --since=YYYY-MM-DD or directory mtime sort over reading any catalogue's "last updated" line.
  • If a catalogue is needed for some downstream use (e.g., reader-orientation), surface that the existing catalogue is stale and propose either a fresh walk-derived inventory or a generation script — don't quietly re-publish stale data.

Cousin patterns

  • canonical-library-not-checked-first (2026-04-24, recurred 2026-04-25)
  • working-from-mental-summary-not-rereading-the-source (2026-04-25)
  • attribution-by-pattern-match-instead-of-verification (2026-04-24)

These all share the same underlying drift: substituting a compressed representation for the actual material. The lex-method's "read before claiming" applies to catalogues as much as to source texts.