Invention 6
Context cartridges for a frozen core
The design / Invention 6
Built fromresearch/02-corerope-design.md (edit)
Once weights stop moving, each user's context state is the largest remaining data movement. A cartridge is a trained, compact starting state for a corpus (a codebase, a manual, a long chat history), stored in the memory tier and loaded in one step instead of re-reading the corpus. Because the core never changes, a cartridge trained once stays valid for the chip's whole life.
Prior art. Stanford's Cartridges (2025) train a small KV cache offline per corpus through synthetic self-study and amortize that cost across every query on the corpus, with up to ~40x less memory than in-context learning (Cartridges; Diaz, 2025). A September 2026 follow-up addresses derailment when questions leave the corpus (Cartridges++).
What is new here.
- The cartridge is a recurrent state, not a KV cache. For a hybrid core it is the recurrent layers' starting state plus a short list of compressed global-attention entries. Its size is fixed whatever the corpus length.
- Durability. On GPUs every model update invalidates every cartridge. A frozen core makes them a durable asset, worth training once for any corpus that many sessions share.
- Checkpointed prefixes. Agent turns reuse 85 to 99% of their context. The core snapshots its recurrent state at chunk boundaries, so a returning session resumes from a snapshot rather than replaying tokens.
Budget. Per user the core holds ~1 MB of recurrent state at 4 bits and reads about 0.5 MB of sparse global attention per token. Together with memory-tier lookups that is ~0.2 mJ per token in the central case, a quarter of the token's energy before overheads and the largest term after the core itself.
Source: research/02-corerope-design.md, lines 126 to 136Edit on GitHub