{
  "context": "Evaluates whether the solution uses ldap3 to run a search and expose results through library-provided accessors. Emphasizes using built-in JSON/LDIF serialization helpers (including file output) instead of custom formatting.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Search call",
      "description": "Builds an ldap3 Server/Connection and issues Connection.search with the supplied base DN, filter, and attribute list before exporting results.",
      "max_score": 20
    },
    {
      "name": "Entries access",
      "description": "Retrieves structured results via Connection.entries to populate the returned entries collection rather than parsing raw responses manually.",
      "max_score": 15
    },
    {
      "name": "Raw response",
      "description": "Captures the last operation's raw payload using Connection.response (or the tuple from get_response for async) to populate raw_response without reconstructing it.",
      "max_score": 10
    },
    {
      "name": "JSON serialization",
      "description": "Uses Connection.response_to_json (or response_to_json helper) to generate the JSON text for the last search instead of hand-built JSON.",
      "max_score": 20
    },
    {
      "name": "JSON file",
      "description": "Writes JSON output with ldap3 support (response_to_json(stream=...) or response_to_file on the JSON data) rather than custom file formatting logic.",
      "max_score": 10
    },
    {
      "name": "LDIF serialization",
      "description": "Uses Connection.response_to_ldif (or response_to_ldif helper) to generate LDIF text for the last search rather than crafting LDIF manually.",
      "max_score": 20
    },
    {
      "name": "LDIF file",
      "description": "Persists LDIF output through ldap3 facilities (response_to_ldif(stream=...) or response_to_file) instead of manual LDIF file writing.",
      "max_score": 5
    }
  ]
}