{
  "context": "Evaluates whether the solution configures pylibmc for binary-protocol connections with SASL credentials and verifies authenticated cache operations using the real client API. Checks reward code that enforces SASL prerequisites rather than silently falling back to unsecured modes.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Binary client",
      "description": "Instantiates pylibmc.Client (or equivalent pool member) with binary=True so no ASCII-mode client is created before performing cache work.",
      "max_score": 30
    },
    {
      "name": "SASL params",
      "description": "Supplies username and password directly to pylibmc.Client to enable SASL negotiation; avoids constructing a client without both credentials when SASL is required.",
      "max_score": 25
    },
    {
      "name": "Auth operations",
      "description": "Uses pylibmc cache calls (e.g., set/get or mapping operators) for the ping/health check so authenticated binary traffic is exercised instead of stubbing or skipping real operations.",
      "max_score": 25
    },
    {
      "name": "Credential guards",
      "description": "Explicitly detects missing binary flag or missing username/password and raises an error before attempting pylibmc operations, reflecting SASL's binary-only requirement.",
      "max_score": 20
    }
  ]
}