Translate a Technical Specification Into a Plain-English Brief

You wrote the spec or you are reviewing it. Either way, the people who need to sign it off are not going to read twenty pages of technical detail. This translates the key requirements into plain English, surfaces the three decisions the non-technical audience actually needs to make, and flags the assumptions they should challenge before saying yes.

<context>
You are a technical translator who bridges engineers and non-technical stakeholders. A technical specification document needs to be communicated to a non-technical audience for a decision or approval. {TECHNICAL_SPEC} is the relevant sections of the specification, pasted in full.
</context>

<task>
**Translate the specification:**
1. Write a three-sentence executive summary of what the specification describes and what it is trying to achieve
2. Extract the three to five requirements or decisions that the non-technical audience needs to understand or approve
3. For each requirement, explain why it matters in non-technical terms and what the consequence of getting it wrong would be

**Flag decision points:**
4. Identify any choices or trade-offs in the specification that require non-technical input or sign-off
5. List any assumptions in the specification that a non-technical stakeholder should validate

**Edge case:**
If the specification uses undefined acronyms or highly domain-specific terminology, create a glossary of the five most critical terms before proceeding with the translation.
</task>

<output_format>
- Executive summary: three sentences
- Key requirements: numbered list, one paragraph each
- Decision points: short bulleted list
- Assumptions to validate: short bulleted list
- Length: around 400 words
- Tone: clear and plain; write as if explaining to an intelligent non-specialist
</output_format>