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>
1.3 KiB
name, description, type, originSessionId, permalink
| name | description | type | originSessionId | permalink |
|---|---|---|---|---|
| Project focus April–May 2026 | L2 parked (steward needs thinking time, L1 not yet reliable). L1 scaling + agent circles are the focus until end of May. Seb wants L1 ready for anyone to use by end of May. | project | a3ddbf34-da48-4129-acba-658f2f869783 | claude-memory/project-focus-april-may |
L2 governance: PARKED as of 2026-04-10. Steward needs time to think. No point advancing L2 while L1 substrate isn't wrinkle-free. Will resume soon — no timeline.
L1: PRIMARY FOCUS. Seb wants L1 ready to scale (anyone can use it) by end of May 2026. Steward actively on L1 production work alongside Seb (re-affirmed 2026-04-19 — Seb too spread thin to carry alone; steward's role extends from stewardship/jurist into hands-on L1 reliability work, audit drafting, diagnostic test branches, PENDING drafting, etc.).
Why: L1 reliability is prerequisite for everything downstream. L2 constitutional work requires full-depth steward attention, not sprint-squeezed sessions. The dependency chain is honest: get the substrate right first.
How to apply: Don't propose L2 governance work or constitutional advancement. Focus executor energy on L1 reliability, scaling, and agent circles. When L2-adjacent questions arise naturally from L1 work, note them but don't pursue.