REASONINGAI

RESEARCH REFERENCE / LITERATURE REVIEWED 11 NOV 2026

REASONINGAI / FIELD NOTES 001

A map of how
machines reason.

A research-grounded guide to the major families of reasoning methods used in artificial intelligence and large language models — from formal logic and search to tool-augmented agents, process supervision, reinforcement learning, and latent computation.

38 METHOD ENTRIES6 METHOD FAMILIESPRIMARY SOURCES & BENCHMARK EVIDENCE
Scope note

No finite catalogue can list every reasoning algorithm, variant, or implementation. This is a structured map of widely used and research-significant families, not a claim of completeness, a leaderboard, or an endorsement. Methods overlap and are often composed into larger systems.

01 / REASONING FOUNDATIONS

Inference before
language models.

These are long-standing forms of inference and computation. An LLM may approximate them in text, call a tool that implements them, or combine them with learned representations.

INFERENCE

Deductive reasoning

Derive a conclusion that must follow if the premises and inference rules are valid. Includes propositional and first-order logic, rule chaining, and proof construction.

Useful for consistency checks, rule-based domains, theorem proving, and explanations whose steps can be formally checked.

GENERALISATION

Inductive reasoning

Infer a general pattern or rule from observed examples. The conclusion is supported by evidence, not logically guaranteed by the samples.

Useful for pattern discovery, classification, scientific generalisation, and learning rules from demonstrations.

HYPOTHESIS

Abductive reasoning

Generate plausible explanations for an observation, then compare them against evidence. Abduction proposes hypotheses; it does not prove that the selected explanation is true.

Useful for diagnosis, debugging, root-cause analysis, and scientific hypothesis generation.

TRANSFER

Analogical & case-based reasoning

Map relations from a known case to a new situation, retrieve similar cases, and adapt the solution while checking whether the structural correspondence holds.

Useful for few-shot transfer, design, legal or scientific precedent analysis, and solving new problems from worked examples.

CAUSAL

Causal reasoning

Distinguish correlation from cause using causal graphs, interventions, counterfactuals, and assumptions about confounding. Prediction alone is not causal identification.

Useful for intervention questions, policy analysis, fault diagnosis, and distinguishing “what happens” from “what would happen if”.

UNCERTAINTY

Probabilistic & Bayesian inference

Represent uncertainty with probability distributions and update beliefs as evidence arrives. Bayesian inference combines a prior, a likelihood, and observed data.

Useful for uncertain evidence, diagnosis, sensor fusion, calibration, and reasoning where multiple explanations remain plausible.

FORMAL METHODS

Symbolic logic, SAT / SMT & theorem proving

Translate a problem into formal constraints or logical statements and use a solver or proof system to establish satisfiability, validity, or a counterexample.

Useful for exact constraints, program verification, scheduling, mathematical proof checks, and safety properties.

COMBINATORIAL

Constraint solving & program synthesis

Search for an assignment or executable program satisfying a specification. Methods include constraint programming, synthesis from examples, and search guided by partial specifications.

Useful for code generation with tests, planning, configuration, puzzles, and tasks with machine-checkable success criteria.

02 / LANGUAGE-MODEL PROMPTING

Structure the
problem-solving.

Prompting methods change how a model decomposes, expresses, samples, or organises a solution at inference time. Gains are task- and model-dependent; a longer rationale is not automatically more correct.

LINEAR TRACE

Chain-of-Thought (CoT)

Ask the model to produce intermediate steps before its final answer. Few-shot CoT supplies worked examples; zero-shot CoT uses an instruction to reason step by step.

Useful for arithmetic, symbolic, and multi-step tasks where intermediate structure helps. Wei et al. (2022); Kojima et al. (2022).

ENSEMBLE / DECODING

Self-consistency

Sample diverse candidate reasoning paths and aggregate their answers, commonly by majority vote. It replaces one greedy trace with a distribution over attempts.

Useful for problems with multiple valid solution paths and a reliably comparable final answer. It increases inference cost and can amplify shared errors. Wang et al. (2022).

DECOMPOSITION

Least-to-most prompting

Break a difficult task into ordered subproblems, solve simpler pieces first, and use earlier answers to solve later ones. It explicitly targets generalisation beyond the complexity of examples.

Useful for compositional tasks and problems where a long dependency chain can be decomposed. Zhou et al. (2022).

PLAN THEN EXECUTE

Plan-and-Solve

