{
  "context": "Evaluates whether the solution leverages aenum's typed enum utilities to model ordered severities and lowercase string channels for the alert routing helper. Checks focus on using AutoNumber/Ordered/Unique options instead of hand-written equivalents to meet the spec requirements.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Int enum",
      "description": "Severity is built on aenum.IntEnum (or an AutoNumberEnum variant) so members are integer-backed and can be converted from ints directly.",
      "max_score": 20
    },
    {
      "name": "Auto numbering",
      "description": "Severity values are assigned via aenum.auto or AutoNumberEnum rather than manual integers, starting at 1 and following the declaration order.",
      "max_score": 20
    },
    {
      "name": "Ordered",
      "description": "Severity comparisons rely on aenum.OrderedEnum (or Ordered* mixin) to reflect the declared urgency order without custom comparator code.",
      "max_score": 20
    },
    {
      "name": "String enum",
      "description": "Channel is implemented with aenum.StrEnum or LowerStrEnum so members store lowercase strings and str(member) returns that value directly.",
      "max_score": 20
    },
    {
      "name": "Uniqueness",
      "description": "aenum.UniqueEnum or the aenum.unique decorator is applied to prevent duplicate values across both Severity and Channel definitions.",
      "max_score": 20
    }
  ]
}