TheREZOR/TinyDecide

The smallest Jev-style decision model.
It runs anywhere and punches far above its size.

Try it in your browser · Watch · Quick start · Python, Rust, ESP32 · Benchmarks

TinyDecide reads one message and answers any number of questions about it. You write the questions in plain English when you call it. It returns a probability for every answer and does not generate text, so one encoder pass answers every question at once.

The model fits the 8 MB flash of an ESP32-S3 without PSRAM, such as the M5Stack Cardputer. This repo has engines for JavaScript in the browser and Node, Python, Rust and the ESP32-S3.

Watch

A 48-second promo with sound. Every answer in it comes from the 4-bit build in this repo. Its Decision Index numbers are self-scored, as Benchmarks explains. If the player does not load, download the video.

Use cases

• Send a voice or chat command to the right app or skill.
• Sort an inbox by spam, urgency and kind of message.
• Pull a time, an amount, a name or a place out of a message.
• Rate tone, priority or sentiment on a scale you define.
• Run offline, with no server and no API key.

Benchmarks

The Decision Index scores typed decision models on 38 public benchmarks. Against the 2026-09-28 board, the 10.4M build would rank first among entries under 100M parameters. It is self-scored and not a listed entry. The board's leaders are 26B to 31B models that score around 57, so this is a result for the small class.

Try it

Open the playground. It runs this exact model in your browser, so your messages stay on your machine. Type a message, edit the questions, and watch every answer update.

Quick start

You need Node 22 or newer. The engine is one JavaScript file with no dependencies.

hf download TheREZOR/TinyDecide --local-dir tinydecide --exclude "assets/*"
cd tinydecide
node example.mjs

import { readFileSync } from "node:fs";
import { TinyDecide } from "./tinydecide.js";

const meta = JSON.parse(readFileSync("meta.json", "utf8"));
const bin = readFileSync("model.bin");
const model = new TinyDecide(meta, bin.buffer.slice(bin.byteOffset, bin.byteOffset + bin.byteLength));

const { answers } = model.answer({
  state: "Book a table for 4 at an Italian place near the station on Friday at 7:30",
  questions: [
    { type: "choice", text: "Which app should handle this?", options: ["reminders", "music", "calendar", "restaurants", "weather"] },
    { type: "noul", text: "The message is urgent." },
    { type: "score", text: "How positive is the tone?", options: ["negative", "neutral", "positive"] },
    { type: "span", text: "Extract the time." },
  ],
});

In a browser, load() from load.js fetches the two files from this repo, or from any URL you pass, and returns the model.

import { load } from "./load.js";
const model = await load();   // https://huggingface.co/TheREZOR/TinyDecide/resolve/main/

Python, Rust and ESP32

Four engines run the same model files. conformance/ holds the JavaScript engine's outputs for 288 tokenizer strings in many scripts and for 84 requests. The requests cover all four question types, several questions per request, corrections and bad input. Each engine's test compares its own outputs with these.

Python. Install it with pip install ./python from the downloaded repo.

from tinydecide import TinyDecide

model = TinyDecide.load(".")            # or TinyDecide.from_pretrained() with huggingface_hub
r = model.answer("Book a table for 4 at an Italian place near the station on Friday at 7:30", [
    {"type": "choice", "text": "Which app should handle this?", "options": ["reminders", "music", "calendar", "restaurants", "weather"]},
    {"type": "span", "text": "Extract the time."},
])
print(r["answers"][0]["pick"], r["answers"][1]["text"])   # 3 7:30

Rust. Add it as a path dependency, tinydecide = { path = "rust" }.

use tinydecide::{Question, TinyDecide};

let model = TinyDecide::load(".")?;      // the folder with meta.json and model.bin
let r = model.answer(
    "Book a table for 4 at an Italian place near the station on Friday at 7:30",
    &[
        Question::choice("Which app should handle this?", &["reminders", "music", "calendar", "restaurants", "weather"]),
        Question::span("Extract the time."),
    ],
)?;
println!("{:?} {:?}", r.answers[0].pick, r.answers[1].text);   // Some(3) Some("7:30")

ESP32. esp32/tinydecide is an ESP-IDF component and an Arduino library.

#include "tinydecide.h"

td::initEmbedded();                       // ESP-IDF embeds model.bin in the app; Arduino uses td::initPartition()
const char* apps[] = {"reminders", "music", "calendar", "restaurants", "weather"};
const td::Question qs[] = {
    {td::CHOICE, "Which app should handle this?", apps, 5},
    {td::SPAN, "Extract the time."},
};
static td::Answer a[2];
const char* msg = "Book a table for 4 at an Italian place near the station on Friday at 7:30";
td::answer(msg, qs, 2, a);                // a[0].pick == 3, msg[a[1].start, a[1].end) == "7:30"

On the ESP32-S3, the PIE vector unit runs the 4-bit matmuls on both cores. On an M5Stack Cardputer the quick-start request takes 1.1 s. It has four questions and 67 tokens, and the answers match the table above. That timing comes from the ESP-IDF project in esp32/examples/basic. The Arduino sketch in esp32/tinydecide/examples/Basic builds, but it has not run on a device yet. Each folder's README has the details.

Files

How it was built

• The backbone is ELECTRA-small, with 12 layers and width 256. This build cuts the feed-forward blocks from 1,024 to 768 units and keeps the 16,000 most used tokens of the vocabulary. It keeps every single character, so any word still splits into known pieces.
• Each question attends to the message but not to the other questions. Asking a question alone or with ten others gives the same answer.
• The training data has public labelled tasks without any benchmark train splits, about 62,000 real messages that Qwen3.6-35B-A3B labelled, and programmatic checks for numbers, times and contact details.
• The 10.4M build learned to imitate an ensemble of two full-size models.
• The losses are proper scoring rules. A held-out split sets one temperature per answer type.

Held-out results (10.4M build)

Calibration error (ECE) is 0.02 to 0.15 on the tiers with true labels.

Limits

• English only.
• Every engine reads the first 127 tokens of a message and sets truncated when it cuts.
• It answers best on short, everyday messages. Questions that need two-step reasoning, such as natural language inference, are close to chance.
• On a Cardputer the quick-start request takes 1.1 s on both cores. Pocket Notes asks one choice question about a short note and takes about 1.8 s with its own, older kernels. A request needs about 2.2 KB of heap per token. The bare ESP32 example has 371 KB free, enough for about 150 tokens. An app with a display and Wi-Fi has less.
• The Decision Index numbers are self-scored with the kit. The board's maintainers have not verified them.
• The 13.8M build's 6.31 is not a clean out-of-sample number. It had two board runs, and one data change came after the first run. The 10.4M build's 5.77 came from a single run.

Made by REZOR. Apache 2.0.