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,13 @@
---
name: Deploy is not commit — visual verification masks missing durable artifact
description: A drift pattern where shipping a visible result (deployed page, build success) is treated as task completion, while the durable artifact (git commit + push) is silently skipped. Caught 2026-05-06 in the After the Reply Sources fix.
description: A drift pattern where shipping a visible result (deployed page, build
success) is treated as task completion, while the durable artifact (git commit +
push) is silently skipped. Caught 2026-05-06 in the After the Reply Sources fix.
type: feedback
originSessionId: 3bf7ae75-1138-4745-9024-0c40b3755ad3
permalink: claude-memory/feedback-deploy-is-not-commit
---
**Pattern:** I edit a file, run `make build` which deploys, the steward verifies visually, work appears complete — but `git commit` was never run. The repo and the deployment desynchronize. The next session inherits an inconsistent tree.
**Caught 2026-05-06**: After the Reply sequence-index Sources fix (three-em rule) was deployed via `make build` and visually verified by the steward. The commit step was skipped. Discovered at session-end via `git status` showing the file as modified (not committed). Committed retroactively as 3d96449.
@@ -28,4 +32,4 @@ The shape is identical: a visible/structural success-signal is treated as eviden
- Today's contamination-awareness: this is the editorial-process layer instance of the same pattern
- ARC CLAUDE.md prime directive: *"things done once, correctly, with lasting integrity"* — the integrity layer that was missing here was the repo, not the deploy
**Steward authorization to save:** *"please note it."* (2026-05-06, after I surfaced the catch)
**Steward authorization to save:** *"please note it."* (2026-05-06, after I surfaced the catch)