ratatoskr/persistent-memory.d/2026-07-13-vendored-the-brokkr-r34-psych-profile-canon-v.md at main

Files

T

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

596 B

Raw Permalink Blame History

[2026-07-13] Vendored the brokkr R34 psych-profile canon (Vuong-directed) — BOTH files, not just the parameters. brokkr said "vendor alongside the authoring-spec you already hold"; I held its content but never a pinned repo copy, so I vendored both (psych-profile-parameters.md + psych-profile-authoring-spec.md) under docs/vendor/brokkr-r34-psych-profile/ — makes the parameters' "authoring-spec governs on conflict" clause resolve against an in-tree file, not a dangling pointer. brokkr confirmed keeping both is the better setup. tolerate_drift; brokkr owns + pings on change.

596 B Raw Permalink Blame History

596 B

Raw Permalink Blame History