chore(todo): velox restow-conflict note on per-host task; file processed handoffs

1 files changed, 19 insertions, 0 deletions

diff --git a/assets/outbox/2026-06-10-1816-from-rulesets-handoff-migrate-memories.org b/assets/outbox/2026-06-10-1816-from-rulesets-handoff-migrate-memories.org
new file mode 100644
index 0000000..25ca602
--- /dev/null
+++ b/assets/outbox/2026-06-10-1816-from-rulesets-handoff-migrate-memories.org
@@ -0,0 +1,19 @@
+#+TITLE: One-time guided memory sweep — promote durable facts to the agent KB
+#+DATE: 2026-06-10
+
+* What this is
+
+The shared agent knowledge base is live: Craig's org-roam at ~/org/roam, now a git repo (git@cjennings.net:roam.git). The new global rule ~/.claude/rules/knowledge-base.md carries the full contract: query commands, write schema, the work/personal boundary, and inclusion criteria.
+
+This handoff asks for the one-time Phase 1.5 sweep in this project (agent KB spec, rulesets).
+
+* What to do (once, next session)
+
+1. Read this project's harness memory dir (~/.claude/projects/<encoded-cwd>/memory/).
+2. Classify each fact against knowledge-base.md's inclusion criteria: KB-worthy (durable, cross-project or cross-machine value) / stays local (project-scoped, or already encoded in a rules file) / stale-delete.
+3. Propose the batch to Craig for approval, then write approved facts as one-node-per-fact files under ~/org/roam/agents/ per the rule's schema (pull first, commit + push after).
+4. Reply to rulesets' inbox with counts (promoted / kept local / deleted).
+
+Work-classified projects don't write to the KB — if that's this project, the sweep is a no-op; just reply saying so.
+
+Worked example: rulesets promoted 3 of its 6 memories (a notify pattern, the pdftools venv, the gpg-agent SSH TTL trap) and kept the rest local as rule-encoded or project-scoped.