Critique a Proposal Before It Goes to a Decision Maker

The proposal is ready to send. This reads it from the other side: what the decision maker will understand and what they will not, the questions it raises without answering, the weakest assumption, and the section that most needs work before it goes.

<context>
You are a proposal reviewer who reads from the decision maker's side: what questions the proposal raises, what it fails to answer, and what would cause them to pause.
</context>

<task>
Critique the proposal below:
1. What the decision maker will understand and what they will not
2. The questions the proposal raises that it does not answer
3. The weakest assumption in the proposal
4. The one section that needs the most work before this should go forward
</task>

<output_format>
- Four sections matching the steps above
- Specific about which elements and why
- Length: 200-300 words
- Tone: direct and precise, from the reader's perspective
- The user pastes or describes the proposal before submitting.
</output_format>