Skip to content
Sprint projectSep 14, 2026Turkiye

Catastrophic Forgetting Makes the Chain-of-Thought More Load-Bearing, Not Less, Where No Shortcut Exists

Mustafa Ilker Aktas · Team Ataturk Research

Submitted to AI Incident Response Sprint. Sprint projects are early-stage work by participants, not Apart Research publications.

Read the report

Report: Catastrophic Forgetting Makes the Chain-of-Thought More Load-Bearing, Not Less, Where No Shortcut Exists

Code (opens in new tab)
Share

After the Hugging Face incident, OpenAI made the use of chain-of-thought monitoring a mandatory requirement for RL training and evaluation. However, this is only true if the model’s chain-of-thought causally determines the answer; a fluent but causally inert chain is text that the monitor can read but cannot track. Lobo et al. demonstrated that fine-tuning reduces chain-of-thought faithfulness and conjectured that this is due to catastrophic forgetting; although this hypothesis has not been tested, it is accepted in the literature as an established finding. Two fine-tuning runs per seed at two seeds, on a 1.5B model, with identical data, format, schedule, and hyperparameters; the only variable was whether replay suppressed forgetting or not; measurements were taken at 13 checkpoints over 600 steps. Forgetting occurred in one arm (general NLL rose by 0.436 on a fixed corpus), but not in the other (-0.032), and the model did not collapse in either arm. Forgetting did not disrupt the causal role of the chain-of-thought; it increased it on four length-invariant measures, reported as forgetting arm versus control: error propagation 0.486 versus 0.422, the shuffled-chain gap 0.229 versus 0.031, the chain’s contribution to accuracy 0.762 versus 0.575, and the effect of premise masking -0.201 versus +0.254. The difference is explained by the evaluation task: without the chain the model performs at chance (0.150, chance 0.167), so no shortcut is available. This reconciles the two sets of results and yields a measurable regime test a lab can run on its own tasks.

Reviews

Judging this Sprint?

Review this project

Your public critique appears on this page without your name. Your private critique is not published; only the Apart team reads it. If you agree below, we share your review with grantmaking.ai (opens in new tab) and the Transformative AI Fund so strong projects can be funded.

Not shown on this page.

Shown on this page, without your name.

Only the Apart team reads this, and funders if you agree below.

Share my name publicly on grantmaking.ai *
Share my private critique with funders *

How much would this matter for AI safety if it worked? How innovative is it? For scores of 4-5: is this actually new to the field, or replicating recent work?

Scoring guide
  1. 1Negligible. No clear problem addressed, or no meaningful novelty.
  2. 2Limited. Addresses a real problem but with a generic or well-trodden approach. Incremental at best.
  3. 3Moderate. Clear problem with a reasonable approach; some novelty in framing or method beyond routine application of existing tools.
  4. 4Significant. Important problem with an original approach, or identifies a neglected problem area. A valuable contribution others could build on.
  5. 5Exceptional. Tackles a critical AI safety problem with a genuinely novel approach, or opens a new research direction. Clear theory of change. You'd be excited to share this with researchers in the area.

How sound are methodology, implementation, and findings?

Scoring guide
  1. 1Seriously flawed. Methodology broken, results uninterpretable, or implementation doesn't work.
  2. 2Weak. Approach has significant gaps: missing validation, flawed experimental design, or incomplete implementation.
  3. 3Competent. Technically solid given the short duration. Methodology makes sense, results are interpretable, limitations acknowledged, work builds toward clear conclusions.
  4. 4Strong. Thorough methodology with convincing validation. Results clearly support conclusions. Immediately useful for future work.
  5. 5Exceptional. Ambitious scope executed rigorously. Surprising findings, novel methods, or unusually robust validation.

How clearly are work, findings, and impact potential communicated?

Scoring guide
  1. 1Incomprehensible. Cannot determine what the project is actually claiming or doing.
  2. 2Hard to follow. Key information buried, missing, or diluted by excessive length. Significant effort to extract main points.
  3. 3Clear enough. Can understand the problem, approach, and results without undue effort. Core content clearly present: problem, method, findings, limitations.
  4. 4Well presented. Easy to follow, well-structured, appropriate level of detail. Target audience would get it quickly.
  5. 5Exceptionally clear. A pleasure to read. Complex ideas made accessible. Could serve as a model for how to present this type of work.

  1. Interesting technical project. Execution was well-considered and detailed. I would have liked to see more than one model size - seems very plausible either that the effect becomes stronger or reverses at larger scales and this study does not give good intuition on scalability. Still, it is a neat experiment which fit within the hackathon format and offers novel results in the space.

    Some of the specific details should probably have been moved to an appendix. The combination of italics and curly font made this very hard to read.

Cite this project

@misc{aktas2026catastrophic,
  title = {{Catastrophic Forgetting Makes the Chain-of-Thought More Load-Bearing, Not Less, Where No Shortcut Exists}},
  author = {Mustafa Ilker Aktas},
  year = {2026},
  month = sep,
  note = {Submitted to AI Incident Response Sprint, an Apart Research Sprint},
  howpublished = {\url{https://apartresearch.com/sprints/projects/catastrophic-forgetting-makes-the-chainofthought-more-loadbearing-not-less-where-no-shortcut-exists-393g}},
  url = {https://apartresearch.com/sprints/projects/catastrophic-forgetting-makes-the-chainofthought-more-loadbearing-not-less-where-no-shortcut-exists-393g}
}

Build something like this at the next Sprint

AI Collusion Research Sprint · Oct 23 - 25, 2026