Documentation
A read only subscriber to each engine's KV cache event socket, and the contract that governs what it emits. Everything here is readable before anything is installed.
Nothing on this page assumes you have decided anything. Read the two that apply to you and ignore the rest.
What it measures
Start here. The two numbers, why a miss gets labelled, what comes attached to every figure, and the three places you can read one, including metrics you can scrape into your own Prometheus.
Trust
The security review page. What leaves the process, what it can reach, the resource envelope, and how to verify each claim yourself.
Deployment
How the binary is vended and verified offline, what the engine must publish, the two supported deployment shapes, running under an orchestrator, and provisioning the key.
Operations
Runbooks. Upgrades, diagnostics, backup and restore verification, retention, and key rotation.
The contract
KV cache event semantics: every record, every field, and what a reader is entitled to conclude from them, with the conformance corpora beside it. Public, Apache 2.0, and hosted where it is authored rather than copied here.
Start here
If you are working out what you would actually get, read What it measures first. It is the two numbers, what comes attached to each one, and the three places you can read them.
If you are reviewing this for security, read Trust,
then run infertap --show-payload, which prints every record the process can emit
with no engine required. The
record
format section of the contract is the complete field enumeration.
If you want to know what running it involves, read Deployment. The engine side is one configuration flag and no fork. The binary itself is vended rather than downloaded, and that page says so first.