David/dotfiles
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore(memory): Basic Memory trial begins — sync normalization baseline (283 files)

Browse Source 
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
Download Patch File Download Diff File Expand all files Collapse all files
claude/memory/feedback-arc-typology-recognition-scaffold.md
+6 -2
View File
@@ -1,9 +1,13 @@
---
name: ARC typology is a recognition scaffold, not a generation template
description: How to relate to the ARC content typology — it serves the steward's recognition of what arrives as ARC-shaped, not a production pipeline. Reference documents and pieces are grounds for recognition, not templates for generation.
description: How to relate to the ARC content typology — it serves the steward's recognition
of what arrives as ARC-shaped, not a production pipeline. Reference documents and
pieces are grounds for recognition, not templates for generation.
type: feedback
originSessionId: b9a0781b-1d1c-418f-8ca3-70a51db83580
permalink: claude-memory/feedback-arc-typology-recognition-scaffold
---
# ARC typology — recognition scaffold, not generation template
**Rule:** the ARC content typology exists to let the steward *recognize* what is ARC-shaped when a thought arrives. It is not a production pipeline, not a notebook-to-public, not a schema to fill.
@@ -64,4 +68,4 @@ Reference texts (Bachelard's *Poétique de la Rêverie*, Visuddhimagga, Jaccotte
- Corpus reclassifications (ARC audit follow-ons) wait until §1 is comprehensively locked, minimum through the adjacent types of whatever's being reclassified.
- Safe reclassifications: those where the *source* type is stable and the *target* type is locked, AND no currently-DRAFT type could plausibly claim the piece. Today (2026-04-21): Graffiti Girl → Reverie is mostly safe (both Observation and Reverie are defined well enough that Graffiti Girl is clearly Reverie), but still wait for Observation's LOCKED state so the boundary is explicit.
- When the spec is nearly complete, run the audit pass with the full vocabulary available. Then reclassify.
- **Executor rule of thumb:** when steward authorizes a spec decision, that authorizes *writing the decision into the spec*. Applying the decision to corpus pieces is a separate authorization, typically to be granted after the whole scaffold is stable.
- **Executor rule of thumb:** when steward authorizes a spec decision, that authorizes *writing the decision into the spec*. Applying the decision to corpus pieces is a separate authorization, typically to be granted after the whole scaffold is stable.