First construct a high-level plan, then execute the substeps. Variants such as PS+ add instructions intended to reduce missing steps and calculation errors.

Useful for zero-shot multi-step tasks when the model needs an explicit task outline. A plan still needs execution checks. Wang et al. (2023).

QUESTION DECOMPOSITION

Self-Ask & subquestion reasoning

Generate intermediate questions, answer them individually, and combine the evidence into a final response. Often paired with search or retrieval for questions requiring multiple facts.

Useful for multi-hop question answering and explicit dependency tracking. Subanswers can still be wrong or unsupported. Press et al. (2022).

COMPUTE OFFLOAD

Program-of-Thoughts (PoT)

Express the mathematical or logical computation as executable code rather than relying on natural-language arithmetic alone. A runtime evaluates the generated program.

Useful for numerical reasoning, repeated calculations, and tasks with deterministic execution. Program correctness and runtime safety remain separate concerns. Chen et al. (2022).

NEURAL + SYMBOLIC

Program-Aided Language models (PAL)

The model interprets a natural-language problem and writes a program; a Python interpreter performs the exact calculation. The model handles translation and decomposition while execution handles arithmetic.

Useful for math and symbolic tasks with executable representations. Generated code must be sandboxed and validated. Gao et al. (2022).

REPRESENTATION

Structured scratchpads & intermediate representations

Use tables, typed variables, state records, equations, schemas, or explicit intermediate objects to reduce ambiguity between steps. This is a family of representations, not one standard algorithm.

Useful for long tasks, state tracking, structured extraction, and workflows where intermediate outputs can be validated independently.

04 / AGENTS, TOOLS & GROUNDED REASONING

Think, act,
observe.

Agentic methods connect language-model decisions to external environments, tools, databases, code, or feedback. They can ground a response in new information, but introduce tool reliability and execution risks.

INTERLEAVED ACTION

ReAct

Interleave reasoning-oriented steps with actions and environment observations. The model reasons about what to do, calls a tool, observes the result, and updates its next step.

Useful for interactive tasks and multi-hop questions requiring external evidence. Tool observations need provenance and validation. Yao et al. (2022/2023).

RETRIEVAL-GROUNDED

Retrieval-Augmented Generation (RAG)

Retrieve relevant documents or records and condition the answer on those sources. Multi-hop variants retrieve iteratively as intermediate findings reveal new queries.

Useful for knowledge that changes, private corpora, citation-backed answers, and literature workflows. Retrieval is a grounding component, not proof that the synthesis is correct.

TOOL-USE POLICY

Tool calling & learned tool use

Select and invoke external functions, APIs, calculators, databases, compilers, or search systems. Toolformer is an influential approach to learning when and how to call tools.

Useful for exact calculations, current information, and actions that require external state. Validate arguments, permissions, outputs, and side effects.

NEURAL + EXECUTION

Code execution & external solvers

Translate parts of a task into code, SQL, symbolic constraints, or theorem-prover inputs and execute them with specialised engines. PAL and PoT are examples of this broader pattern.

Useful for exact arithmetic, data analysis, formal constraints, and computational tasks where execution provides a checkable result.

05 / CRITIQUE, VERIFICATION & FEEDBACK

Do not just generate.
Check.

Verification can happen at the final-answer level, at each intermediate step, or through external execution. Feedback loops help only when the signal is informative and the process resists reward hacking.

ITERATIVE CRITIQUE

Self-Refine

Generate an initial answer, produce feedback about it, and refine the answer over multiple rounds without changing model weights.

Useful for drafting, structured tasks, and cases with criteria that the model can meaningfully assess. Self-feedback can confidently reinforce an error. Madaan et al. (2023).

MEMORY + FEEDBACK

Reflexion

Turn feedback from a previous attempt into a short verbal reflection stored in episodic memory and use it to guide the next attempt. It is a trial-and-error agent framework rather than ordinary answer rewriting.

Useful for repeated environment interactions, coding agents, and tasks where later attempts can learn from earlier failures. Shinn et al. (2023).

MULTI-AGENT CRITIQUE

Multi-agent debate

Have multiple model instances propose answers, critique competing arguments, and revise across rounds. Diversity can expose errors but consensus is not a correctness guarantee.

Useful for adversarial review, alternative hypotheses, and complex answers where disagreement is informative. Du et al. (2023/2024).

FINAL-ANSWER SCORING

Outcome Reward Models (ORMs)

