REPOSITORY ANALYSIS

kev

Tiny Jev-like decision head built atop Qwen2.5-0.5B that can be trained and run locally on Apple Silicon MacBooks.

E2 · source reviewedPublic material or source evidence was reviewed. A fixed-version source review requires checking a pinned revision; this is not a reproduction, performance endorsement, or safety guarantee.
Stars
6,183
Forks
339
License
Apache-2.0
Last commit
2026-09-24

What Jev does here

Attaches a parallel decision head to an open 0.5B model to answer discrete questions directly from token activations.

Provides a small local decision-model architecture and probes for packed-versus-separate questions, option order and calibration. Hosted teacher calls for data collection remain a separate network and cost dependency.

The pinned README and hosted-teacher adapter were read. This site did not train the student or reproduce its calibration figures. Local inference capability does not mean every data-generation step is offline or free.

What task does this project fit?

Explore a small local decision-head architecture and its training/evaluation workflow.

Material analysed:

From input to action

  1. Encode state and typed questions with a Qwen2.5-0.5B backbone.
  2. Isolate question branches with a block-causal mask.
  3. Score candidate readouts and serve the System One-shaped response.

Implementation details that matter

Question isolation is an architectural claim with a checkable design

The README describes each question seeing the document but not sibling questions. Packed-versus-separate equivalence should be checked independently from task accuracy.

Inspect the supporting source ↗

The hosted teacher is a separate dependency

kev/jev.py wraps a Vercel Gateway Jev call for teacher data and token accounting. Local student inference does not mean every training-data operation is offline or free.

Inspect the supporting source ↗

When to choose it

Useful for learning and adapting a small decision model when local deployment matters. Compare a trained checkpoint on your own held-out questions before treating API compatibility as quality parity.

How to inspect it yourself

Inspect the README's packed/separate and permutation probes, then read kev/jev.py for hosted credentials and token usage before running data-generation steps.

Limits of this review

  • No training, checkpoint inference or published calibration number was reproduced here.
  • A compatible response shape does not establish equal generalization to hosted Jev.
Primary material used in this analysis