← TinyGPT · docs · devlog · roadmap · speedup
source: docs/prds/capability-retention.md · view on GitHub ↗

Capability retention under fine-tuning

Every specialist we train risks eroding the base model’s general intelligence. We have direct, measured evidence (tool-calling-frontier-parity.md §8.4–8.5): a file-ops tool-calling distill that hit 100% on its domain dropped out-of-domain agentic from 60→42% and single-turn from 87→83%; the multi-backend gold-distill dropped breadth to 31%. As we add more specialists (tool-callers, founder-voice / style LoRAs), “how much intelligence did we keep?” must be a first-class metric, not an afterthought.

Two halves

1. Measure retention — a regression suite for intelligence

A fixed “general capability” battery run before and after every fine-tune, reporting a retention delta per axis:

Output: a retention scorecard, e.g. “tool-caller: +42 file-ops / −18 breadth / −4 single-turn / −X reasoning.” Make it a gate — a specialist that craters general capability is flagged, not shipped blind. Half the battery already exists (breadth gate + single-turn BFCL).

2. Preserve retention — techniques to try

Why now / connection

This is the dual of the self-improving loop (self-improving-agents.md): self-improvement adds capability; retention measures what specialization subtracts. The auto-curriculum (training across the whole distribution) is itself a retention strategy.

Acceptance (when picked up)

References: catastrophic forgetting (McCloskey & Cohen 1989; the modern LLM version); replay / rehearsal; TIES-merge (Yadav et al. 2023); journey §8.4–8.5; the breadth gate; the self-improving PRD.