session 2026-08-24 addendum 2: trial IS running on multilingual-e5-small — prior addendum corrected

The plugin's progress panel confirms 'Using Xenova/multilingual-e5-small for embeddings'
(336/48233, 1729 tok/sec). Addendum 1 reported the opposite from smart_env.json, which
still read bge-micro-v2 in a file written 14s earlier — a persistence artifact with a
debounce, read as live state. Trial clock starts 2026-08-24, grade 2026-10-05.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01JQKeKY9T9d95KpvHwwok8T

claude/memory/knowledge-graph.jsonl

@@ -706,3 +706,5 @@
 {"subject": "deriving a rule from the existing consumer instead of writing a second one", "predicate": "prevention", "object": "CAUGHT A REINTRODUCTION OF THE PREVIOUS DAY'S BUG WITHIN MINUTES. Fixing thread-query.py's archive filter, I wrote startswith('99. archive') — which re-created the exact substring failure that hid 78 live notes on 2026-08-23. The control carried over from that day failed immediately. The fix was not a better private rule but ADOPTING vault-links.py's existing definition (ARCHIVE_DIR = '99. Archive', exact path component), so the vault has one archive rule rather than two that can drift. The banked discipline 'derive the rule from the consumer, not from the survivor' prevented a field-computed-twice defect in a different tool and a different domain.", "valid_from": "2026-08-24", "valid_to": null, "confidence": 0.95, "source_file": "session-2026-08-24-the-heap-got-a-dynamo.md", "extracted_at": "2026-08-24"}
 {"subject": "the daily note practice", "predicate": "diagnosed-as", "object": "A CONTINUOUS OBLIGATION WITH NO RECURRING CUE. Record, not impression: notes for 2026-08-19 through 08-22 do not exist; 2026-08-23 exists at 33,242 bytes across 8 commits, written incrementally as specified. The practice has produced exactly one note — on the day its convention was authored and live in working memory. daybook-ensure.py fires at SessionStart and ONLY EVER CREATES; the next cue is /wrap-up, hours later; between them there is no cue at all. The vault's own notes diagnosed the two dead predecessors correctly ('neither had a trigger') and then built the trigger for the half that never needed one. Compounding factor: competing sinks that DO have cues — the Symmetria ledger was written three times unprompted the same day, because it belongs to an active skill. SKILLS AND HOOKS FIRE; DOCUMENTS DESCRIBE. Remedy built: daybook-cue.py, PostToolUse on Write|Edit, reminder not block.", "valid_from": "2026-08-24", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-24-the-heap-got-a-dynamo.md", "extracted_at": "2026-08-24"}
 {"subject": "/wake-up", "predicate": "reaches", "object": "0.71% of the memory corpus — 6,107 words of 859,803, always the newest, ordered by recency. Measured 2026-08-24. This is the gap thread-query.py exists to close, and the number the six-week trial is graded against.", "valid_from": "2026-08-24", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-24-the-heap-got-a-dynamo.md", "extracted_at": "2026-08-24"}
+{"subject": "claude-code", "predicate": "drift-pattern", "object": "Read a CONFIG FILE as evidence of LIVE STATE, and reported a failure that had not occurred. Smart Connections' smart_env.json still recorded TaylorAI/bge-micro-v2 in a file written 14 seconds before the check; I treated the freshness of the mtime as evidence of currency and told the steward the model change had not taken. The plugin's own progress panel showed it embedding with Xenova/multilingual-e5-small at that moment. A config file is a PERSISTENCE ARTIFACT WITH A DEBOUNCE (re_import_wait_time: 13) — it answers 'what was last written', never 'what is running now'. The running process's own report is the substrate for a liveness question. The banked ladder rule 'verify the RUNNING BINARY's provenance, not source HEAD' is the identical principle in another domain and was not reached for.", "valid_from": "2026-08-24", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-24-the-heap-got-a-dynamo.md", "extracted_at": "2026-08-24"}
+{"subject": "stating both possibilities instead of picking one", "predicate": "prevention", "object": "LIMITED A WRONG REPORT TO A SINGLE-DIRECTION CORRECTION. When smart_env.json disagreed with the steward's action, the report said explicitly 'that may simply be Obsidian not having flushed yet... this is the disk not having caught up, not it failed again — I cannot tell which from here, and I would rather say so than pick one.' The benign branch turned out correct. Because the uncertainty was declared rather than resolved by guess, the steward was not sent to undo work that was already right, and the record needed amending in one direction only. Hedging is usually noise; here the hedge was the load-bearing part.", "valid_from": "2026-08-24", "valid_to": null, "confidence": 0.9, "source_file": "session-2026-08-24-the-heap-got-a-dynamo.md", "extracted_at": "2026-08-24"}