{
  "context": "Evaluates how the solution uses ldap3's LDIF client strategy to generate offline change and content LDIF. Emphasizes streaming, ordering, and line-ending controls via package helpers instead of manual formatting.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "LDIF strategy",
      "description": "Initializes ldap3.Connection with client_strategy=ldap3.LDIF (or LDIF constant) to run completely offline and binds through that strategy rather than using a live SYNC/ASYNC connection.",
      "max_score": 20
    },
    {
      "name": "Change via ops",
      "description": "Builds the change LDIF by issuing ldap3 Connection operations (e.g., add with object classes/attributes and modify using MODIFY_REPLACE/MODIFY_ADD/MODIFY_DELETE) so the LDIF strategy formats changetype sections, instead of manual string concatenation.",
      "max_score": 25
    },
    {
      "name": "Stream output",
      "description": "Uses ldap3-provided streaming hooks (Connection.stream, response_to_ldif(stream=...), or response_to_file) to write the generated LDIF change text to a file-like target while also returning it.",
      "max_score": 20
    },
    {
      "name": "Content export",
      "description": "Serializes entry data to LDIF content using ldap3 helpers such as response_to_ldif with sort_order/attribute ordering or Entry.entry_to_ldif(), rather than manually formatting attributes.",
      "max_score": 20
    },
    {
      "name": "Line separators",
      "description": "Configures LDIF line endings through ldap3 parameters (line_separator on response_to_ldif or LDIFConnectionStrategy) so CRLF requests are honored without post-processing the returned text.",
      "max_score": 15
    }
  ]
}