chore(memory): Basic Memory trial begins — sync normalization baseline (283 files)
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:
co-authored by
Claude Opus 4.8
parent
161fad7ae2
commit
3f9a89b00c
@@ -1,10 +1,13 @@
|
||||
---
|
||||
name: feedback-trust-prior-pass-frame
|
||||
description: "When extending a prior verification, re-run it at the scope of the extension. Frame-inheritance from a deep-read is contamination shape — the prior pass tested what it tested; your extension claims things the prior pass did not test."
|
||||
metadata:
|
||||
description: When extending a prior verification, re-run it at the scope of the extension.
|
||||
Frame-inheritance from a deep-read is contamination shape — the prior pass tested
|
||||
what it tested; your extension claims things the prior pass did not test.
|
||||
metadata:
|
||||
node_type: memory
|
||||
type: feedback
|
||||
originSessionId: fd7dd184-f64d-4f13-a1bd-abe1fa26192e
|
||||
permalink: claude-memory/feedback-trust-prior-pass-frame
|
||||
---
|
||||
|
||||
When a prior verification produced a finding, that verification tested *something* — at a specific scope. The next consumer of the finding tends to extend its conclusion into adjacent domains the prior pass did not test, without re-verifying at the extended scope. This is **frame-inheritance contamination** — the prior pass was honest at its level; the inheritance carries it past its level silently.
|
||||
@@ -24,4 +27,4 @@ When a prior verification produced a finding, that verification tested *somethin
|
||||
|
||||
**Related:** [[feedback-rank-on-fields-you-actually-write]] (a sibling drift family — claiming a system ranks by a field nothing populates is a related contamination of "explicit claim doesn't match operational reality"); [[mempalace-is-unaffiliated-stopgap]] (similar shape: an explicit fact known but the operational framing carries an older view).
|
||||
|
||||
**Caught 2026-05-28** by steward on *"How did you miss this before?"* — leading to the four-pass pre-build audit and the discovery that the deep-read had three other findings whose scopes also needed correction (parent amendment 2/3 shipped not fully shipped; B1 governors partially exist; etc.). The pattern was structural across the workstream, not isolated to A1.
|
||||
**Caught 2026-05-28** by steward on *"How did you miss this before?"* — leading to the four-pass pre-build audit and the discovery that the deep-read had three other findings whose scopes also needed correction (parent amendment 2/3 shipped not fully shipped; B1 governors partially exist; etc.). The pattern was structural across the workstream, not isolated to A1.
|
||||
Reference in New Issue
Block a user