Handle a Cache-Busting Policy Change
Choose a rollout plan that preserves prompt-cache economics while still shipping a required instruction change.
A required policy clause is changing the shared prompt prefix. What should Omar do before the new refund policy goes live? Create one versioned stable prefix, add the policy clause there, batch the regression set, and monitor cache recovery and routing quality. Right. Exact-prefix caching survives disciplined versioning, Batch handles non-urgent tests, and routing is rechecked against the new policy behavior. Let each team paste the clause wherever it fits their local prompt. Weaker. This fragments the initial prefix, creating avoidable cache misses and making token economics hard to compare. Delay the policy update until the cache metrics look stable…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in