We introduce Mobius-v0, an architecture that comprises a globally shared Memory (FFN) that stores knowledge vectors and multiple Reasoners (Self-Attn) that iteratively achieve compositional reasoning. Using hidden states as cache and carrier, reasoners repeatedly query memory for required knowledge-vectors, while the knowledge is transmitted back to reasoning operators. Through this knowledge-reasoning-separation architecture, Mobius achieves better knowledge compression and reasoning efficiency. Built upon Mobius-v0 architecture: 1) Our 7B model trained-from-scratch achieves similar downstream score as a 7B Transformer baseline with 62.6% of baseline's training data. 2) Our Intern-S2-Mobius, continually-pretrained from Qwen3.5-35B, achieves similar downstream score while delivering nearly 4x end-to-end inference speedup.
Alex: Welcome to another episode of ResearchPod.
Sam: Today we're looking at a paper from the Shanghai AI Laboratory introducing a new model architecture called Mobius-v0. The central question it asks is deceptively simple: why do current AI systems have to write out thousands of extra words just to solve a tricky math or coding problem?
Alex: That's a question I hadn't thought to ask before. I just assumed that's how these systems work.
Sam: Most people do. And to be fair, generating long sequences of step-by-step text genuinely has made AI models much better at complex reasoning. But it creates a serious efficiency problem. Every intermediate thought has to be spelled out as a distinct word on the screen, and the computational cost climbs rapidly, even for straightforward tasks.
Alex: It's like making someone write out every single scratchpad calculation on a blackboard instead of letting them think quietly before answering.
Sam: That's a useful way to frame it. And it points to a structural limitation. In a traditional model, information flows in a strict one-way direction—from early processing stages to the final output. There's no way to loop back, and there's no shared workspace where different parts of the system can compare notes.
Alex: So every step of the reasoning has to be committed to text before the next step can begin?
Sam: Exactly. The system uses generated words as a bridge between every single stage of thought. Which means if you want to check your work or revisit an earlier assumption, you have to write all of that out too. That's where the verbosity comes from.
Alex: And Mobius is trying to change that?
Sam: It is. The core idea is to separate two things that standard models keep tangled together: where factual knowledge is stored, and the rules the system uses to reason. Think of it like keeping your encyclopedia in a completely different room from your scratchpad. That way, you can update your facts without accidentally erasing how you do math.
Alex: That separation sounds almost obvious when you put it that way. Why hasn't it been done before?
Sam: It's technically difficult to implement cleanly. What Mobius builds is something the authors call a globally accessible repository—a kind of shared memory that different layers of the model can read from and write to simultaneously, rather than passing information strictly in one direction. That bidirectional flow is what allows the system to refine its reasoning internally, without having to surface every intermediate step as visible text.
Alex: So instead of writing out "let me check this... actually, that's wrong... let me try again," the model does all of that silently, in a kind of internal scratchpad?
Sam: That's precisely it. And the paper provides a concrete example to show how much difference that makes. On a linear algebra multiple-choice question, a standard model generates well over two thousand tokens of text—long paragraphs of trial and error—before arriving at an answer. Mobius completes the same reasoning using roughly a quarter of that, without skipping any of the core mathematical steps.
Alex: That's a meaningful reduction. But I'd want to know whether the model is actually reasoning more carefully, or just cutting corners.
Sam: The authors asked exactly that question, and they were explicit about investigating it. The detailed traces they examined confirm that the shorter output comes from genuine efficiency improvements—the underlying logic remains intact. The system isn't guessing; it's just not writing out the redundant parts.
Alex: Which brings up a longer-term question. If you cleanly separate knowledge from reasoning, does that help with one of the persistent problems in AI—where updating a model's facts tends to corrupt what it already knows how to do?
Sam: That's one of the more significant implications the paper points to. When facts and reasoning rules are stored together, updating one tends to interfere with the other. A clean separation offers a pathway around that constraint. The authors suggest it could support systems that continuously absorb new information without forgetting past training—though they're careful to note that real-world deployment still needs to be validated.
Alex: And presumably the hardware picture changes too, if you're not keeping everything loaded into fast memory at once.
Sam: That's the practical upshot. If bulk knowledge lives on external storage while only the active reasoning components sit in fast memory, future systems could be deployed at significantly lower cost. The authors also position this latent approach as a stronger foundation for modeling continuous physical environments and generating scientific hypotheses—but again, those remain directions rather than demonstrated results.
Alex: So Mobius is less a finished product and more a proof of concept for a different way of thinking about how AI systems should be built.
Sam: That's a fair characterization. The architecture itself is the contribution. The claim is that by rethinking where knowledge lives and how reasoning operates, you can build systems that are more efficient, more updatable, and potentially more capable—without simply making them larger.
Alex: That's a worthwhile set of ideas to sit with. Thanks for listening to ResearchPod.