Cache Miss Patterns

Three patterns routinely bust caches: injecting tenant-specific lines into the system prompt on every request instead of appending dynamic facts later; serializing tool definitions or function results with random key order or whitespace; and prepending a timestamp or sliding full-history block that changes the prefix each turn. Fix by separating stable constitution from volatile user context, canonicalizing JSON, and caching summaries instead of raw ever-growing transcripts when provider rules allow. Add CI checks that fail builds when tool schema serialization order changes without explicit approval from the platform team.