chore(memory): phase 4 keeps judgment capitalization triggers
This commit is contained in:
1 parent
15d9dae964
commit
45b2b6b592
1 file changed
+1
-1
@@ -51,7 +51,7 @@ Shared rules for every phase:
|
||||
- Per-prompt retrieval: local score of registry headings (`## BDR|LRN|BLK|EVAL-` lines) against the typed prompt, top 3-5 `ID — title` lines as `prompt.submit` `context` above a threshold; no model call. Optional `memory_search` tool (`$.tool.register`, `isDeferred: false`) for skills (analyze-before-plan pass 1 calls it instead of grep).
|
||||
- Capitalization proposals on observed milestones only: a `feat`/`fix` commit or a `gitflow finish` seen in `tool.call` → one context note at the next prompt (never per turn, never at Stop).
|
||||
- Proof: digest canary after start, after compaction, after /clear; retrieval precision on 10 real prompts from journal history; zero note on turns without milestone.
|
||||
- Cleanup: CLAUDE.global.md "Session start" step 1 (read registries) → mod; "Proactive capitalization" paragraph shrinks; analyze-before-plan pass 1 points at the tool; fix the reconcile engine gap seen 2026-10-23 (`reconcile_blk_open` ignores header `[resolved]`) since the digest reuses it.
|
||||
- Cleanup: CLAUDE.global.md "Session start" step 1 (read registries) → mod; "Proactive capitalization" paragraph KEPT (design choices, surprising discoveries, dead ends leave no commit: only the model sees them; the mod adds the commit/merge triggers, never replaces the judgment ones; writing always stays model draft + user approval, format checked by the phase 2 guard); analyze-before-plan pass 1 points at the tool; fix the reconcile engine gap seen 2026-10-23 (`reconcile_blk_open` ignores header `[resolved]`) since the digest reuses it.
|
||||
|
||||
- [ ] **Phase 5, per-project profiles, native and concurrent (user ask 2026-10-24)**
|
||||
- Today `lib/profile.sh` is global (symlinks skills/ ↔ skills-disabled/, `claude plugin enable|disable` user scope): every open session shares one profile. Target: each session gets its own profile, so web in one project, full in another, backend in a third, at the same time.
|
||||
|
||||
Reference in new issue
Block a user