Kaizen request to a charter draft

The prompt

Draft a one-page Kaizen event charter from my notes, for the sponsor
to review and sign before the event.

My notes can be an email, meeting notes, a data table or a mix. Use only
what they say. You were not there. Where they are silent, write "Not in
these notes".

Definitions
- Scope: one process, first step to last step, that a team can walk and
  change in one event week. For a changeover: last good piece to first
  good piece, unless the notes say otherwise.
- Baseline: a number from a log, a board or a timed study. Anything
  said without a record is an estimate.
- Idea: any fix, tool, hire or purchase someone suggested.

Start with one line: "Draft charter from notes. The sponsor sets the
target and signs. The team confirms the baseline." If the problem
started when something specific changed, or the causes people name sit
in different departments, add a second line: "Check first: [the
check], before you commit a team for a week."

Then give me four parts and nothing else.

1. THE CHARTER
One line each:
Event: the problem, not a fix.
Why now: the business reason, from the notes.
Area and process: first step to last step.
Problem: what happens, how much, since when. Logged numbers only. No
causes.
Baseline: each logged measure with its source and dates. Estimates go
on their own line as "(estimate, [role])". Before calling two numbers a
conflict, check they measure the same thing over the same period.
Target: the sponsor's. If the notes give one, turn it into a number
against the baseline and add "Sponsor to confirm." Say so if it is
better than any period in the notes. If there is none, write "Sponsor
to set."
In scope. Out of scope: every other problem in the notes, one line each.
Boundaries: limits on spending, people or time from the notes, or
"Sponsor to state."
Team: 5 to 8 roles for the full week: operators from each shift that
runs the process, their supervisor, the support roles the notes point
to, and one person from outside the area. Roles only. The sponsor adds
names.
Sponsor, process owner, team lead, dates, report-out.

2. IDEAS ALREADY ON THE TABLE
Each suggested fix, with who suggested it by role, one line each. The
team tests these during the week. None of them is the plan. A request
to add a problem or skip the event is not an idea: put it under Out of
scope or in part 4.

3. BEFORE THE EVENT
Up to five things to collect for the in-scope problem, most important
first: what the baseline needs, then records that could settle a cause
someone named.

4. QUESTIONS FOR THE SPONSOR
Up to three, most important first: who sponsors and owns the process if
the notes don't say, the target, and any purchase or scope decision
someone is pushing.

Rules
- One problem per charter: the one the sponsor asked for. With no
  sponsor, the one with logged numbers.
- A cause stays with whoever said it, as "[role] thinks...", in part 2
  or 3 only.
- Replace every name with a role, quotes included. Leave out remarks
  about anyone's attitude or effort.
- Before you finish, check for names, causes in the Problem line, and
  numbers that aren't in the notes.

NOTES:
"""
[PASTE YOUR NOTES HERE]
"""