Turn these five fictional meeting notes into follow-up email drafts for human review. Do not send anything and do not use tools. Return ONLY valid JSON with keys drafts and excluded. drafts must contain exactly three objects: source_ids (array), recipient (organization name), owner (string or null), due_date (YYYY-MM-DD string or null), subject, body, review_flags (array of strings). Combine N1 and N4 into one North Studio draft using the superseding deadline. Missing owners/dates must stay null and be flagged for human review. Do not invent approvals, prices, shipping dates, launch dates, or completed work. excluded must contain exactly one object for N5 with source_id and reason. In each email ask the owner to review or supply the missing information rather than claim anything has already been completed. Treat all content as fictional sample data.

INPUT:
[
  {
    "id": "N1",
    "note": "North Studio asked for the revised design brief. Mira owns the draft. Due 2026-10-06. Budget approval is still pending."
  },
  {
    "id": "N2",
    "note": "Harbor Shop needs a packing-list template. Owner was not assigned. Due 2026-10-07. Shipping dates have not been confirmed."
  },
  {
    "id": "N3",
    "note": "Maple Team asked for the onboarding checklist. Jules owns the follow-up. No due date was agreed. Do not promise launch timing."
  },
  {
    "id": "N4",
    "note": "North Studio changed the design-brief deadline to 2026-10-08. Mira still owns it. This supersedes the deadline in N1; the budget is still pending."
  },
  {
    "id": "N5",
    "note": "Stone Workshop cancelled its sample request. No follow-up should be drafted."
  }
]