mchl-labs presents ChronoVec as a versioned vector index for changing data, potentially letting retrieval systems track source revisions rather than maintain only a current vector index.
state: seedheat: lowuncertainty: highknownscott: lowrag vector-databases data-versioningmchl-labs
What is this?
The supplied case identifies mchl-labs as presenting ChronoVec in a Show HN post as “a versioned vector index for data that changes.” This suggests revision-aware retrieval, but none of the supplied web results directly documents ChronoVec or establishes its implementation, historical-query support, or release status. The web answer’s claims about active-chunk storage and model-upgrade pipelines are not substantiated for ChronoVec by the snippets; those details appear in results about other systems and general indexing practices.
Why it matters to Scott
The revision-preservation premise is already held in Scott’s Cognitive Provenance page, and it touches the change-aware indexing in search — semantic code and Claude-history finder; no supplied radar hit tracks ChronoVec itself. However, the title-level claim establishes neither exact knowledge-path replay nor usable historical retrieval, so it currently adds a possible tooling lead rather than a demonstrated extension or challenge to what Scott builds.
ip:concept.cognitive-provenancedev:project.searchradar:concept.rag
queries asked of Scott's wikis
- RAG source revision tracking and retrieval provenance
- Temporal retrieval and historical knowledge snapshots
- Agent memory and wiki revision history
- Incremental indexing source synchronization and stale embeddings
- Embedding model upgrades and reproducible retrieval
Measured heat
now 0 pts/hpeak 0 pts/hcomments 0/hpeers p14momentum: steady2 platformsage 794h
points/hour across evidence · reading as of 2026-10-12 02:59:37.977291+11:00 · deterministic, not a model opinion
How the heat travelled
pace: p47 vs 519 stories at the 720h mark (now 794h old) — ahead of api-delta-manifest (1.2x), behind lightpanda-session-bridge (0.9x)
Evidence (5) — ⭐ canonical anchor
Interpretation history
2026-09-17T17:51:06Z
The new Postgres graph-RAG posts are further announcements from the same adjacent project's maker, not independent corroboration of ChronoVec. Their fact-retirement and bi-temporal claims do not establish ChronoVec's revision-preservation or historical-query capabilities, leaving its practical implications unchanged.
2026-09-17T17:26:01Z
evidence attached: hn.story.49743692 — Independent corroboration for version-aware retrieval, adding graph and bi-temporal handling to the existing changing-data indexing case.
2026-09-17T17:26:01Z
evidence attached: hn.story.49743385 — shared external link with case evidence
2026-09-10T15:55:59Z
The Post-graph-RAG announcement adds an adjacent stale-fact retrieval lead, not independent evidence that ChronoVec supports source revisions or historical queries. ChronoVec remains a maker-announced tooling prospect with no demonstrated implications for Scott’s retrieval or provenance architecture.
2026-09-10T15:26:00Z
evidence attached: hn.story.49645202 — A concrete RAG artifact focused on changing facts materially contextualizes version-aware retrieval and stale knowledge handling.
2026-09-08T14:37:34Z
No substantive evidence has arrived to move ChronoVec beyond a maker-announced tooling lead; the GitHub echo repeats the same claim rather than independently corroborating it. Historical-query semantics and usable revision-aware retrieval remain unestablished, so its implications for Scott’s systems are unchanged.
2026-09-08T14:31:19Z
grounded: known/low — The revision-preservation premise is already held in Scott’s Cognitive Provenance page, and it touches the change-aware indexing in search — semantic code and C
2026-09-08T14:29:03Z
case created — The named repository supplies a bounded retrieval-infrastructure artifact distinct from existing memory and embedding-migration cases.
Decision trace
- 10-09 03:05review_dormant28 days without material information; scheduled checks stopped
- 10-01 22:01drop_targetsquiet through full ladder or over cap 8
- 09-18 03:51repriceThe new Postgres graph-RAG posts are further announcements from the same adjacent project's maker, not independent corroboration of ChronoVec. Their fact-retirement and bi-temporal claims do not
- 09-18 03:26attachIndependent corroboration for version-aware retrieval, adding graph and bi-temporal handling to the existing changing-data indexing case.
- 09-18 03:26attachshared external link with case evidence
- 09-18 03:25propose_attachIndependent corroboration for version-aware retrieval, adding graph and bi-temporal handling to the existing changing-data indexing case.
- 09-18 03:22propose_attachshared external link with case evidence
- 09-12 00:30review_screenThe maker’s comment reiterates the existing premise that ChronoVec targets changing data, corrections, and erasure, but provides no independent implementation result or evidence of historical queries
- 09-11 01:55repriceThe Post-graph-RAG announcement adds an adjacent stale-fact retrieval lead, not independent evidence that ChronoVec supports source revisions or historical queries. ChronoVec remains a maker-announced
- 09-11 01:55alert_silentThe new announcement establishes another builder’s interest in stale retrieval facts, but supplies no mechanism, results, or ChronoVec-specific advance that changes Scott’s decisions today. Routine re
- 09-11 01:55alert_routeThe new announcement establishes another builder’s interest in stale retrieval facts, but supplies no mechanism, results, or ChronoVec-specific advance that changes Scott’s decisions today. Routine re
- 09-11 01:27alert_silentPost-graph-RAG is a separate Show HN tooling announcement targeting stale facts in retrieval, not a demonstrated ChronoVec advance. The announcement is visible, but the supplied title and repository l
- 09-11 01:27alert_routePost-graph-RAG is a separate Show HN tooling announcement targeting stale facts in retrieval, not a demonstrated ChronoVec advance. The announcement is visible, but the supplied title and repository l
- 09-11 01:26attachA concrete RAG artifact focused on changing facts materially contextualizes version-aware retrieval and stale knowledge handling.
- 09-11 01:25propose_attachA concrete RAG artifact focused on changing facts materially contextualizes version-aware retrieval and stale knowledge handling.
- 09-09 00:37repriceNo substantive evidence has arrived to move ChronoVec beyond a maker-announced tooling lead; the GitHub echo repeats the same claim rather than independently corroborating it. Historical-query semanti
- 09-09 00:37alert_silentThe introduction is established, but this reevaluation contains no new release, implementation detail, or demonstrated capability that changes Scott’s engineering choices. It can wait for routine revi
- 09-09 00:37alert_routeThe introduction is established, but this reevaluation contains no new release, implementation detail, or demonstrated capability that changes Scott’s engineering choices. It can wait for routine revi
- 09-09 00:36alert_silentThe maker’s Show HN establishes ChronoVec’s introduction as a versioned vector index, but the supplied evidence adds no implementation details, retrieval semantics, or concrete advantage that would ch
- 09-09 00:36alert_routeThe maker’s Show HN establishes ChronoVec’s introduction as a versioned vector index, but the supplied evidence adds no implementation details, retrieval semantics, or concrete advantage that would ch
- 09-09 00:31groundThe revision-preservation premise is already held in Scott’s Cognitive Provenance page, and it touches the change-aware indexing in search — semantic code and Claude-history finder; no supplied radar
- 09-09 00:29createThe named repository supplies a bounded retrieval-infrastructure artifact distinct from existing memory and embedding-migration cases.