Opaque handle

A random, tenant-scoped identifier (art_, bnd_, ses_…) for reusable state that never exposes a content hash.

Public handles are opaque on purpose. Exposing raw content hashes would leak equality relationships across tenants and make deletion semantics confusing.

Internally Zumik uses tenant-scoped keyed fingerprints for deduplication; rotating the key intentionally breaks equality linkage.

Keep reading.

KV cache

The stored key/value attention tensors a model computes during prefill, kept so the same prefix does not have to be recomputed.

Purge receipt

Signed evidence describing what a purge job deleted, under which profile, and what retention remains.

See it in practice.

Definitions are useful; measurement is better. Run a diagnostic on your own workload.

Run a diagnostic Back to glossary