jevcache

The README opens with

The decision ledger for Jev-class models. A Jev decision is (approximately) a pure function of (model, schema, state) — so it's memoizable. jevcache caches those decisions locally: same decisions, fewer bills, and deterministic replay in CI. It's backend-agnostic — point it at any local decision endpoint, a hosted Jev provider, or a mock — and it never proxies or resells inference (your key stays on your machine).

- Local-first & offline. An embedded, zero-dependency store (in-memory map + append-only log). A point lookup is a map access — instant. - Private by construction. State is redacted and canonicalized before it's hashed, so the fingerprint is over decision-relevant content only; PII (emails, phones, long digit runs) and volatile fields...