Files
dotfiles/claude/memory
David F GliddenandClaude Opus 5 e64bae78fc prefs: name the store a claim was read from; app memory as a second uncheckable cache
Test 3 passed on the hardest axis — offered plausible material to confabulate a
conflict resolution from, the jurist declined and named the kind of gap instead. So
the battery now has a demonstrated FAIL condition it did not trip, which is what
makes the earlier passes mean anything.

Then I got the follow-up wrong twice. The answer cited "the Savall file"; I found it
in none of the six exposed documents and nowhere in the vault, and reported that with
a confabulation framing. The steward supplied the source (Claude.app memory) and
then that he watched it search memory mid-answer. So it WAS reading, from a store
outside my reach, and the wording was accurate provenance from its side. My check
established one thing — not in OUR files — and I let it stand in for a claim about
the world. Q2 one level up: I ran a negative check without establishing that the
instrument covered the domain.

The finding is mine. I designed the MCP server reasoning as though the jurist saw
the preferences plus our six documents; it also has an actively-retrieved memory
store that nothing on this side can read or audit. Unlike §Standing Context, that
cache cannot be seen drifting. Two bullets added: name which of the four stores a
claim came from, and flag memory-sourced facts for steward cross-check — because the
executor structurally cannot verify them.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WuMjg3ipEVa3n8CoSzoyvc
2026-07-28 11:28:39 +02:00
..