Flow of Thoughts
A research map beyond chain-of-thought

How should thoughts flow through a model?

Flow of Thoughts traces how reasoning can move through a model—not only along token-by-token chains, but through recurrent depth, latent states, flow-based refinement, adaptive allocation, and recurrent memory. The goal is not necessarily more computation, but better-structured computation.

Living research notes Notes last updated Revised as new papers and evidence arrive.
Core idea
reasoning = only generate more tokens → reasoning = structure and route computation
How to read this site

Four layers, four different jobs

You do not need to read the page from top to bottom. Choose the layer that matches what you want to know.

New to the topic? Read Map → Findings → one or two Paper evidence cards. Use the Library only when you need breadth.

Conceptual map

Six overlapping mechanisms

Unifying lens

Four questions for every method

State: what carries the intermediate computation? Update: how does it change? Compute policy: where and how long does the model iterate? Outcome: what improves?

Evidence-backed synthesis

Cross-paper findings

Each synthesis separates direct paper evidence from our cross-paper inference, then ends with a concrete unresolved gap and falsifiable hypotheses.

DIRECT explicitly reported by the paper FOLLOW-UP later work testing the claim SYNTHESIS inference supported across papers HYPOTHESIS testable, not established
Read the full evidence ledger →
Paper dossiers

What each core paper establishes

Each dossier records the paper's research question, state, update rule, compute policy, direct findings, and scoped limitations. This is the audit trail behind the higher-level synthesis.

Paper explorer

Search the full bibliography

Loading…

Research programs

Open problems derived from the evidence

These are downstream of the evidence synthesis above: each should be traceable to concrete results, limitations, or future-work statements.

A

What properties must a thought state have?

Beyond expressiveness: can it expose progress, separate correct from incorrect trajectories, support verification, and remain steerable?

B

What makes another loop useful?

Can training guarantee progress under self-application rather than instability, saturation, or spurious fixed points?

C

When is convergence trustworthy?

Can we distinguish solution-aligned convergence from confidently wrong convergence before an external checker is available?

D

Where should the next FLOP go?

Depth, breadth, whole-state refinement, or token-wise pondering: which allocation has the highest marginal value?

E

Can reasoning dynamics be steered?

Can weak-to-strong or verifier-derived directions reshape trajectories without damaging their convergence or general capability?

F

Is there a coupled scaling law for thinking?

When should a system buy parameters, data, recurrent depth, state capacity, breadth, or wall-clock time?

Read evidence-derived research programs →
Reading paths

Enter from the question you care about

01

Recurrent depth

Universal Transformers → Recurrent Depth → Ouro → LoopFormer → Parcae → Loop, Think, & Generalize

Lens: Why should another loop help?
02

Latent reasoning

Coconut → PonderLM-2 → PonderLM-3 → Latent Recurrent Transformer

Lens: What can hidden thought do that token thought cannot?
03

Flows & dynamics

RIN → Flow Reasoning Models → Attractor Models → Thinking with Looped Flows → Parcae

Lens: Is reasoning progress a form of convergence?
Contribute

Help make the map sharper, not just larger.

Suggest a paper, challenge a category, or add a missing failure mode. Every entry should explain its state, update rule, compute policy, and scientific contribution.

Suggest a paper ↗