Siddhant Khare shipped a KV-cache truth auditor in LLMTraceFX. It checks engine attestations against an independent token oracle. It also checks observed prompt work, output identity, evaluator correctness and a hash-bound bundle. The demo ran ten cases with token-identical outputs and passing evaluators. Exact duplicates reused eight of nine tokens. Interior mutations cut safe reuse to three of nine tokens. Namespace isolation forced zero reuse. Capacity revisits returned an evicted verdict. The auditor proved a cache hit does not always mean work was skipped. The public snapshot and verification command are committed in the repository.
What it unlocks
Verifying whether a cache hit actually skipped prompt work for a given token prefix.
- 10 test cases passed
- 4,749 local tests passed
- 91 evidence-catalog tests passed
- 9 tokens per request
What you need to act on it
- a deterministic synthetic token-level control
- LLMTraceFX PR #74 merged
Sources