Provenance Record

Well-structured News piece (614 words, within the 400-1200 News range). Clean Overview / What We Know / What We Don't Know format. Technical depth is appropriate and the GA-vs-preview distinction is handled carefully and accurately throughout.

All 5 source snapshots read from disk and verified (no archive fallback; all HTTP 200). source-0 (GitHub release v1.38.0): confirms 'HFresh (GA)', the verbatim quote 'numerous performance optimizations reducing memory usage, disk writes, and allocations', 'Breaking Changes: none', and that Namespaces / Nested Object Filtering / Alter Schema Reindex / Secure MCP Server are each labeled '(Preview)' — exactly as the article states; the MCP quote 'allows AI agents (such as Claude, IDEs, etc.) to natively read and write to Weaviate without requiring custom code' is verbatim; the GitHub page header also shows 'released this 05 Jun', corroborating the June 5 date independently of Elestio. source-1 (Weaviate 1.36 blog): confirms 'March 3, 2026', 'HFresh (Preview)'/'technical preview', and the disk-index quotes; one minor deviation noted below. source-2 (docs vector-index): confirms 'cluster-based vector index based on the SPFresh algorithm', 'uses an HNSW index for centroid search, providing a balance between memory efficiency and search performance', the four index types (HNSW/Flat/Dynamic/HFresh), the dynamic-index threshold behavior, and 'Added in v1.36' (all verbatim/accurate). source-3 (arXiv 2410.14452): the abstract quote 'provides superior query latency and accuracy to solutions based on global rebuild, with only 1% of DRAM and less than 10% cores needed at the peak compared to the state-of-the-art, in a billion scale vector index with 1% of daily vector update rate' is verbatim, and the paper title matches; the SPFresh-specific claim is correctly cited to the arXiv primary (Rule 9). source-4 (Elestio): confirms 'Weaviate 1.38.0 (June 5)' and the feature list.

DATE CHECK PASSED: the article uses June 5 (and 'early June'), which is corroborated by both Elestio ('June 5') and the GitHub release page itself ('05 Jun'). No source contains '2024' — the feared GitHub-fetcher year misread did NOT propagate into the article; no fabricated date is present (Rule 2 satisfied). GA-vs-PREVIEW LABELING PASSED: HFresh is correctly described as preview in 1.36 -> GA in 1.38, and namespaces, nested object filtering, schema reindexing, and the MCP server are all correctly labeled as previews, matching the release notes exactly. No claim rests on a bot-blocked source (Phoronix 403 was correctly excluded and is not among the sources).

Accurate, well-sourced, neutral News piece. The critical risk areas (release date and GA-vs-preview feature labeling) are both correct and independently corroborated. The only blemish is a single dropped word inside one quote, which is honestly recoverable via a corrections note. Verdict: APPROVE_WITH_CORRECTIONS.