esh-pfi-infrastructure/persistent-memory.d/2026-07-09-granite-gen-memory-extractor-bind-host-synced-on.md at abc8f0ceab56b93e805f51afdb94aca2477c0ec4

Files

T

vh d710e56aca memory: migrate persistent-memory.md to two-tier index (53 detail files)

Split the 53 over-threshold dated log entries (Recent decisions, Tried
and abandoned) into per-entry persistent-memory.d/<slug>.md detail files,
leaving one-line pointers in the index; the 10 short entries stay inline.
Startup index drops 60,527 -> 25,256 bytes (492 -> 270 lines); entry
bodies move verbatim to on-demand detail files, so a fresh session loads
~25 KB instead of ~60 KB and pulls a detail file only when its pointer is
relevant. Top matter (Repo purpose, Tools & conventions, Current state)
is unchanged; both archival back-references preserved.

CLAUDE.md persistent-memory section now documents the index<->detail read
discipline (read the index, pull details on demand, never bulk-read the
dir, commit both together).

Auto-archival still held every dated entry back (all <30 days old); the
July burst begins aging past the 30-day guard ~2026-07-31.

2026-07-15 13:33:42 -07:00

5.0 KiB

Raw Blame History

[2026-07-09] granite→gen memory_extractor bind host-synced on demo+personal Worldtree (Vuong-directed, #335 Slice-4). Changed model_roles.yaml memory_extractor binds.catalog_id summarizer→gen (overrides intact: thinking:false/temp0/8192) on BOTH /opt/worldtree{,-personal}/config; memory_distiller left on summarizer (range-scoped sed /memory_extractor:/,/memory_distiller:/ — the naive global replace would've hit both); backups *.bak-preqgen-20260709; validated via each container's OWN yaml parser. DEMO LIVE on gen (b43 d501e516732d auto-deployed mid-edit + its restart RACED my edit by ~2min → I restarted worldtree-worldtree-api-1 to activate; healthy, live process resolves memory_extractor=gen). PERSONAL NOW LIVE on gen too — Vuong authorized the restart (via wt-dev); restarted worldtree-personal-worldtree-api-1 after a PRE-FLIGHT that ran the app's OWN load_model_roles() (core/llm/roles.py:121) against the synced config INSIDE the running c9986cd container: gen in catalog, all 9 roles resolve, no DanglingBindingError → proven safe on the OLDER image BEFORE touching it (model_roles-delta-alone clean; no full-config-set sync needed). StartedAt 20:50:55Z, healthy, resolves gen. BOTH instances live on gen. LESSON: the bind-mount /opt/worldtree*/config SHADOWS the baked /app/config-defaults/ → the deploy alone never updates the ACTIVE config; the host edit is required AND a restart activates it (role registry cached at boot) — pre-stage BEFORE the deploy's restart or you race it. FOLLOW-UPS (non-blocking): (a) memory.extractor.user_pass parity block → self-serve from the b43 baked defaults.yaml (pydantic-default no-op); (b) stale gen provider description (Mistral-Small-4 → qwen3.6-35b-a3b-heretic) → wt-dev owns the REPO-side providers.yaml fix (operator's call — NOT purely cosmetic: the gen/dialogue + classifier entries carry Mistral-Small-4 SAMPLING defaults that drive mask/lofn/forseti/mimir dialogue, so wt-dev re-validates for qwen), host cosmetic sync pairs when it deploys. Gave wt-dev the VERIFIED canonical 4-alias set (backends+samplers read from the LIVE gateway config, not the doc); corrected docs/pfi/model-sampler-defaults.md seat 4 (had lagged QwQ-RpR-v4 → Deckard-PKD; live gateway was always Deckard). Operator SCOPED IN the character-RP re-point (2026-07-09): character→char-rp / thoughtful-character→char-rp-reasoning (character-rp per wt-dev's role semantics), moving character RP off the GENERAL qwen onto the dedicated Magidonia/Deckard seats. Relayed to wt-dev w/ the mapping principle + a SAMPLER-OVERRIDE warning (DROP character-rp's old temp0.75/top_p0.85 overrides — carried onto the dedicated seats they'd clobber the canonical RP tuning DOWNWARD) + ratatoskr-reach note (role call is transparent but Magidonia/Deckard quality/latency differs from gen). DONE 2026-07-09: wt-dev committed 5d4fa4a (v1.0.0b44, UNPUSHED — operator drives push); operator directed host-ahead-of-push, so I sourced BOTH config files directly from that unpushed commit (local ~/development/Worldtree checkout — capital W; git show 5d4fa4a:config/…) + mirrored VERBATIM to /opt/worldtree{,-personal}/config on demo+personal, paired-pre-flighted via the app's load_model_roles() (no DanglingBinding), restarted both → LIVE: character→char-rp, thoughtful-character + character-rp→char-rp-reasoning, memory_extractor→gen preserved. Backups *.bak-prerp-20260709. context_window VERIFIED (llama.cpp /props + char-rp-gguf .env): char-rp 131072, char-rp-reasoning 262144 (gave wt-dev to patch the repo from its interim 32768). HOST AHEAD of repo-remote until the operator pushes 5d4fa4a (baked config converges with the bind-mount on push+deploy). GOTCHA: demo≠personal — PERSONAL was already partly re-pointed (2026-07-06 AEON-era character→char-rp) so its delta was mostly stale-AEON-descriptions→Magidonia/Deckard
- character-rp + stripping personal's char-rp default_params temp0.7/top_p0.8 that CLOBBERED the gateway RP tuning downward; DEMO had no char-rp catalog entries at all (b44 adds them). Diffed each instance vs b44 before applying (both deltas = expected changeset only, nothing instance-specific clobbered). wt-dev PATCHED the context_window in b45/3384a37 (char-rp 131072, char-rp-reasoning 262144). BUMPED HOST-AHEAD on both instances (operator-directed 2026-07-09): mirrored b45's providers.yaml → /opt/worldtree{,-personal}/config, restarted, verified LIVE (char-rp ctx 131072, char-rp-reasoning 262144, bindings intact); backups .bak-b44interim-20260709. HOST now = b45 canonical (providers.yaml) + b44 (model_roles unchanged b44→b45). STILL PENDING: (1) operator's batched push of b44+b45 (5d4fa4a+3384a37) to converge the repo-remote — host is ahead, no fork; (2) user_pass parity block (defaults.yaml — NOT in either, separate). Threads 01KX3SGH/01KX48QP (worldtree-dev), monitor armed. See reference_corviduo_dev_emergency_ops.

5.0 KiB Raw Blame History

5.0 KiB

Raw Blame History