← All parts of this equation

Equation 1 · Part 7 · How Claude Code's Memory Actually Persists Across Sessions

Symbol k

Tstart=Tsys+Tmem+Tenv+Ttools+∑i=1kMiT_{\mathrm{start}} = T_{\mathrm{sys}} + T_{\mathrm{mem}} + T_{\mathrm{env}} + T_{\mathrm{tools}} + \sum_{i=1}^{k} M_i
kk

What this part means

k appears in the bound of this sum. The bound states where the repeated operation starts, ends, or which values it includes.

Its job in the formula

k appears in the bound of this sum. The bound states where the repeated operation starts, ends, or which values it includes.

The passage around this formula

…and worth writing down as an identity: Tstart=Tsys+Tmem+Tenv+Ttools+∑i=1kMiT_{\mathrm{start}} = T_{\mathrm{sys}} + T_{\mathrm{mem}} + T_{\mathrm{env}} + T_{\mathrm{tools}} + \sum_{i=1}^{k} M_i. where MiM_i is the token count of the i -th memory file discovered along the walk from the filesystem root to the working directory, summed over however many, k , are found. Every term is committed before the developer types a word. The point is not the specific numbers; it is that TstartT_{\mathrm{start}} is arithmetic settled at launch, and every additional CLAUDE.md file anyone commits to a repository is a term someone chose to add to it, permanently, for…

Read this part in the article →

Learn the underlying idea

A variable is a named place for a value. Its letter is a local label: x can mean position in one formula and a data point in another.

Open the illustrated variables: a letter stands for a value guide →

See this notation across published equations →

Sources cited in the surrounding passage

These citations provide research context; check each source for the exact claim it supports.