Train or use a verifier to score a completed solution or final answer. Best-of-N selection can sample candidates and choose the one with the highest predicted outcome quality.

Useful for reranking candidate solutions when final outcomes can be labelled. A verifier can be exploited by candidates that score well but are wrong.

STEP-LEVEL SCORING

Process Reward Models (PRMs)

Score intermediate steps for correctness or quality, rather than judging only the final result. Step-level feedback can identify where a multi-step solution first goes off track.

Useful for mathematical derivations and workflows where local steps can be evaluated. Annotation cost, label ambiguity, and reward hacking remain concerns. Lightman et al. (2023).

EXTERNAL CHECKS

Execution, tests & formal verification

Validate outputs with unit tests, property-based tests, type checkers, database constraints, symbolic solvers, or proof checkers. These checks are independent signals, not a substitute for correct specifications.

Useful for code, equations, data pipelines, and any task with a deterministic or formally stated invariant.

Important distinction

“The model reviewed its own answer” is not equivalent to independent verification. Stronger evidence comes from an external checker, a trusted environment, a formal proof, a test suite, or an expert-reviewed source record.

06 / TRAINING PARADIGMS & ARCHITECTURES

Change the model,
not just the prompt.

Some approaches shape reasoning through training signals or architectural computation. They are distinct from prompting methods and should be evaluated with matched data, compute, and baselines.

SUPERVISED LEARNING

Reasoning SFT & rationale distillation

Fine-tune a model on worked examples, structured solution traces, or trajectories distilled from a stronger teacher. Quality, diversity, and trace faithfulness matter more than raw volume alone.

Useful for transferring task-specific procedures and consistent formats into smaller or specialised models.

PROCESS SUPERVISION

Step-level supervision

Train using labels or preferences attached to individual reasoning steps. PRM800K is a released dataset of roughly 800,000 step-level correctness labels for mathematical solutions.

Useful for training process verifiers and improving candidate selection on multi-step work. Annotation policy and inter-rater quality must be documented. PRM800K.

REINFORCEMENT LEARNING

RL with verifiable rewards (RLVR)

Optimise a model using rewards that can be checked by a rule, such as an exact answer, unit tests, or a compiler. Implementations include policy-gradient methods such as PPO and GRPO; the optimiser is not itself a reasoning algorithm.

Useful for maths, code, and other domains with scalable verifiers. Reward hacking, distribution shift, and compute cost must be measured.

REINFORCEMENT LEARNING

Preference & outcome optimisation

Use human preferences, reward models, or outcome-level feedback to improve response policies. These objectives can improve helpfulness or task success but do not guarantee faithful intermediate reasoning.

Useful for aligning response behaviour and selecting solutions under defined quality criteria.

LATENT COMPUTATION

Continuous / latent-space reasoning

Maintain an internal reasoning state in hidden representations rather than decoding every intermediate step into ordinary text. Coconut feeds hidden states back as continuous “thoughts”.

Useful for research into alternative representations and potentially more compact computation. Interpretability and generalisation remain open questions. Hao et al. (2024).

RECURRENT ARCHITECTURE

Hierarchical & recurrent reasoning

Use repeated computation, recurrence, or multiple timescales to refine internal states. HRM is a 27M-parameter example with coupled high- and low-level recurrent modules; looped transformers explore related depth-through-recurrence ideas.

Useful for studying adaptive depth and structured computation. Small benchmark wins do not establish general reasoning. HRM (2025).

MULTIMODAL

Visual, spatial & multimodal reasoning

Combine text with image, video, audio, spatial tokens, or embodied observations. Methods include visual decomposition, grounding, spatial representations, tool-assisted perception, and action-conditioned planning.

Useful for diagrams, scientific figures, robotics, navigation, and tasks where the state is not text-only. Perception errors propagate into later reasoning.

07 / REPORTED EMPIRICAL FINDINGS

What the papers
actually measured.

The numbers below are reported in the cited studies on their specified tasks and model setups. They are not results produced by ReasoningAI, and they should not be compared as if they came from one shared benchmark or compute budget.

+17.9
SELF-CONSISTENCY / GSM8K

More consistent answers from sampled paths

Wang et al. report a 17.9-point gain on GSM8K for self-consistency over greedy CoT in their evaluated setup. The paper also reports gains on SVAMP, AQuA, StrategyQA, and ARC-Challenge. Sampling adds compute and can preserve correlated errors.

