Server-side context caching requires an exact token match starting from token zero of the prompt, so any mutable value placed before or inside the static context — a timestamp, session ID, or turn counter — changes the prompt hash and forces a full-price cache miss. Agent harnesses enforce prefix invariance by structurally separating an immutable header (tool definitions, system prompt, repository context) from a dynamic suffix appended at the end of each turn.