Files
ratatoskr/persistent-memory.d/2026-07-01-salience-scorer-non-discriminating-3-way-rout.md
vh ff1f9ca1e8 memory: /snapshot — #368 silo test passed; two-tier migration; stores scrubbed
- #368 (user,character) memory silo test DONE + PASSED live (WT b127):
  write-side conjunctive {end_user,agent_self} scoping + read-side cross-
  character isolation both proven end-to-end; betty (throwaway) deleted,
  Sindra intact. Full record in persistent-memory.d/2026-07-18-368-silo-
  test-passed.md. Retired the stale "silo test in progress" in-flight blocks.
- Two-tier migration: split 152 over-threshold dated entries into
  persistent-memory.d/ detail files, leaving one-line pointers in the index
  (startup load ~196KB -> ~53KB; bodies now load on demand).
- Tier-3 stores scrubbed clean (memory 0 / affect 0, provider restarted
  empty); persistent-memory + detail file updated to reflect the scrub.
2026-07-17 21:39:18 -07:00

735 B
Raw Permalink Blame History

[2026-07-01] Salience scorer non-discriminating → 3-way routing. Persistence-side finding: 51/56 promoted chunks at salience 0.9-1.0, throwaway "17×23?" scored 1.0 tied with a real fact (textbook zero-shot-LLM-self-rating); recall-utility untracked (access_tally=0, our search read-only). Routed: Worldtree #335 (the code fix, deferred behind their waves) + brokkr-smithy-dev R-target proposal (scoring+eval methodology — few-shot/distill/fine-tune, eval design, weak-supervision; msg 01KWGM970H…, awaiting) + ratatoskr provides the eval-instrument (designed-probe salience dumps). Salience gates PROMOTION not RECALL-ranking (our search is cosine-only), so bad salience = storage bloat, not bad recall.