Skip to content
← Back to research index

abstract indexed · arXiv 2610.07730 · updated 2026-10-18

SanSi: A Looped Typed Decision Model for System 1.5 Thinking

First page of SanSi: A Looped Typed Decision Model for System 1.5 Thinking
From the original paper · arXiv 2610.07730Page 1. Select the image to read the PDF.

SanSi replaces generated chain-of-thought reasoning and large single-pass classifiers with a small looped language model that recursively re-applies its layers before a single typed readout, with one model serving any compute budget from one to eight loops. It costs a looped pre-trained backbone, multi-loop training with a proper scoring rule, and up to 8x the forward-pass latency of a single-pass model, though with no KV growth from generated tokens. It can fail on tasks needing explicit intermediate text, on decision formats outside the declared-option setting, or if the reported gains do not transfer from the paper's 59-source benchmark to the reader's domain, and adopting it requires reproducing the authors' specific training recipe rather than fine-tuning an off-the-shelf model.

For solo builders

A possible application for this research area. Paper-specific feasibility still needs a full-paper review.

Your workload might fit a smaller or differently structured model.

What you would change

Check for available weights and a compatible runtime before planning a product trial.

Try the idea on your product

A proposed first test. Set your budget and success criteria before running it.

Check for available weights and a compatible runtime before planning a product trial.

Compare against

Your current model on identical held-out tasks and the same resource budget.

  1. Locate the paper's implementation and check its license, model support, data needs, and hardware requirements. Stop here if you cannot obtain the required artifacts.
  2. Save a small set of representative product tasks and expected outcomes. Keep evaluation tasks out of any training or tuning, and choose quality and cost limits before running.
  3. Run the baseline and the proposed change on identical inputs. Keep other settings fixed and repeat paired runs to expose variation.
  4. Save per-task outputs, failures, timings, and all usage costs. Review regressions before expanding the test.

What to measure

Task success, latency, memory, context limits, and migration cost.

When to keep it

Keep the change only if it meets your preselected quality and latency limits and improves the metric you care about after setup and operating costs. Otherwise retain the baseline. This is an exploration plan, not a validated recommendation.

Download test plan ↓

abstract indexedPaperraft next step

Do not allocate compute yet.

This page uses the abstract and public adoption signal only. Request the deep report before relying on its recommendation.

Abstract-level screening only. Risks and infrastructure may not have been evaluated. This recommendation is not a reproduced result.
minimum test setup
not reported
published evidence setup
not reported
source-linked claims
0 of 2
exposure checks
0 of 8

Why it was shortlisted

The technical change, research area, and reason it entered the archive.

recommendation
test
research area
efficient architectures
technical change
Looped typed decision model with per-loop readout
published
2026-10-06

The approach is compatible with a single 24 GB GPU and a small team and offers a plausible quality-per-parameter gain for classification, judging, and routing workloads, but it depends on a custom looped backbone and training recipe whose benefits must be validated on the reader's own tasks before production adoption.

About the technical core

Equations have not been fetched yet.

When reading the methods, identify the rule, algorithm, or evaluation protocol that produces the claimed change. An equation is useful here only if it explains that mechanism.

Inspect the original paper

Claims and evidence

A claim is source-linked only when the PDF page and matching excerpt are available.

  1. claim 01Paperraft inference
    Read the brief interpretation

    SanSi replaces generated chain-of-thought reasoning and large single-pass classifiers with a small looped language model that recursively re-applies its layers before a single typed readout, with one model serving any compute budget from one to eight loops. It costs a looped pre-trained backbone, multi-loop training with a proper scoring rule, and up to 8x the forward-pass latency of a single-pass model, though with no KV growth from generated tokens. It can fail on tasks needing explicit intermediate text, on decision formats outside the declared-option setting, or if the reported gains do not transfer from the paper's 59-source benchmark to the reader's domain, and adopting it requires reproducing the authors' specific training recipe rather than fine-tuning an off-the-shelf model.

    This is a Paperraft inference. It is not pinned to a verified PDF passage.

    Inspect the source
  2. claim 02Paperraft inference

    72.0% accuracy on 10,027 test decisions from 59 sources: 13.5 points above a non-looped model of identical shape, 5.3 points above a newer non-looped model of its size, 1.8 points below a model with three times the parameters; as an RL judge it raises generator F1 by 7.7 points.

    This is a Paperraft inference. It is not pinned to a verified PDF passage.

    Inspect the source

Exposure map

Author findings, Paperraft interpretations, and the next check. Missing analysis never counts as evidence of safety.

quality

Still unknown

Which tasks improve, and which regress against the baseline?

compute and memory

Still unknown

What memory, hardware, and total compute does the complete method require?

latency

Still unknown

Are startup time, typical response time, and slow requests measured separately?

operations

Still unknown

What must be monitored, maintained, and rolled back?

software compatibility

Still unknown

Does the implementation support your model, runtime, and hardware?

security

Still unknown

What new data access, permissions, or trust boundaries does it introduce?

data and training

Still unknown

What data preparation or training is required, and is it included in the cost?

reproducibility

Still unknown

Are code, versions, inputs, and evaluation scripts available?

Continue the investigation

A reading guide for efficient architectures.

Editorial prompts, not findings from this paper or a validated test plan. Detailed analysis is still pending for the topics below.

What to inspect

Which assumptions does the proposed method need, and where might your workload violate them?

Plan a fair comparison

Identify the baseline, metric, dataset, and experimental settings in the paper. Which can you match?

Questions for adoption

What implementation and evaluation artifacts are available, and what would you need to supply?

Read the paper with these questions

Inside the paper

Preview the first 3 pages of the original PDF. Click the stack to turn the page.

The downloadable skill includes SKILL.md and evidence.json, with recorded findings and unanswered checks. TRY-IT.md adds a product test plan and a blank results sheet.

A reading aid for your agent. Findings still need validation.

Page 1 of 3
Open this page in the PDF ↗

Provisional research brief updated 2026-10-18. Paperraft has not reproduced this experiment.

Discuss this paper

Question a claim, compare interpretations, or share what happened when you tried the method.

Join the conversation on GitHub. Use this paper's arXiv ID in the title when starting a discussion.

arXiv 2610.07730

Comments are public and separate from Paperraft's research brief. When sharing a result, include the model, hardware, baseline and a link to your work.