HunterAlphaHub
OpenRouter model reference Facts from the public catalogue, dated and labelled

GitHub ·

Rizzo-AI-Academy/rizzo-flow

Keeping decisions on your own hardware without rewriting the client.

The repository's GitHub card, read on 2026-09-27

What it does

Stands up a local service that takes unstructured state and returns typed probabilistic decisions — a yes/no, a choice among options, a score on a rubric — using open weights instead of a hosted API, and speaks the same /v1/systemone request shape as TypeSafe's own endpoint so a client changes only its base URL.

The repository's own description: “The open, local take on Jev: typed decisions from an LLM, without generating a single token”

How it works

The project wraps open chat models and constrains them to answer with probabilities in a single pass rather than generating text; a local server exposes the Jev-compatible route. Its results table is measured on the public typed-decisions test split, which is what makes it comparable at all.

The repository, by the numbers

Stars
626
Forks
37
Language
Python
Last push
2026-09-25

Read from the GitHub API on 2026-09-27. Stars and the last push move daily — quote them with the date, the way we do.

What we checked

  • the README's compatibility claim and the model names it lists
  • the licence (Apache-2.0) and the linked documentation
  • the results table and the dataset it names (LocalLLaMA/typed-decisions)

What we did not check. We did not install it, so whether a real TypeSafe client works unmodified against this server is the author's statement rather than something we tested, and the accuracy rows are the authors' measurements.

Open the repository ↗All builds

Send us a link

A project built with Jev, a post, a video, a correction, a tip. We open the link, check it says what you said it says, and write the entry ourselves.

Required a link, and an email to reply to. Optional everything else.

Add context — all optional

One or two sentences about what it does, in your words. We write the entry ourselves.

Cost, latency, a benchmark — anything you measured. We attribute these to you.

We store what you type and email it to ourselves. No IP address, no user agent, no referrer — the same rule as the mailing list.

What happens to what you send →