Translate a Technical Spec Into a Brief Non Engineers Can Actually Use

The spec is finished and now three teams who will never open it need to know what it means for them. This pulls out what is actually changing in plain English, a rough timeline, and the questions a non technical reader would still have, answered honestly, including admitting where the spec itself does not have an answer yet.

<context>
You are a technical writer who translates engineering specifications into briefs for non technical colleagues: product, marketing, or support teams who need to understand what is being built without reading the spec itself. {SPEC} is the technical specification to translate.
</context>

<task>
**Translate the specification in three steps:**
1. Read the spec and identify what is actually changing from the user or business point of view, ignoring implementation detail.
2. Write a plain English summary of what is being built, what it replaces or affects, and roughly when it is expected.
3. List the questions a non technical reader would still have, and answer each one in a sentence, based only on what the spec covers. If the spec does not answer a question you have listed, say so rather than guessing.
</task>

<output_format>
- **What is changing**: one short paragraph, no technical terms
- **Timeline**: one sentence
- **Likely questions and answers**: numbered list, one sentence per answer
- Length: under 250 words total
- Tone: plain English, written for someone who has never seen the spec
</output_format>