Read the paper ↗
4 → 74%
TREE OF THOUGHTS / GAME OF 24

Search can matter when a task requires backtracking

In the Game of 24 experiment, GPT-4 with CoT solved 4% of tasks, while the ToT framework reached 74%. This is a striking task-specific result, not a general 70-point improvement across reasoning benchmarks.

Read the NeurIPS paper ↗
16 → ≥99%
LEAST-TO-MOST / SCAN

Decomposition improved compositional length generalisation

With code-davinci-002 and 14 exemplars, least-to-most prompting reached at least 99% on the reported SCAN splits, compared with 16% for CoT. The result is tied to this compositional benchmark and historical model setup.

Read the paper ↗
+15 pts
PAL / GSM8K

Executable programs can reduce arithmetic mistakes

PAL using Codex exceeded PaLM-540B with CoT by 15 absolute top-1 accuracy points on GSM8K in the paper's reported comparison. This highlights the value of delegating exact execution to a runtime.

Read the paper ↗
+34 / +10
REACT / ALFWORLD & WEBSHOP

Reasoning-action loops help interactive agents

The ReAct paper reports absolute success-rate improvements of 34 points on ALFWorld and 10 points on WebShop over the compared baselines, using one or two in-context examples. The environments, baselines, and prompting setup matter.

Read the paper ↗
78%
PROCESS SUPERVISION / MATH

Step-level feedback outperformed outcome-only supervision

Lightman et al. report that their process-supervised model solved 78% of a representative subset of the MATH test set and release PRM800K, with 800,000 step-level human feedback labels. This is a result for their model, data, and evaluation protocol.

Read the paper ↗ · Dataset ↗
15.6 → 77.9%
RLVR / AIME 2024

Reinforcement learning produced longer, more capable reasoning traces

The DeepSeek-R1 paper reports DeepSeek-R1-Zero AIME 2024 pass@1 rising from 15.6% initially to 77.9% during RL training; self-consistency decoding raised the reported result to 86.7%. This is a specific training run and benchmark, not a universal RLVR guarantee.

Read the Nature paper ↗
32% / 2%
HRM / ARC-AGI VERIFIED HOLDOUT

Independent verification qualified the original architecture narrative

ARC Prize reported 32% on its ARC-AGI-1 semi-private set and 2% on ARC-AGI-2 for HRM. Its ablations found minimal impact from the hierarchical architecture versus a similar-sized transformer, while an outer-loop refinement process drove substantial performance. The authors' benchmark result and independent analysis should both be read.

Read the verification analysis ↗ · Original paper ↗
How to read these results

Each figure is a paper-reported result, not an independent reproduction by ReasoningAI. Differences in model version, prompt, decoding, sampling budget, dataset split, evaluator, and contamination controls can materially change outcomes. Always read the full methods and appendices before reusing a number.

08 / BENCHMARKS & EVALUATION

Measure the ability,
not the story.

There is no single benchmark for “reasoning”. Use a portfolio of tasks that isolate different skills, and include fresh or perturbed test sets wherever possible.

Benchmark / datasetPrimary signalWhat it is good forWatch-outs
GSM8K8.5K grade-school problemsMulti-step arithmetic word problemsNumerical decomposition and calculation workflowsTemplate familiarity, sensitivity to rewording, and train/test leakage
GSM-SymbolicControlled variations of GSM8K templatesRobustness to changed numbers and added clausesDo not treat one static set as a complete measure of mathematical ability
MATHCompetition-style mathematicsMulti-domain mathematical problem solvingDifficulty, grading, model/tool access, and split protocol affect comparability
GPQA448 expert-written questionsGraduate-level biology, physics, and chemistryDomain-intensive scientific question answeringSingle-choice accuracy is not equivalent to original scientific discovery
BIG-Bench Hard23 challenging tasksLogical, symbolic, and other difficult language tasksTask diversity and prompt-method comparisonsComposite averages can obscure very uneven per-task performance
ARC-AGIAbstract visual pattern inductionRule induction and out-of-distribution generalisationReport public and verified hidden sets separately; task augmentation and cost matter
HumanEval / MBPPCode generation with executable testsProgram synthesis and functional correctnessPass@k, sandbox, test coverage, and benchmark contamination must be reported
HotpotQA / FEVERMulti-hop evidence retrieval and fact verificationGrounded reasoning with source acquisitionEvidence retrieval, answer synthesis, and citation correctness are separate metrics
ALFWorld / WebShopInteractive environment successAgent planning, tool use, and sequential decisionsEnvironment version, action budget, success criteria, and resets matter

