aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorCraig Jennings <c@cjennings.net>2026-05-23 16:14:20 -0500
committerCraig Jennings <c@cjennings.net>2026-05-23 16:14:20 -0500
commit0f4d1f852c48b80cc7db8c1643a90e8494428ff3 (patch)
treee1b641fc1f40709b4d6ed9d1705859da0974277b
parent3f802eb819bc9be572b230ac1bd142b7ce13d87f (diff)
downloadrulesets-0f4d1f852c48b80cc7db8c1643a90e8494428ff3.tar.gz
rulesets-0f4d1f852c48b80cc7db8c1643a90e8494428ff3.zip
chore(todo): close cross-machine memory sync via dedicated repo
I closed the memory-sync task. Memory now lives in a dedicated private claude-memory.git on cjennings.net, with each project's memory dir symlinked into a local clone so new memory lands in the working tree and a push syncs it. I settled on that over stow/dotfiles and over keeping it in rulesets, since rulesets sits on every session's startup-pull path and memory churn would dirty it. The task's dated entries carry the decision and the shipped details.
-rw-r--r--todo.org10
1 files changed, 7 insertions, 3 deletions
diff --git a/todo.org b/todo.org
index f3c4b48..20fc24f 100644
--- a/todo.org
+++ b/todo.org
@@ -7,7 +7,8 @@ Project-scoped (not the global =~/sync/org/roam/inbox.org= list).
* Rulesets Open Work
-** DOING [#A] Check that memories are sync'd across machines via git.m
+** DONE [#A] Check that memories are sync'd across machines via git
+CLOSED: [2026-05-23 Sat]
:PROPERTIES:
:LAST_REVIEWED: 2026-05-20
:END:
@@ -39,8 +40,11 @@ Create the destination in archsetup, move existing per-project
commit + push archsetup. After that, every machine running =stow=
picks up the same memory tree.
-*** VERIFY Approve stow-based sync of ~/.claude/projects via the dotfiles repo
-Held 2026-05-22: dotfiles are being split out of archsetup into their own repository, so the stow target is in flux. Revisit the stow approach (and the destination path) once that split settles — the target is the new dotfiles repo, not =archsetup/dotfiles/common/=.
+*** 2026-05-23 Sat @ 16:12:48 -0500 Decided: dedicated private repo, not stow
+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=).
** TODO [#C] Build =create-documentation= skill for high-quality project/product docs
:PROPERTIES:
:LAST_REVIEWED: 2026-05-20