jevcache

What it is

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

The homepage listed on the repository, jevcache.sh, puts it like this: Jev returns a typed decision in milliseconds. jevcache memoizes it by (model, schema, state) so the same decision never runs — or bills — twice. Repeats are free, deterministic, and shareable.

Getting started

From the README:

curl -fsSL jevcache.sh/install | sh

Where the decision sits

jevcache calls the hosted decision API rather than running its own weights. That keeps the project small and means its behaviour moves whenever the vendor ships a new model version. It also means an API key and a network round trip sit in the path of every decision.

Models it references: Jev.

How active it is

Created 2026-09-18, last pushed 2026-09-19, 78 stars and 3 forks when we read it on 2026-11-02. Everything in this category is weeks old at most, so a stale push date means something different here than it would on a mature project. Check the repository before you depend on it.