The Caching Strategy Designer

Design a caching strategy for this agent.

Agent: [DESCRIBE]
What is stable across calls: [SYSTEM PROMPT, TOOLS, DOCUMENTS,
CONVERSATION HISTORY]
What varies: [DESCRIBE]
Volume: [DESCRIBE]

Produce:
1. What is identical across requests and could be cached at the
   provider level
2. The ordering requirement: stable content must come before
   variable content in the prompt, or nothing caches
3. Anything currently early in the prompt that varies per request —
   these silently break everything after them
4. Where cache breakpoints should go
5. Application-level caching: tool results, computed values,
   retrieved documents
6. Cache invalidation: what makes each cached thing stale
7. Cache keys: what makes two requests equivalent

Then audit for silent invalidators:
8. Timestamps, request IDs, or UUIDs in the system prompt
9. Non-deterministic serialisation — unsorted keys, iterated sets
10. Tool sets that vary by user or request
11. Conditional prompt sections

Finally: how would I verify caching is actually working, rather
than assuming it?

Mark provider-specific mechanisms as [VERIFY CURRENT].