{
  "context": "Tests whether the agent organizes meeting content into the three correct labeled sections (Decisions, Action Items, Key Takeaways), places each item in the right section, includes ownership information for action items, captures enduring context such as recurring patterns, compliance constraints, and cross-team dependencies, and excludes transient logistics from the persistent notes.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Decisions section present",
      "description": "organized_notes.md contains a labeled section for decisions (e.g., 'Decisions', 'What We Decided')",
      "max_score": 7
    },
    {
      "name": "Action items section present",
      "description": "organized_notes.md contains a labeled section for action items (e.g., 'Action Items', 'Next Steps', 'Follow-ups')",
      "max_score": 7
    },
    {
      "name": "Key takeaways section present",
      "description": "organized_notes.md contains a labeled section for patterns, constraints, or broader context (e.g., 'Key Takeaways', 'Context', 'Observations')",
      "max_score": 7
    },
    {
      "name": "Airflow decision placed correctly",
      "description": "The Airflow adoption decision appears under the decisions section, not under action items or takeaways",
      "max_score": 9
    },
    {
      "name": "Analytics replica policy placed correctly",
      "description": "The policy requiring pipelines to read from analytics replicas (not production replicas) appears under the decisions section",
      "max_score": 9
    },
    {
      "name": "Action item ownership",
      "description": "Action items include all four named owners: Carlos (template repo), Lena (onboarding), James (roadmap), Sofia (PII pipeline review)",
      "max_score": 12
    },
    {
      "name": "Schema hard-coding pattern in takeaways",
      "description": "The recurring hard-coded schema name pattern (three prod/staging bugs) appears under the takeaways/context section",
      "max_score": 10
    },
    {
      "name": "PII compliance constraint in takeaways",
      "description": "The PII audit logging compliance requirement appears under takeaways/constraints, not under decisions or action items",
      "max_score": 10
    },
    {
      "name": "Cross-team dependency captured",
      "description": "The dependency of the customer cohort analysis feature on pipeline migration completion IS present in organized_notes.md",
      "max_score": 10
    },
    {
      "name": "Meeting logistics excluded",
      "description": "Transient logistics (weekly sync moving to Wednesday, sprint review Thursday at 2pm) do NOT appear in the persistent notes written to the notes system",
      "max_score": 19
    }
  ]
}