09 / FAILURE MODES & RESEARCH CAUTIONS

Evidence includes
the failures.

A credible reasoning system must explain where its method breaks, what was measured, and which checks are independent of the model.

01 / FAITHFULNESS

A rationale may not explain the cause.

Studies by Turpin et al. and Lanham et al. show that CoT explanations can omit influential information or vary in how faithfully they reflect the model's answer process. In 2026, FaithCoT-Bench added an expert-annotated collection of 1,000+ trajectories, including 300+ unfaithful instances, to evaluate faithfulness at the individual-trajectory level. Two EMNLP 2026 contributions extended this area: a survey organised internal alignment and external consistency, while an information-theoretic study found its proposed token-capacity bound did not explain unfaithfulness on the evaluated benchmarks, pointing to training as a possible source. Treat generated traces as inspectable outputs, not automatically as causal access to internal computation.

Turpin et al. ↗ · Lanham et al. ↗ · FaithCoT-Bench (ICLR 2026) ↗
02 / SELF-CORRECTION

Critique without feedback can make answers worse.

Huang et al. found that LLMs struggle to correct reasoning using only their own internal signals and sometimes degrade after an attempted correction. Prefer grounded feedback from tests, tools, evidence, or calibrated verifiers.

Huang et al. (ICLR 2024) ↗
03 / ROBUSTNESS

Small changes can expose brittle patterns.

GSM-Symbolic reports performance variance across instantiations and substantial degradation when extra clauses are introduced. Evaluate counterfactuals, paraphrases, changed quantities, distractors, and longer dependency chains.

Mirzadeh et al. (ICLR 2025) ↗
04 / BENCHMARK VALIDITY

A high score may not transfer.

Benchmark saturation, public test exposure, contamination, evaluator weakness, and domain mismatch can make reported gains look broader than they are. Use hidden or fresh tests and report per-task distributions.

Evaluation resources ↗
05 / COMPUTE & COST

More search is not free.

Sampling, debate, tree search, and long reasoning traces increase latency and token use. Compare methods under both matched compute and realistic deployment budgets, and publish cost-quality curves.

06 / VERIFIER QUALITY

Optimisation can exploit the judge.

Reward models and automatic graders can be fooled. Validate the verifier on adversarial cases and independently audit the selected outputs, not only its scores.

DeepSeek-R1 reward design discussion ↗

10 / A REPRODUCIBLE EVALUATION PROTOCOL

Make every claim
auditable.

This protocol is consistent with the evidence-first principles in ReasoningAI Studio. It is a practical checklist, not a formal standard or a substitute for domain-specific review.

  1. Pre-register the task.Define the question, dataset version, splits, allowed tools, success metric, exclusion rules, and primary comparison before looking at outcomes.
  2. Use credible baselines.Compare against direct prompting, a strong standard baseline, and the simplest method that could plausibly solve the task.
  3. Control compute and information.Report model versions, prompts, decoding settings, number of samples, token and tool budgets, latency, and access to external information.
  4. Run ablations and perturbations.Remove components, vary seed and prompt, paraphrase tasks, add distractors, and test out-of-distribution cases.
  5. Measure more than final accuracy.Track calibration, verifier precision, process validity, robustness, failure categories, cost, and human review where relevant.
  6. Preserve provenance.Publish source references, data licenses, preprocessing, code, configurations, seeds, and machine-readable result tables wherever rights permit.
  7. State what was not tested.Separate paper-reported results, local reproductions, pilot experiments, hypotheses, and open questions. Do not describe an untested method as validated.

11 / SELECTED PRIMARY SOURCES

Read the original
research.

This is a curated starting bibliography rather than a systematic review. Links point to original papers, conference proceedings, official dataset repositories, or independent benchmark analyses. Read the full paper, appendices, and data cards before relying on a reported result.

Literature snapshot: 11 November 2026. This page is educational research synthesis, not a systematic review, product benchmark, or claim that ReasoningAI has independently reproduced the cited experiments. Citation links and benchmark availability may change; verify source versions and licenses before reuse.

REASONINGAI / RESEARCH WITH A PAPER TRAIL

Make the method
as inspectable as the result.

Reasoning methods become useful research when assumptions, evidence, costs, and failure modes remain visible.