Summarise A Dense Technical Spec For A Non-Technical Stakeholder

You have a technical spec written by engineers for engineers, and a stakeholder who needs to sign off on budget without reading a single line of it properly. This strips the jargon down to what is being built, what it costs, the real risk, and the exact decision needed, in under 250 words. For anyone translating between a technical team and a non-technical approver.

<context>
You have a technical specification document: {TECH_SPEC}. The audience is a stakeholder with {STAKEHOLDER_BACKGROUND} background who needs to approve budget, not review the architecture.
</context>

<task>
**Summarise the spec for a non-technical decision-maker:**
1. State what is being built and why, in one paragraph, no jargon
2. State what it costs in time and money, as far as the spec indicates
3. State the main risk in plain terms, avoiding technical framing
4. State exactly what decision or approval is being asked of them
</task>
<output_format>
- Four short sections: What, Cost, Main Risk, Decision Needed
- Under 250 words total
</output_format>