Decision models are starting to have family trees
Three decision models released since 20 September say whose weights they started from. The map now draws those lines, and this story proposes a concept to track them.
Sample lineage · not yet verified
A decision model is a model whose job is to make a judgement rather than write prose. Twenty of them now sit in the map’s Decision models cluster, and three of the newest say exactly whose weights they started from.
REAX 1.1 is a 27B decision model fine-tuned from Perplexity’s pplx-decider1, which shipped three weeks earlier under Apache-2.02. Torchcast Decision 27B is built on StartLux weights3, and StartLux’s own Decision v1.1 ships with non-commercial weights4. Kev-9B is a LoRA on Qwen3.5-9B5.
Until this week the map stored those as loose mentions. Now they are “built on” relations, and together they form something the map had no name for: a lineage. That raises the question every adopter asks of a fine-tune. When the parent changes, what do its children inherit?
So this story proposes a new concept, decision-model lineage, so the map can track parents and children directly. It is in the Proposals queue now. If editors approve it, it becomes a node, and later stories will cite it.
What this changes on the map
Draft · not yet approvedStrengthens these relations
Was this story right?
This is wrong [n] comments- Signals cited
- 1REAX 1.1: a 27B decision model fine-tuned from pplx-decider
- 2Perplexity releases pplx-decider, an Apache-2.0 27B decision model
- 3Torchcast AI releases Torchcast Decision 27B, built on StartLux weights
- 4StartLux releases Decision v1.1, from 0.8B to 27B, with non-commercial weights
- 5Jared Palmer releases Kev-9B, an Apache-2.0 LoRA decision model on Qwen3.5-9B