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-link-treatment-one-rule-two-exceptions.md
+5 -2
View File
@@ -1,9 +1,12 @@
---
name: ARC link treatment — one rule, two named exceptions
description: Predictability principle for ARC link styling — single global treatment per spec §VII.c, with avatar-link and Reading Compass as the only exempt elements
description: Predictability principle for ARC link styling — single global treatment
per spec §VII.c, with avatar-link and Reading Compass as the only exempt elements
type: feedback
originSessionId: 8d9ac240-47df-4578-aec1-a9dd32965027
permalink: claude-memory/feedback-arc-link-treatment-one-rule-two-exceptions
---
ARC link treatment follows **one rule, two named exceptions** — captured by steward 2026-05-02 during the §VII.c link-spec drafting + SCSS migration session.
> *"the avatar and reading compass are the only links that need special treatment. The rest should be predictable and crafted with care"*
@@ -19,4 +22,4 @@ ARC link treatment follows **one rule, two named exceptions** — captured by st
- When you encounter a context-specific link rule that diverges from §VII.c, the question is NOT *"is this a different valid pattern?"* but rather *"is this (a) legacy material destined for an archival collection where preservation overrides current-spec alignment, or (b) a cascade artifact to be reconciled?"* Don't propose new sub-spec sections for the divergence; reconcile it or archive it.
- The earlier impulse (mine, 2026-05-02) to spec multiple sub-variants (§VII.c.ii catalogue, §VII.c.iii quiet-nav, §VII.c.iv button) was over-elaboration. Resist that pattern. The simpler frame — *one rule, two exceptions, everything else predictable* — is correct.
**Related:** care-over-traffic (work answers to itself; quality + predictability + accountability matter even at low traffic); the broader "would Alexander do it like this?" discipline against unnecessary elaboration.
**Related:** care-over-traffic (work answers to itself; quality + predictability + accountability matter even at low traffic); the broader "would Alexander do it like this?" discipline against unnecessary elaboration.