Docs / Specification

contract store · 10-store.md · 11-snapshot.md · 12-time.md · 13-replica.md · 14-drain.md · 15-endpoint.md · 16-collect.md · 17-merge.md · 18-pull.md · guide · card

Snapshot corpora

A snapshot corpus stores copies of external documents, landed through the ordinary write path, for local ranking under local-rankread.horizon.local-rankUnder a horizon, corpus.retrieve ranks stored rows through local indexes; search sources read their pinned capture corpus. Live search reaches no host through egress-hook..

snapshot

Document capture records, snapshot identifiers for evaluation cases and access to documents captured after the reading horizon.

• capturetest[pipeline.tables.snapshot] declares SnapshotDecl, the columns describing each captured document. Each capture commits as one store snapshot, and an evaluation case pins it by snapshot id.
  Why

  A-store#snapshot-corpus-declared
• post-horizon-capturetestA document captured after the reading horizon carries _available_reconstructed true under live-sincestore.available-time.live-sinceA date-typed availability value resolves at landing to the start of the next day in the declared zone; rows available before available_time.live_since, when the source began publishing live, get injected _available_reconstructed true., and a horizon read admits it only while the block’s leak_score column holds 0.
  Why

  A-store#snapshot-corpus-declared

Scenarios

• store.snapshot.post-horizon-capturestore.snapshot.post-horizon-captureA document captured after the reading horizon carries _available_reconstructed true under live-since, and a horizon read admits it only while the block's leak_score column holds 0.: WHEN a pipeline captures a page published 2014-03-02 on 2019-06-10 and a reader requests horizon 2014-05-01, THEN the row carries _available_reconstructed true and appears only while its leak_score is 0.