{
  "context": "Tests whether the response provides a sound Redis caching design for a read-heavy, infrequently-updated catalog.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Proposes cache key structure",
      "description": "Defines a sensible cache key pattern that accounts for pagination, filters, or query parameters",
      "max_score": 12
    },
    {
      "name": "Sets appropriate TTL",
      "description": "Suggests a TTL that balances freshness vs performance given the few-times-per-day update frequency",
      "max_score": 10
    },
    {
      "name": "Describes invalidation strategy",
      "description": "Explains how to invalidate cache when products are updated (event-driven, key deletion, versioned keys, or pattern-based)",
      "max_score": 15
    },
    {
      "name": "Addresses cache stampede or thundering herd",
      "description": "Mentions the risk of many concurrent requests hitting the DB when cache expires and suggests mitigation (locking, stale-while-revalidate, jittered TTL)",
      "max_score": 10
    },
    {
      "name": "No incorrect information",
      "description": "Response does not contain factually wrong statements about Redis or caching patterns",
      "max_score": 10
    }
  ]
}