jevbooks

← All projects

chakuho

taku-me/chakuho

Jev-compatible System One decision endpoint over a local LLM.

Agent Decisions0.90Runner-up: Infra / SDKs / IntegrationsQuestionnaireFlight recorderCheck-up
Automated README summary

Automatically summarized from the README on 20 Oct 2026; not a run by jevbooks. Run instructions and author-reported outcomes still need verification.

What it is

chakuho is a Python HTTP server that answers typed decision questions (choice, noul/boolean, score) by reading a local OpenAI-compatible LLM's next-token distribution, returning calibrated probabilities instead of generated text. It targets developers who want Jev-style System One decisions using an already-running general instruct model.

How it uses Jev

The caller declares a state and questions with enumerated options. chakuho labels options A–Z/a–z, builds a prompt ending in "Label:", and either samples n=16 one-token completions (default) or reads one logprobs pass, then aggregates and normalizes probabilities over the declared labels. Results are returned as choice/probabilities, noul probability, or normalized score, with coverage and degraded flags.

Primitives:choicescorenoul

Technique worth stealing

Map enumerated options to single-token labels and read the LLM's next-token distribution, aggregating label mass into a probability distribution.

Try it

uv sync && uv run chakuho serve --port 9750, then POST to /v1/systemone.

View on GitHub

Start using Jev: API key and your first request →

Model judgments from README excerpts

Project signals use repository metadata, an existing summary and the first 700 README characters, not the full project. “Not found” means not detected in that material; it does not establish absence. These are the original judgments with recorded models and dates, not source audits or run results.

Models & evaluation dates

Inclusion gate
jev-1.13.0
Project signals
jev-1.13.0
Category
jev-1.13.0
Pattern tags
jev-1.13.0

Evidence

These signals use repository metadata, an existing summary and at most 700 cleaned README characters. ≥ 0.60 means reported in that excerpt; ≤ 0.40 means not found there. The middle band is inconclusive. None is a source-code audit or a test result. The runnable-tool question excludes research experiments; the recommendation question asks for a learning shortlist, not a quality verdict.

  • Jev is core to the projectFound in material0.91
  • Shows a System One patternunclear0.58
  • Describes handling uncertaintynot found in the excerpt0.05
  • Reports measured numbersnot found in the excerpt0.04
  • Is a runnable toolFound in material0.98
  • Top-10 learning shortlist signalnot found in the excerpt0.28
  • Is a replica of the modelFound in material0.91
  • Solves a common problem (0–2)score on a 0–2 scale1.01 / 2
  • About JevFound in material0.97
Signals
Jev is core to the project0.91Shows a System One pattern0.58Describes handling uncertainty0.05Reports measured numbers0.04Is a runnable tool0.98Top-10 learning shortlist signal0.28Is a replica of the model0.9100.51Solves a common problem (0–2)1.01 / 2012

no-judgment band (0.40–0.60)

Design patterns
Questionnaire0.97Check-up0.93Flight recorder0.77Funnel0.61Menu0.60Inspection0.60Blind review0.39Fail open, fail closed0.26Prefetch0.2400.51

no-judgment band (0.40–0.60)

The Jev model and date for each judgment stage are listed above. Card written by DeepSeek V4.1 Flash from the README on 20 Oct 2026.