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:
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
@@ -1,9 +1,15 @@
---
name: Action completes the outcome — integration completes the work
description: Umbrella drift pattern across multiple layers (substrate, build, editorial, memory). The visible outcome appears complete; the integration step that makes the artifact durable/findable/correct is silently skipped. Surfaces as deploy ≠ commit, write ≠ index, draft ≠ verify, count ≠ vault-write. Saved 2026-05-06 after three same-shape instances in a single session.
description: Umbrella drift pattern across multiple layers (substrate, build, editorial,
memory). The visible outcome appears complete; the integration step that makes the
artifact durable/findable/correct is silently skipped. Surfaces as deploy ≠ commit,
write ≠ index, draft ≠ verify, count ≠ vault-write. Saved 2026-05-06 after three
same-shape instances in a single session.
type: feedback
originSessionId: 3bf7ae75-1138-4745-9024-0c40b3755ad3
permalink: claude-memory/feedback-action-completes-outcome-integration-completes-work
---
**Pattern:** A structural action produces a visible outcome that *looks* complete. The action's integration step — the move that ties the outcome into a durable, findable, or verified state — is silently skipped. The work appears done; the work is not done. The drift is invisible until a downstream check (next session, next collaborator, next verification) surfaces the gap.
## Instances of the same shape
@@ -71,4 +77,4 @@ The contamination architecture: the system is *trained to terminate on visible s
The per-layer instances are useful for specific recall (when next at the deploy step, recall *deploy ≠ commit*). The umbrella is useful for *new layers as they emerge* — when a new instance surfaces (a new "X ≠ Y" pair), the umbrella says: this is the same pattern, apply the same discipline (integration step is part of the work, not after it).
**Steward authorization to save**: *"yes"* (2026-05-06, after I named three same-shape instances and asked whether they warranted one umbrella entry rather than three siblings).
**Steward authorization to save**: *"yes"* (2026-05-06, after I named three same-shape instances and asked whether they warranted one umbrella entry rather than three siblings).