aboutsummaryrefslogtreecommitdiff
path: root/todo.org
diff options
context:
space:
mode:
authorCraig Jennings <c@cjennings.net>2026-05-24 03:10:28 -0500
committerCraig Jennings <c@cjennings.net>2026-05-24 03:10:28 -0500
commit9b0fbad50c90628e138920785d3b8f8cc69ab3d2 (patch)
tree6ef9e1cb8b31056f74a065fdf880039a01fa2d02 /todo.org
parent349a8c74bd9d1a0ba2cee1050f6421d05bf8c6db (diff)
downloadrulesets-9b0fbad50c90628e138920785d3b8f8cc69ab3d2.tar.gz
rulesets-9b0fbad50c90628e138920785d3b8f8cc69ab3d2.zip
chore(ai): archive session record, regen lint follow-ups, fix dangling todo link
The claude-memory clone was removed this session, so the todo entry's file: link to it would dangle — switched to plain text.
Diffstat (limited to 'todo.org')
-rw-r--r--todo.org2
1 files changed, 1 insertions, 1 deletions
diff --git a/todo.org b/todo.org
index 8c2ed04..4e810da 100644
--- a/todo.org
+++ b/todo.org
@@ -43,7 +43,7 @@ picks up the same memory tree.
Worked through dotfiles → rulesets → dedicated repo. Dropped stow/dotfiles (machine config, wrong cadence) and rulesets (it's pulled first in every session, so memory edits would dirty its tree and skip the startup =git pull --ff-only=). Chose a dedicated private repo on cjennings.net: storage is unified there while recall stays per-project (the encoded-cwd subdirs), since pooling recall would hurt relevance and risk work-private facts surfacing in personal-project artifacts.
*** 2026-05-23 Sat @ 16:12:48 -0500 Shipped: claude-memory.git + folded symlinks
-Created bare =git@cjennings.net:claude-memory.git=, cloned to [[file:/home/cjennings/.claude-memory/][~/.claude-memory]], moved all 7 per-project =memory/= dirs in (54 files; work has 40) and replaced each live =~/.claude/projects/<enc>/memory= with a folded dir-symlink so new memory lands in the clone and a push syncs it. Added =link-claude-memory.sh= (idempotent — recreates the symlinks on a new machine after clone) + README. Private repo, never GitHub (carries work/DeepSat memory). Initial import pushed (=f496370=).
+Created bare =git@cjennings.net:claude-memory.git=, cloned to =~/.claude-memory= (later deleted in the reversal below), moved all 7 per-project =memory/= dirs in (54 files; work has 40) and replaced each live =~/.claude/projects/<enc>/memory= with a folded dir-symlink so new memory lands in the clone and a push syncs it. Added =link-claude-memory.sh= (idempotent — recreates the symlinks on a new machine after clone) + README. Private repo, never GitHub (carries work/DeepSat memory). Initial import pushed (=f496370=).
*** 2026-05-24 Sun @ 01:53:35 -0500 Reversed the migration — back to unmanaged per-project memory
Cancelled the follow-up brainstorm and undid the dedicated-repo migration at Craig's call. Moved all 7 memory dirs back to =~/.claude/projects/<enc>/memory/= (content preserved), deleted the =~/.claude-memory= clone, and deleted the bare =claude-memory.git= on the server. Memory is back to its original at-risk state, so the task reopens at [#C] pending a direction. The brainstorm landed on a two-tier idea for whenever this resumes: promote general lessons into a rulesets-tracked file symlinked into =~/.claude/rules/= (loaded into every project natively, one repo), and keep project-specific memory under each project's own =.ai/memory/= (committed where =.ai/= is tracked, at-risk where it's gitignored). Not implemented.