{
  "context": "This criteria evaluates how well the engineer uses PostHog's batch size limiting and queue management capabilities. It focuses on proper client initialization with batch configuration, effective event capture methods, and correct shutdown procedures to ensure event delivery.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Client initialization",
      "description": "Uses posthog.Client() or similar initialization method with proper project_api_key parameter",
      "max_score": 15
    },
    {
      "name": "Batch size configuration",
      "description": "Configures batch size settings using parameters like flush_at (events per batch) or flush_interval (time between flushes) during client initialization",
      "max_score": 20
    },
    {
      "name": "Event capture method",
      "description": "Uses posthog.capture() method to send events with event name and properties",
      "max_score": 20
    },
    {
      "name": "Distinct ID usage",
      "description": "Includes distinct_id parameter when calling capture() to identify users",
      "max_score": 10
    },
    {
      "name": "Large payload handling",
      "description": "Captures events with large properties (200KB+ data) by passing dictionaries with substantial content to the properties parameter",
      "max_score": 15
    },
    {
      "name": "Event flushing",
      "description": "Calls posthog.flush() to send all queued events before program termination",
      "max_score": 15
    },
    {
      "name": "Client cleanup",
      "description": "Uses posthog.shutdown() or posthog.join() to properly clean up the client and ensure event delivery",
      "max_score": 5
    }
  ]
}