decision-head-qwen3.5-4b-rlcd-32k

Decision head for Qwen3.5-4B — RLCD, 32K one-pass

The common read on Jev is that its generalisation comes from the data rather than the training algorithm. This adapter is one arm of an experiment built to test that: base, algorithm and hyperparameters held fixed, three seeds, held-out sets grouped by their relationship to the training data. The answer is in the transfer table below — coverage predicts generalisation in both directions, and where coverage is missing, RL lands below the untrained base.

A LoRA adapter that turns Qwen3.5-4B into a typed decision model: one forward pass, no generation, a probability distribution read off the option-letter logits. 4.9M trainable parameters (0.12% of the base), attention projections only — no MLP, no embeddings, no output head. The classification head is not new weights: it reads single-token A–Z logits out of the frozen vocabulary.

Trained with RLCD (Gaussian noise on candidate logits as the action, leave-one-out baseline over 8 samples) on 32,000 items in a single pass. Three seeds were trained; this is seed 1, selected on a held-out 400-item validation split (0.8675 vs 0.8500 and 0.8650) before any test set was consulted. Seed 3 scores higher on JevBench (0.797 vs 0.779) — picking it would have been selection on the test set, so it is reported below but not released as the default.

What it is for

Bounded decisions where the caller supplies the material, the question and the exact option set, and wants a calibrated-ish distribution over those options: request routing, answer-adequacy judging, policy yes/no checks, intent classification, ordinal severity scoring, evidence support.

It does not generate text. It cannot be prompted into free-form answers. Input is capped at 4,096 tokens and is not truncated — a longer input raises rather than silently losing material.

Results

Against the untrained base on the frozen held-out sets:

JevBench v1.2 (external, 231 public items)

JevBench is run by a third party; we did not write its items. Scored with its own harness through an adapter that mirrors semif_direct, the Qwen3.5-4B entrant already on its board, so the two are comparable item for item.

On the easy and standard tiers this ties Jev item for item. The whole remaining gap is the hard tier.

The part worth reading: transfer has a direction

The headline numbers hide a split that three independent evaluations agree on. Grouping held-out tasks by their relationship to the training stream:

Six rows, three seeds, same sign in every cell. RL on a narrow slice of a structure does not merely fail to generalise to other material of that structure — it lands below the untrained starting point. The algorithm never varied, so the variable is the data, and narrow data is a liability rather than a no-op.

Two cells that look more dramatic in one seed are deliberately left out of the table: JevBench multi_hop rises 0.50 → 0.83 and tradeoff falls 0.83 → 0.33 in seed 3 only (seed 1: 0.56 and 0.83). An earlier version of this card showed those seed-3 cells next to seed-2 public-panel cells under a single "after RL" column; that was a cross-seed selection and is corrected here.

Calibration also degrades: Brier 0.342 → 0.378 on JevBench, and expected calibration error rises on the public panel. The model becomes both more accurate and more overconfident.

If you plan to use this on material that does not look like ordinary web/wiki prose, or on decisions that require weighing competing objectives, measure against the untrained base before adopting it.

Known limits

• No ablation arm. This run changed data, reward, base model and learning rate at once. Gains are not attributable to any one of them.
• Adapter capacity is a live confound. rank 8, attention-only, inherited unexamined from a 0.6B prototype. Whether the regressions above come from narrow data or from an adapter too small to hold two strategies is not separable from this run alone.
• One-pass stream, one frozen order. All three seeds share the same data order; seeds vary only LoRA init and RLCD noise, so run-to-run variance is understated.
• Arithmetic and dates are out of reach. JevBench temporal_numeric: base 0.27, after RL 0.13, Jev 0.27. One forward pass with no intermediate computation cannot do this, for anyone.
• Small cells. JevBench long_policy is 19 items, tradeoff 6. The regression below base rests on three sites agreeing across three seeds (pubmedqa, vitaminc, long_policy), not on any one cell. The tradeoff drop, which would speak to "no rule decides" items directly, is seed-dependent and is not part of the claim.

Usage

from peft import PeftModel
from transformers import AutoModelForCausalLM, AutoTokenizer

BASE, REV = "Qwen/Qwen3.5-4B", "851bf6e806efd8d0a36b00ddf55e13ccb7b8cd0a"
tok = AutoTokenizer.from_pretrained(BASE, revision=REV)
model = AutoModelForCausalLM.from_pretrained(BASE, revision=REV, dtype="bfloat16", device_map="cuda")
model = PeftModel.from_pretrained(model, "AstroHan/decision-head-qwen3.5-4b-rlcd-32k").eval()

The prompt format matters: the adapter was trained on one exact template (system instruction, then Material: / Question: / Options: with single-token letter labels, chat template, no thinking). decision.py in the code repository is the reference implementation — reproduce it exactly or the letter logits will not mean what they meant in training.

Training data

32,000 items in a single pass: 29,000 choice, 1,800 ordinal (3/4/5/6 levels), 1,200 boolean, drawn from eight synthetic families plus public datasets.

The mixture is not redistributed. It derives from public datasets under differing licences and from synthetic items generated through commercial APIs. The frozen manifest (SHA-256, per-family proportions, per-domain concentration, prefix drift) and the build scripts are in the code repository, and the snapshot rebuilds byte-identically from them with your own API keys.

Two ways the mixture is not diverse, measured and recorded before the run: routing has only 3 domains (largest 33.8%) and evidence only 4 (25.1%); the interleaver balances stream buckets but not sources, so a 512-item prefix has source TV distance 0.059 from the final stream. Both turned out to matter — see the transfer table above.

Compute

One H200 SXM, 9.0 GPU-hours total for three seeds plus all evaluation.

Citation

Full report with the five pre-registered predictions and their resolutions: see REPORT.md in the code repository. The criteria were written before the run; two resolved against expectation and one revealed a flaw in its own criterion, all of which the report states.

License

Apache 2.0, matching the base model. JevBench results are reproduced from its MIT-licensed repository; JevBench is not affiliated with TypeSafe AI, whose Jev model it measures.