Claude Code First, specification version 0.1.0. The plain-language guide

Version 0.1.0. Grade R3/S3.

F3 Content moved into on-demand files keeps growing where it lands, and stays bounded only under a ceiling of its own

FieldValue
Statusactive
TopicContext economy and agent prose
GradeR3/S3
CasesShio, roadkeep
Contrarynone
Harness factsH3

Claim

Skills and area files that took content out of the every-turn file grew afterwards as the every-turn file had: without a ceiling they reached several times the size of what they replaced, and the one project that capped them had to add a ceiling for each file it had left uncapped.

Mechanism

Moving content to a trigger-loaded file removes it from the every-turn budget (F2), and with it from the only check that was counting it. The destination receives the same additions the every-turn file used to receive. A skill's body is paid in full on each turn that loads it (H3), so a skill that grows becomes a large cost on the turns that trigger it.

Observations

Independence

Two origins: Shio's area files and roadkeep's skill are separate files in separate repositories, each growing under its own project's work. winwright caps its shipped skill's body at "private const int Body = 6000;" [winwright@861b82e:tests/Winwright.Tests/SkillTests.cs#L33], on the stated ground that otherwise the skill "becomes the same instruction file it replaced" [winwright@861b82e:tests/Winwright.Tests/SkillTests.cs#L31]. That is a remedy with no recorded growth behind it, so it adds no origin; it predates roadkeep's orientation ceiling (2026-08-26 against 2026-08-31), so it is not a copy of it.

Counter-evidence

Grade

R3: growth of the moved content is observed independently in two projects. S3: both are counted, Shio's bytes per directory and file, and roadkeep's code units before and after the split and per later task. Not S4: roadkeep's tests encode the ceiling, but no source shows one failing.