{
  "context": "This criteria evaluates how well the engineer uses requests-cache to implement persistent HTTP response caching with automatic serialization. The focus is on proper use of CachedSession with SQLite backend (which uses pickle serialization by default) to store and retrieve HTTP responses.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "CachedSession initialization",
      "description": "Uses requests_cache.CachedSession or requests_cache.install_cache() to create a cached session with SQLite backend (default or explicitly specified)",
      "max_score": 25
    },
    {
      "name": "Backend configuration",
      "description": "Properly configures the cache backend to use the specified database file name (http_cache.db) via the cache_name or backend parameter",
      "max_score": 20
    },
    {
      "name": "HTTP requests",
      "description": "Makes HTTP GET requests using the CachedSession instance (or requests module functions if using install_cache) to fetch data from the specified API endpoint",
      "max_score": 15
    },
    {
      "name": "Cache verification",
      "description": "Demonstrates cache functionality by checking if responses are cached using session methods like cache.contains(), cache.has_url(), or by inspecting response attributes like from_cache or created_at",
      "max_score": 20
    },
    {
      "name": "Response persistence",
      "description": "Correctly relies on the default pickle serialization behavior of SQLite backend to automatically serialize and deserialize response objects without explicit serialization code",
      "max_score": 15
    },
    {
      "name": "Cache file persistence",
      "description": "Creates a persistent cache file (http_cache.db) that can be reused across program executions without requiring manual file handling",
      "max_score": 5
    }
  ]
}