DUNIN7 · LOOMWORKS · RECORD
record.dunin7.com
Status Current
Path change-requests/cr-2026-138-persist-lists-pin-temperature-v0_1.md

CR-2026-138 — Persist Structured List Data; Pin Classifier Temperature — v0_1

Version. 0.1 Date. 2026-07-03 Status. Drafted, not staged for build. Number 138 confirmed free at staging (highest prior: CR-2026-137). Base: engine main @ 69c8d8d, OL main @ 443c950. No build yet. Repos. loomworks-engine, loomworks. Diagnosed via. CR-2026-137 Post-Ship Gaps diagnosis (unstaged, this session).


Part A — structured list data does not survive reload

find_files matches, and likely show_held's held items, only render immediately after the search — the same session, before any reload. On reload, only the plain message text persists (record_turn's generic step-7 call, unlike CR-2026-136's upload-specific fix, was never widened to carry structured list data). toDisplayTurns() does not populate matchedFiles/heldItems from reloaded history — only the live optimistic-send path does.

Fix: extend the generic step-7 record_turn path (not just uploads') to persist structured list content the same way CR-2026-136 did for upload descriptions, so reloaded turns can rebuild the list body, not just the header text.

Step-0 must confirm whether show_held has the identical gap (untested by luck in prior verification, not confirmed exempt) before assuming it needs no fix.


Part B — classifier temperature not pinned

_call_classifier_llm calls the model with no temperature parameter — classification has always been non-deterministic. Borderline phrasings (confirmed: "list images" at 0.82 confidence, close to the 0.7 threshold) can misroute on unlucky sampling. Pre-existing, not introduced by CR-2026-137, but newer intents are more exposed to it.

Fix: pin temperature=0 on the classifier call for consistent, repeatable routing.


Seed check

No conflict. Both fixes reinforce the seed's Memory commitment — accumulates with provenance, reliably recallable — undermined today by a list that vanishes on reload and routing that isn't consistent.


Out of scope

No change to the matching/relevance logic itself (CR-2026-137, already shipped). No change to View source.