Snapshots
Snapshot stamps make reads reproducible — pin a point in time and the same query returns the same chunks.
Every retrieval and answer response carries a snapshotId and a
policyBundleRevision. A snapshot encodes
(pipeline_version, log_offset, index_build_id) — pinning it makes a read
reproducible: the same query returns the same chunks, even as new data lands.
v0 status
This endpoint is a stub in v0. Snapshots are per-tenant sequence stamps;
the eval plane and the durable append-only log own the full lifecycle
(see docs/ARCHITECTURE §2.3). The response documents that explicitly.
Response
{
"note": "v0 stub — snapshots are per-tenant sequence stamps; the eval plane and the durable log own the full lifecycle (docs/ARCHITECTURE §2.3)."
}What is (and isn't) pinnable
| Pinnable | Not pinnable |
|---|---|
| Knowledge (chunks, embeddings, the index build) | Policy bundles |
| The log offset a read observed | ACL grants and revocations |
Pinning knowledge lets an eval replay a fixed corpus. Policy and ACLs are never pinned — a revoked grant must take effect immediately, so it is always evaluated live against the current bundle.
Unauthenticated liveness + capability probe. Handy for readiness checks and for seeing which providers are wired.
{
"ok": true,
"embedder": "mock",
"generator": "mock",
"capabilities": { "hybrid": true, "knn": "post-filter" }
}