---
id: "prereq-llm-context"
type: "prereq"
source_timestamps: ["00:01:48", "00:04:31"]
tags: ["llm-basics"]
related: ["concept-icm"]
reason: "Required to understand why reducing token usage via folder structures is a significant optimization."
sources: ["video"]
sourceVaultSlug: "interpretible-context-methodology-icm-2026Jun02"
originDay: 1
---
# Understanding LLM Context Windows

## Why It's Required

To fully grasp why the folder-based [[concept-icm-d1]] is efficient, you must understand:

- **How LLMs process tokens** — text is chunked into tokens before inference
- **Context window limits** — every model has a maximum context size
- **Cost scaling** — most APIs price per input + output token, so context bloat directly costs money
- **Attention degradation** — practical performance often degrades as context grows ('lost in the middle')

## Connection to ICM

ICM's central efficiency argument is that **on-demand folder navigation loads only relevant slices into context**, instead of stuffing everything into the prompt. This is consistent with general LLM guidance (externalize persistent state, load only what is needed).

The claimed 20–40% token reduction in [[claim-icm-superiority]] is a direct consequence of this design choice.


## Related across days
- [[prereq-llm-context-windows]]
- [[claim-token-efficiency]]
- [[concept-context-scoping]]