{
  "context": "Evaluates how well the solution leverages pylibmc's UTF-8 normalization between str and bytes keys to implement a cache wrapper. Checks focus on correct client setup plus use of set/get, get_multi, and delete operations so text and byte keys stay interchangeable without duplicate entries.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Client config",
      "description": "Creates and reuses a pylibmc.Client with the provided servers so UTF-8 key normalization is available (no per-call reconnections or alternate clients).",
      "max_score": 20
    },
    {
      "name": "Set/get normalization",
      "description": "Uses pylibmc set (or mapping assignment) and get to show that a value stored with a str key is readable via the equivalent UTF-8 bytes key and vice versa, relying on the client's built-in key handling.",
      "max_score": 25
    },
    {
      "name": "Bulk retrieval",
      "description": "Uses get_multi to fetch a mix of str and bytes keys and returns values keyed in the requested representations without duplicating entries for the same normalized key.",
      "max_score": 20
    },
    {
      "name": "Delete coherence",
      "description": "Uses delete (or delete_multi) so removing an entry by one key representation also clears the other form, with subsequent get/get_multi reflecting the miss.",
      "max_score": 15
    },
    {
      "name": "Default handling",
      "description": "Applies pylibmc get default handling (e.g., default argument) to return caller-provided defaults when normalized keys are absent instead of raising or inventing placeholders.",
      "max_score": 10
    },
    {
      "name": "No redundant encoding",
      "description": "Does not reimplement key encoding/decoding logic or store duplicate entries; relies on pylibmc's internal UTF-8 normalization rather than manual conversions.",
      "max_score": 10
    }
  ]
}