Instructions to use hiteshluke/arbiter-v4-12b with libraries, inference providers, notebooks, and local apps. Follow these links to get started.
- Libraries
- PEFT
How to use hiteshluke/arbiter-v4-12b with PEFT:
from peft import PeftModel from transformers import AutoModelForCausalLM base_model = AutoModelForCausalLM.from_pretrained("google/gemma-4-12b-it") model = PeftModel.from_pretrained(base_model, "hiteshluke/arbiter-v4-12b") - Notebooks
- Google Colab
- Kaggle
- Local Apps Settings
- llama.cpp
How to use hiteshluke/arbiter-v4-12b with llama.cpp:
Install (macOS, Linux)
curl -LsSf https://llama.app/install.sh | sh # Start a local OpenAI-compatible server with a web UI: llama serve -hf hiteshluke/arbiter-v4-12b:Q4_K_M # Run inference directly in the terminal: llama cli -hf hiteshluke/arbiter-v4-12b:Q4_K_M
Install from WinGet (Windows)
winget install llama.cpp # Start a local OpenAI-compatible server with a web UI: llama serve -hf hiteshluke/arbiter-v4-12b:Q4_K_M # Run inference directly in the terminal: llama cli -hf hiteshluke/arbiter-v4-12b:Q4_K_M
Build from source code
git clone https://github.com/ggml-org/llama.cpp.git cd llama.cpp cmake -B build cmake --build build -j --target llama-app # Start a local OpenAI-compatible server with a web UI: ./build/bin/llama serve -hf hiteshluke/arbiter-v4-12b:Q4_K_M # Run inference directly in the terminal: ./build/bin/llama cli -hf hiteshluke/arbiter-v4-12b:Q4_K_M
Use Docker
docker model run hf.co/hiteshluke/arbiter-v4-12b:Q4_K_M
- Llama new
- LM Studio
- Jan
- Ollama
How to use hiteshluke/arbiter-v4-12b with Ollama:
ollama run hf.co/hiteshluke/arbiter-v4-12b:Q4_K_M
- Unsloth Desktop
- Pi
How to use hiteshluke/arbiter-v4-12b with Pi:
Start the llama.cpp server
# Install llama.cpp: brew install llama.cpp # Start a local OpenAI-compatible server: llama serve -hf hiteshluke/arbiter-v4-12b:Q4_K_M
Configure the model in Pi
# Install Pi: npm install -g @earendil-works/pi-coding-agent # Add to ~/.pi/agent/models.json: { "providers": { "llama-cpp": { "baseUrl": "http://localhost:8080/v1", "api": "openai-completions", "apiKey": "none", "models": [ { "id": "hiteshluke/arbiter-v4-12b:Q4_K_M" } ] } } }Run Pi
# Start Pi in your project directory: pi
- Docker Model Runner
How to use hiteshluke/arbiter-v4-12b with Docker Model Runner:
docker model run hf.co/hiteshluke/arbiter-v4-12b:Q4_K_M
- Lemonade
How to use hiteshluke/arbiter-v4-12b with Lemonade:
Pull the model
# Download Lemonade from https://lemonade-server.ai/ lemonade pull hiteshluke/arbiter-v4-12b:Q4_K_M
Run and chat with the model
lemonade run user.arbiter-v4-12b-Q4_K_M
List all available models
lemonade list
- Hermes Agent
How to use hiteshluke/arbiter-v4-12b with Hermes Agent:
Start the llama.cpp server
# Install llama.cpp: brew install llama.cpp # Start a local OpenAI-compatible server: llama serve -hf hiteshluke/arbiter-v4-12b:Q4_K_M
Configure Hermes
# Install Hermes: curl -fsSL https://hermes-agent.nousresearch.com/install.sh | bash hermes setup # Point Hermes at the local server: hermes config set model.provider custom hermes config set model.base_url http://127.0.0.1:8080/v1 hermes config set model.default hiteshluke/arbiter-v4-12b:Q4_K_M
Run Hermes
hermes
- Atomic Chat
- OpenClaw
How to use hiteshluke/arbiter-v4-12b with OpenClaw:
Start the llama.cpp server
# Install llama.cpp: brew install llama.cpp # Start a local OpenAI-compatible server: llama serve -hf hiteshluke/arbiter-v4-12b:Q4_K_M
Configure OpenClaw
# Install OpenClaw: npm install -g openclaw@latest # Register the local server and set it as the default model: openclaw onboard --non-interactive --mode local \ --auth-choice custom-api-key \ --custom-base-url http://127.0.0.1:8080/v1 \ --custom-model-id "hiteshluke/arbiter-v4-12b:Q4_K_M" \ --custom-provider-id llama-cpp \ --custom-compatibility openai \ --custom-text-input \ --accept-risk \ --skip-health
Run OpenClaw
openclaw agent --local --agent main --message "Hello from Hugging Face"
Arbiter v4 Β· 12B
A typed-decision model by Codekins Β· Zyot Lab. Arbiter answers the way software needs it β yes/no, multiple-choice, and ordinal ratings β from a single calibrated forward pass, not free text. It is Gemma-4 12B IT + LoRA (r 32, Ξ± 64) with a fixed 28-slot decision head read at the last token.
One model, three decision types. No sampling, no parsing β a probability over the valid options, every time.
Benchmarks
| Benchmark | Score | Notes |
|---|---|---|
| BoolQ (validation, 3,270) | 89.2% | Near-human (~90%) boolean reasoning; majority-class baseline is 62.2% |
| Ollaya typed-decisions | 0.640 | Head-scored on ollaya.dev; the metric reads the head's probabilities directly (no text generation) |
| β³ Yes / No (noul) | 0.803 | True/false + "unanswerable" detection β Arbiter's strength |
| β³ Multiple-choice | 0.663 | pick-one decisions |
| β³ Ordinal score | 0.501 | fine-grained ratings β an industry-wide ceiling (gold labels have ~0.61 annotator agreement) |
Why this is strong. BoolQ at 89.2% puts a compact classifier head within a point of human performance
and of much larger frontier models β confirming the boolean/answerable judgment that also shows as 0.803 on
Ollaya's noul type. The ordinal score type is weak for every model on the board because its gold labels
are noisy by construction; Arbiter leads where the signal is clean.
What makes it different
- Explicit typed decision head. Most models read a decision off next-token logits; Arbiter has a trained
28-slot head (
T/FΒ·Aβ¦PΒ·0β¦9) over the final hidden state β boolean, choice, and ordinal in one place. - Calibrated & deterministic. A fitted temperature; one forward pass; the same answer every time. No sampling, no "please output JSON", no parse failures.
- Compact to deploy. The decision is a classifier, not a generation loop.
How it answers
| Slots | Tokens | Used for |
|---|---|---|
| 0, 1 | T, F |
yes/no β option logits [F, T] |
| 2β¦17 | Aβ¦P |
choice β up to 16 options |
| 18β¦27 | 0β¦9 |
score β up to 10 ordinal levels |
The prompt is State: β¦ / Question: β¦ / Options: β¦ / Answer:; the head is read at the last position. One
causal row answers one question.
Files
adapter_model.safetensorsβ the LoRA adapter (on q/k/v/o and gate/up/down), F32head.ptβ the 28-slot decision head (nn.Linear(3840, 28, bias=False), BF16)head_meta.jsonβ verbalizer + calibration temperature
Load the base google/gemma-4-12b-it, attach the adapter, and read the head over the last-token hidden state.
On Ollaya
Arbiter's 4B predecessor is live on ollaya.dev as the arbiter family; the 12B
is being added as arbiter12b (a 28-slot head). Ollaya scores decision models by reading the head directly, so
the leaderboard number reflects the real classifier β not a generated string.
Citation
Arbiter v4 (12B) Β· Codekins Pvt Ltd Β· Zyot Lab. Base model: Gemma-4 12B IT (Β© Google, Gemma license).
- Downloads last month
- 49
4-bit
8-bit