{
  "context": "Evaluates how well the solution uses josepy's declarative JSON object support to implement the contact profile mapper, focusing on field mapping, defaults, and omission of empty values. Emphasizes reliance on josepy helpers instead of hand-written JSON handling.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Field mapping",
      "description": "Defines the profile as a josepy JSONObjectWithFields subclass and uses josepy.field/Field to map username, email, timezone, phone, tags, and marketing_opt_in to JSON keys user, contact_email, tz, phone, labels, and marketing_opt_in.",
      "max_score": 30
    },
    {
      "name": "Default values",
      "description": "Relies on josepy field defaults to supply timezone \"UTC\" and marketing_opt_in False when the JSON input omits them, rather than hardcoding defaults outside the descriptor configuration.",
      "max_score": 20
    },
    {
      "name": "Omit empty",
      "description": "Uses josepy's omitempty behavior on the phone and tags fields so json_dumps/to_json skip those keys when values are None or empty.",
      "max_score": 20
    },
    {
      "name": "JSON helpers",
      "description": "Parses and emits data through josepy's JSON helpers (from_json/json_loads/json_dumps) instead of custom JSON parsing/serialization code.",
      "max_score": 15
    },
    {
      "name": "Partial output",
      "description": "Leverages to_partial_json from JSONObjectWithFields to produce the dictionary form with omissions handled by josepy rather than manually filtering keys.",
      "max_score": 15
    }
  ]
}