v0.17.0 — thread-aware retrieval, reachable event time, convergent replication
v0.17.0 — thread-aware retrieval, reachable event time, convergent replication
32 commits since v0.16.0 (385de30 → 74066e1). Schema v47 → v50 (lazy migration; verified on a live 5,968-row v46 store).
Retrieval: retrieve wide, then compress
recall_thread— coverage-first entity-thread retrieval (#188)recall_thread_v2+ persistedsource_turn(schema v50) — every record carries its canonical source turn;record_queuedcomputes it through the same extractor asrecord(#195)resolve_thread_topics— adaptive topic budget for thread recall, floor 12 / cap 16 (#197)select_thread_evidence— relevance-ranked selection under a budget with chronological presentation and recomputableselectiondiagnostics; typedThreadSelectionPolicyInfeasibleinstead of silent truncation (#199)
Event time becomes reachable
- v48 columns + census:
event_time_min/event_time_maxpersisted and countable (#149 phase 1, #170) recallgains a valid-time filter — filter-first, per contract (#149 phase 2, #173)
Facets (opt-in lane on the synthesis substrate)
- Standing-instruction facets — opt-in; measured +0.875 on the standing-instruction category in the AMB harness, no default behavior change (#169)
- Facets expose first mention turn (#187)
Correctness fixes users should have
- Replication:
relateLWW now compares HLC, not wall-clockcreated_at(#148, #168) - Replication: relation LWW projections stay convergent across peers (#171)
- Hawkes: order preserved for late-arriving events (#153)
- Migrations: the statement splitter must not cut trigger bodies (#146, #160)
- Organizer: conservative count sets route to items (#158)
- Paired bootstrap seed separated (#180)
Engine internals
- Persisted Unicode-normalized entity key (schema v49) — perf (#190)
- Manual SAVEPOINT sites migrated to
SavepointGuard(#154)
Benchmarks & docs (no runtime effect)
- AMB preregistrations, audits and loss-funnel classification (#151, #155–#157, #159, #172, #174–#179, #185, #186, #189, #191)
- Edge conflict detection placement explained (#198 — contributor: FaarisK)
Compatibility
- Additive schema (v47→v50), lazy migration on first use; no API removals.
yantrikdb-hermes-pluginpins<0.16.0; admitting 0.17.0 there is a separate, gated plugin release.