{
  "context": "This criteria evaluates how well the engineer uses IPython's event hooks and customization capabilities, specifically the pre-execution and post-execution hook system, to build a code execution logger. The focus is on proper use of IPython's events API and shell integration.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Get IPython instance",
      "description": "Uses get_ipython() to retrieve the current InteractiveShell instance for registering hooks",
      "max_score": 15
    },
    {
      "name": "Pre-execution hook registration",
      "description": "Registers a pre-execution event callback using events.register('pre_execute', callback) or events.register('pre_run_cell', callback) to capture code before execution",
      "max_score": 25
    },
    {
      "name": "Post-execution hook registration",
      "description": "Registers a post-execution event callback using events.register('post_execute', callback) or events.register('post_run_cell', callback) to capture execution completion",
      "max_score": 25
    },
    {
      "name": "Access execution info",
      "description": "Accesses execution-related information from the shell (e.g., shell.user_ns, execution_count, or info parameter in callbacks) to retrieve executed code and execution count",
      "max_score": 15
    },
    {
      "name": "Exception handling hook",
      "description": "Captures execution failures either through post-execution hook checking or by examining shell state to determine success/error status",
      "max_score": 10
    },
    {
      "name": "Automatic activation",
      "description": "Implements automatic hook registration when the module is loaded (e.g., in module-level code or through load_ipython_extension pattern) without requiring manual user setup",
      "max_score": 10
    }
  ]
}